https://wiki.archlinux.org/api.php?action=feedcontributions&user=Giselher&feedformat=atomArchWiki - User contributions [en]2024-03-29T10:17:06ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Mpv&diff=360088Mpv2015-02-09T09:39:22Z<p>Giselher: Fix vapoursynth spelling</p>
<hr />
<div>{{Lowercase title}}<br />
[[Category:Player]]<br />
[[ja:Mpv]]<br />
[[ru:Mpv]]<br />
{{Related articles start}}<br />
{{Related|MPlayer}}<br />
{{Related articles end}}<br />
[http://mpv.io/ mpv] is a movie player based on [http://www.mplayerhq.hu/design7/news.html mplayer] and [http://www.mplayer2.org/ mplayer2]. It supports a wide variety of video file formats, audio and video codecs, and subtitle types. A comprehensive (although admittedly incomplete) list of differences between ''mpv'' and the aforementioned players can be found [https://github.com/mpv-player/mpv/blob/master/DOCS/mplayer-changes.rst here].<br />
<br />
== Installation ==<br />
<br />
[[Pacman|Install]] the {{Pkg|mpv}} package from the [[official repositories]] or {{AUR|mpv-git}} from the [[Arch User Repository]].<br />
<br />
=== Front ends ===<br />
<br />
''mpv'' provides an elegant User Interface called OSC which appears when moving the mouse. To ease casual users, other graphical interfaces exist:<br />
<br />
* {{App|Baka MPlayer|Free and open source, cross-platform, ''libmpv'' based multimedia player (Qt 5).|https://github.com/u8sand/Baka-MPlayer/|{{AUR|baka-mplayer-git}}, {{AUR|baka-mplayer}}}}<br />
* {{App|bomi|Powerful and easy to use multimedia player (Qt 5).|https://bomi-player.github.io/|{{AUR|cmplayer}}, {{AUR|bomi-git}}}}<br />
* {{App|GNOME MPV|A simple frontend for ''mpv'' (GTK+ 3).|https://github.com/gnome-mpv/gnome-mpv/|{{AUR|gnome-mpv-git}}}}<br />
<br />
{{Note|CMPlayer/''bomi'' packages provide ''mpv'' internally.}}<br />
<br />
== Configuration ==<br />
<br />
''mpv'''s configuration is read from the files {{ic|mpv.conf}} (settings) and {{ic|input.conf}} (key bindings). If the [[environment variables|environment variable]] {{ic|XDG_CONFIG_HOME}} is not set, user configuration files will be read from the {{ic|~/.config/mpv}} directory. System-wide configuration files are read from the {{ic|/etc/mpv}} directory.<br />
<br />
== Tips and Tricks ==<br />
<br />
=== Hardware Decoding ===<br />
<br />
Unlike ''mplayer'' and ''mplayer2'', ''mpv'' has both [[VA-API]] and [[VDPAU]] support built-in. To enable it, run ''mpv'' with the {{ic|1=--hwdec='method'}} option. You can find list of all available methods looking for {{ic|1=--hwdec=<api>}} in [[man page]] {{ic|mpv (1)}}. To make this persistent, add the line {{ic|1=hwdec=''method''}} to your configuration file. When hardware decoding is used, the video output should be set to {{ic|opengl}}, {{ic|opengl-hq}} or {{ic|vdpau}} (if using {{ic|1=hwdec=vdpau}}). Using {{ic|1=vo=vaapi}} is not recommended for use anymore [https://github.com/mpv-player/mpv/blob/master/DOCS/man/vo.rst]. If hardware decoding cannot be used, ''mpv'' will automatically fall back to software decoding. See [https://github.com/mpv-player/mpv/blob/master/DOCS/man/options.rst options.rst] and [https://github.com/mpv-player/mpv/blob/master/DOCS/man/vo.rst vo.rst] for more information.<br />
<br />
=== Automatically resuming from where you left off ===<br />
<br />
The default key to quit ''mpv'', saving the video's current position and state, is {{ic|Shift+q}}. This key can be changed by adding the {{ic|quit_watch_later}} string in the key bindings configuration file.<br />
<br />
=== Volume is too low ===<br />
<br />
Set {{ic|1=softvol-max=''value''}} in your configuration file to a reasonable amount, such as {{ic|1=softvol-max=600}}. Additionally (or alternatively), you can utilize [[Wikipedia:Dynamic range compression|dynamic range compression]] with {{ic|1=af=drc}}.<br />
<br />
=== Quickly cycle between multiple aspect ratio ===<br />
<br />
Append this line to your {{ic|input.conf}}:<br />
F2 cycle_values video-aspect "16:9" "16:10" "4:3" "2.35:1" "-1"<br />
<br />
You should now be able to cycle between the provided aspect ratios by pressing the {{ic|F2}} key.<br />
<br />
=== Drawing to a root window ===<br />
<br />
Run ''mpv'' with {{ic|1=--wid=0 file.mp4}}. This tells ''mpv'' to draw onto a window with a window ID of 0.<br />
<br />
=== Use as a browser plugin ===<br />
<br />
With the help of {{AUR|mozplugger}}, ''mpv'' can be used in a supported browser to play video. See [[Browser plugins#MozPlugger]] for configuration details. This coupled with a user script such as [http://isebaro.com/viewtube/?ln=en ViewTube], allows you to use ''mpv'' in place of a site's integrated video player.<br />
<br />
[[Browser_plugins#Video_players_workarounds]] page shows other easy ways to watch videos.<br />
<br />
=== Improving mpv as a music player with Lua scripts ===<br />
<br />
The development of mpv's Lua scripts are documented in [https://github.com/mpv-player/mpv/blob/master/DOCS/man/lua.rst DOCS/man/lua.rst]<br />
and examples are shown in [https://github.com/mpv-player/mpv/tree/master/TOOLS/lua TOOLS/lua]<br />
of the [https://github.com/mpv-player/mpv mpv repository].<br />
[https://bamos.github.io/2014/07/05/mpv-lua-scripting/ This blog post] introduces the<br />
[https://github.com/bamos/dotfiles/blob/master/.mpv/lua/music.lua music.lua] script,<br />
which shows how Lua scripts can be used to improve mpv as a music player.<br />
<br />
=== Twitch.tv streaming over mpv ===<br />
<br />
See [[Livestreamer#Twitch]].<br />
<br />
Another alternative based on Livestreamer is this Lua script: https://gist.github.com/ChrisK2/8701184fe3ea7701c9cc<br />
<br />
== Vapoursynth ==<br />
<br />
Vapoursynth is an alternative to AviSynth that can be used on Linux and allows for Video manipulation via python scripts. Vapoursynths python scripts can be used as video filters for ''mpv''.<br />
<br />
To use vapoursynth filters you have to install the {{ic|vapoursynth}} package and compile ''mpv'' with the {{ic|--enable-vapoursynth}} build flag.<br />
<br />
=== Debanding (flash3kyuu) ===<br />
<br />
To use the f3k_db debanding filter install {{AUR|vapoursynth-plugin-flash3kyuu_deband-git}} and write a python script that uses the ''vapoursynth'' extension.<br />
<br />
The following sample script can be used to enable debanding in ''mpv''.<br />
<br />
import vapoursynth as vs<br />
core = vs.get_core()<br />
<br />
clip = video_in<br />
clip = core.std.Trim(clip, first=0, length=500000)<br />
clip = core.f3kdb.Deband(clip, grainy=0, grainc=0, output_depth=16)<br />
clip.set_output()<br />
<br />
Finally specify the python script in the config file or use a command line argument when executing mpv.<br />
mpv --vf=vapoursynth=f3k_db.py <video_file></div>Giselherhttps://wiki.archlinux.org/index.php?title=Mpv&diff=360087Mpv2015-02-09T09:37:19Z<p>Giselher: Better english (hopefully)</p>
<hr />
<div>{{Lowercase title}}<br />
[[Category:Player]]<br />
[[ja:Mpv]]<br />
[[ru:Mpv]]<br />
{{Related articles start}}<br />
{{Related|MPlayer}}<br />
{{Related articles end}}<br />
[http://mpv.io/ mpv] is a movie player based on [http://www.mplayerhq.hu/design7/news.html mplayer] and [http://www.mplayer2.org/ mplayer2]. It supports a wide variety of video file formats, audio and video codecs, and subtitle types. A comprehensive (although admittedly incomplete) list of differences between ''mpv'' and the aforementioned players can be found [https://github.com/mpv-player/mpv/blob/master/DOCS/mplayer-changes.rst here].<br />
<br />
== Installation ==<br />
<br />
[[Pacman|Install]] the {{Pkg|mpv}} package from the [[official repositories]] or {{AUR|mpv-git}} from the [[Arch User Repository]].<br />
<br />
=== Front ends ===<br />
<br />
''mpv'' provides an elegant User Interface called OSC which appears when moving the mouse. To ease casual users, other graphical interfaces exist:<br />
<br />
* {{App|Baka MPlayer|Free and open source, cross-platform, ''libmpv'' based multimedia player (Qt 5).|https://github.com/u8sand/Baka-MPlayer/|{{AUR|baka-mplayer-git}}, {{AUR|baka-mplayer}}}}<br />
* {{App|bomi|Powerful and easy to use multimedia player (Qt 5).|https://bomi-player.github.io/|{{AUR|cmplayer}}, {{AUR|bomi-git}}}}<br />
* {{App|GNOME MPV|A simple frontend for ''mpv'' (GTK+ 3).|https://github.com/gnome-mpv/gnome-mpv/|{{AUR|gnome-mpv-git}}}}<br />
<br />
{{Note|CMPlayer/''bomi'' packages provide ''mpv'' internally.}}<br />
<br />
== Configuration ==<br />
<br />
''mpv'''s configuration is read from the files {{ic|mpv.conf}} (settings) and {{ic|input.conf}} (key bindings). If the [[environment variables|environment variable]] {{ic|XDG_CONFIG_HOME}} is not set, user configuration files will be read from the {{ic|~/.config/mpv}} directory. System-wide configuration files are read from the {{ic|/etc/mpv}} directory.<br />
<br />
== Tips and Tricks ==<br />
<br />
=== Hardware Decoding ===<br />
<br />
Unlike ''mplayer'' and ''mplayer2'', ''mpv'' has both [[VA-API]] and [[VDPAU]] support built-in. To enable it, run ''mpv'' with the {{ic|1=--hwdec='method'}} option. You can find list of all available methods looking for {{ic|1=--hwdec=<api>}} in [[man page]] {{ic|mpv (1)}}. To make this persistent, add the line {{ic|1=hwdec=''method''}} to your configuration file. When hardware decoding is used, the video output should be set to {{ic|opengl}}, {{ic|opengl-hq}} or {{ic|vdpau}} (if using {{ic|1=hwdec=vdpau}}). Using {{ic|1=vo=vaapi}} is not recommended for use anymore [https://github.com/mpv-player/mpv/blob/master/DOCS/man/vo.rst]. If hardware decoding cannot be used, ''mpv'' will automatically fall back to software decoding. See [https://github.com/mpv-player/mpv/blob/master/DOCS/man/options.rst options.rst] and [https://github.com/mpv-player/mpv/blob/master/DOCS/man/vo.rst vo.rst] for more information.<br />
<br />
=== Automatically resuming from where you left off ===<br />
<br />
The default key to quit ''mpv'', saving the video's current position and state, is {{ic|Shift+q}}. This key can be changed by adding the {{ic|quit_watch_later}} string in the key bindings configuration file.<br />
<br />
=== Volume is too low ===<br />
<br />
Set {{ic|1=softvol-max=''value''}} in your configuration file to a reasonable amount, such as {{ic|1=softvol-max=600}}. Additionally (or alternatively), you can utilize [[Wikipedia:Dynamic range compression|dynamic range compression]] with {{ic|1=af=drc}}.<br />
<br />
=== Quickly cycle between multiple aspect ratio ===<br />
<br />
Append this line to your {{ic|input.conf}}:<br />
F2 cycle_values video-aspect "16:9" "16:10" "4:3" "2.35:1" "-1"<br />
<br />
You should now be able to cycle between the provided aspect ratios by pressing the {{ic|F2}} key.<br />
<br />
=== Drawing to a root window ===<br />
<br />
Run ''mpv'' with {{ic|1=--wid=0 file.mp4}}. This tells ''mpv'' to draw onto a window with a window ID of 0.<br />
<br />
=== Use as a browser plugin ===<br />
<br />
With the help of {{AUR|mozplugger}}, ''mpv'' can be used in a supported browser to play video. See [[Browser plugins#MozPlugger]] for configuration details. This coupled with a user script such as [http://isebaro.com/viewtube/?ln=en ViewTube], allows you to use ''mpv'' in place of a site's integrated video player.<br />
<br />
[[Browser_plugins#Video_players_workarounds]] page shows other easy ways to watch videos.<br />
<br />
=== Improving mpv as a music player with Lua scripts ===<br />
<br />
The development of mpv's Lua scripts are documented in [https://github.com/mpv-player/mpv/blob/master/DOCS/man/lua.rst DOCS/man/lua.rst]<br />
and examples are shown in [https://github.com/mpv-player/mpv/tree/master/TOOLS/lua TOOLS/lua]<br />
of the [https://github.com/mpv-player/mpv mpv repository].<br />
[https://bamos.github.io/2014/07/05/mpv-lua-scripting/ This blog post] introduces the<br />
[https://github.com/bamos/dotfiles/blob/master/.mpv/lua/music.lua music.lua] script,<br />
which shows how Lua scripts can be used to improve mpv as a music player.<br />
<br />
=== Twitch.tv streaming over mpv ===<br />
<br />
See [[Livestreamer#Twitch]].<br />
<br />
Another alternative based on Livestreamer is this Lua script: https://gist.github.com/ChrisK2/8701184fe3ea7701c9cc<br />
<br />
== Vapoursynth ==<br />
<br />
Vapoursynth is an alternative to AviSynth that can be used on Linux and allows for Video manipulation via python scripts. Vapoursnyths python scripts can be used as video filters for ''mpv''.<br />
<br />
To use vapoursynth filters you have to install the {{ic|vapoursynth}} package and compile ''mpv'' with the {{ic|--enable-vapoursynth}} build flag.<br />
<br />
=== Debanding (flash3kyuu) ===<br />
<br />
To use the f3k_db debanding filter install {{AUR|vapoursynth-plugin-flash3kyuu_deband-git}} and write a python script that uses the ''vapoursyth'' extension.<br />
<br />
The following sample script can be used to enable debanding in ''mpv''.<br />
<br />
import vapoursynth as vs<br />
core = vs.get_core()<br />
<br />
clip = video_in<br />
clip = core.std.Trim(clip, first=0, length=500000)<br />
clip = core.f3kdb.Deband(clip, grainy=0, grainc=0, output_depth=16)<br />
clip.set_output()<br />
<br />
Finally specify the python script in the config file or use a command line argument when executing mpv.<br />
mpv --vf=vapoursynth=f3k_db.py <video_file></div>Giselherhttps://wiki.archlinux.org/index.php?title=Mpv&diff=360031Mpv2015-02-08T14:16:01Z<p>Giselher: </p>
<hr />
<div>{{Lowercase title}}<br />
[[Category:Player]]<br />
[[ja:Mpv]]<br />
[[ru:Mpv]]<br />
{{Related articles start}}<br />
{{Related|MPlayer}}<br />
{{Related articles end}}<br />
[http://mpv.io/ mpv] is a movie player based on [http://www.mplayerhq.hu/design7/news.html mplayer] and [http://www.mplayer2.org/ mplayer2]. It supports a wide variety of video file formats, audio and video codecs, and subtitle types. A comprehensive (although admittedly incomplete) list of differences between ''mpv'' and the aforementioned players can be found [https://github.com/mpv-player/mpv/blob/master/DOCS/mplayer-changes.rst here].<br />
<br />
== Installation ==<br />
<br />
[[Pacman|Install]] the {{Pkg|mpv}} package from the [[official repositories]] or {{AUR|mpv-git}} from the [[Arch User Repository]].<br />
<br />
=== Front ends ===<br />
<br />
''mpv'' provides an elegant User Interface called OSC which appears when moving the mouse. To ease casual users, other graphical interfaces exist:<br />
<br />
* {{App|Baka MPlayer|Free and open source, cross-platform, ''libmpv'' based multimedia player (Qt 5).|https://github.com/u8sand/Baka-MPlayer/|{{AUR|baka-mplayer-git}}, {{AUR|baka-mplayer}}}}<br />
* {{App|bomi|Powerful and easy to use multimedia player (Qt 5).|https://bomi-player.github.io/|{{AUR|cmplayer}}, {{AUR|bomi-git}}}}<br />
* {{App|GNOME MPV|A simple frontend for ''mpv'' (GTK+ 3).|https://github.com/gnome-mpv/gnome-mpv/|{{AUR|gnome-mpv-git}}}}<br />
<br />
{{Note|CMPlayer/''bomi'' packages provide ''mpv'' internally.}}<br />
<br />
== Configuration ==<br />
<br />
''mpv'''s configuration is read from the files {{ic|mpv.conf}} (settings) and {{ic|input.conf}} (key bindings). If the [[environment variables|environment variable]] {{ic|XDG_CONFIG_HOME}} is not set, user configuration files will be read from the {{ic|~/.config/mpv}} directory. System-wide configuration files are read from the {{ic|/etc/mpv}} directory.<br />
<br />
== Tips and Tricks ==<br />
<br />
=== Hardware Decoding ===<br />
<br />
Unlike ''mplayer'' and ''mplayer2'', ''mpv'' has both [[VA-API]] and [[VDPAU]] support built-in. To enable it, run ''mpv'' with the {{ic|1=--hwdec='method'}} option. You can find list of all available methods looking for {{ic|1=--hwdec=<api>}} in [[man page]] {{ic|mpv (1)}}. To make this persistent, add the line {{ic|1=hwdec=''method''}} to your configuration file. When hardware decoding is used, the video output should be set to {{ic|opengl}}, {{ic|opengl-hq}} or {{ic|vdpau}} (if using {{ic|1=hwdec=vdpau}}). Using {{ic|1=vo=vaapi}} is not recommended for use anymore [https://github.com/mpv-player/mpv/blob/master/DOCS/man/vo.rst]. If hardware decoding cannot be used, ''mpv'' will automatically fall back to software decoding. See [https://github.com/mpv-player/mpv/blob/master/DOCS/man/options.rst options.rst] and [https://github.com/mpv-player/mpv/blob/master/DOCS/man/vo.rst vo.rst] for more information.<br />
<br />
=== Automatically resuming from where you left off ===<br />
<br />
The default key to quit ''mpv'', saving the video's current position and state, is {{ic|Shift+q}}. This key can be changed by adding the {{ic|quit_watch_later}} string in the key bindings configuration file.<br />
<br />
=== Volume is too low ===<br />
<br />
Set {{ic|1=softvol-max=''value''}} in your configuration file to a reasonable amount, such as {{ic|1=softvol-max=600}}. Additionally (or alternatively), you can utilize [[Wikipedia:Dynamic range compression|dynamic range compression]] with {{ic|1=af=drc}}.<br />
<br />
=== Quickly cycle between multiple aspect ratio ===<br />
<br />
Append this line to your {{ic|input.conf}}:<br />
F2 cycle_values video-aspect "16:9" "16:10" "4:3" "2.35:1" "-1"<br />
<br />
You should now be able to cycle between the provided aspect ratios by pressing the {{ic|F2}} key.<br />
<br />
=== Drawing to a root window ===<br />
<br />
Run ''mpv'' with {{ic|1=--wid=0 file.mp4}}. This tells ''mpv'' to draw onto a window with a window ID of 0.<br />
<br />
=== Use as a browser plugin ===<br />
<br />
With the help of {{AUR|mozplugger}}, ''mpv'' can be used in a supported browser to play video. See [[Browser plugins#MozPlugger]] for configuration details. This coupled with a user script such as [http://isebaro.com/viewtube/?ln=en ViewTube], allows you to use ''mpv'' in place of a site's integrated video player.<br />
<br />
[[Browser_plugins#Video_players_workarounds]] page shows other easy ways to watch videos.<br />
<br />
=== Improving mpv as a music player with Lua scripts ===<br />
<br />
The development of mpv's Lua scripts are documented in [https://github.com/mpv-player/mpv/blob/master/DOCS/man/lua.rst DOCS/man/lua.rst]<br />
and examples are shown in [https://github.com/mpv-player/mpv/tree/master/TOOLS/lua TOOLS/lua]<br />
of the [https://github.com/mpv-player/mpv mpv repository].<br />
[https://bamos.github.io/2014/07/05/mpv-lua-scripting/ This blog post] introduces the<br />
[https://github.com/bamos/dotfiles/blob/master/.mpv/lua/music.lua music.lua] script,<br />
which shows how Lua scripts can be used to improve mpv as a music player.<br />
<br />
=== Twitch.tv streaming over mpv ===<br />
<br />
See [[Livestreamer#Twitch]].<br />
<br />
Another alternative based on Livestreamer is this Lua script: https://gist.github.com/ChrisK2/8701184fe3ea7701c9cc<br />
<br />
== Vapoursynth ==<br />
<br />
Vapoursynth is an alternative to AviSynth that can be used on Linux.<br />
It allows for Video manipulation via python scripts. Vapoursnyths python scripts can be used as video filters for ''mpv''.<br />
<br />
To use vapoursynth filters you have to install the {{ic|vapoursynth}} and compile ''mpv'' with {{ic|--enable-vapoursynth}}.<br />
<br />
=== Debanding (flash3kyuu) ===<br />
<br />
To use the f3k_db debanding filter install {{AUR|vapoursynth-plugin-flash3kyuu_deband-git}}.<br />
<br />
The following sample script can be used to enable debanding in ''mpv''.<br />
<br />
import vapoursynth as vs<br />
core = vs.get_core()<br />
<br />
clip = video_in<br />
clip = core.std.Trim(clip, first=0, length=500000)<br />
clip = core.f3kdb.Deband(clip, grainy=0, grainc=0, output_depth=16)<br />
clip.set_output()<br />
<br />
Finally specify the python script in the config file or use a command line argument when executing mpv.<br />
mpv --vf=vapoursynth=f3k_db.py <video_file></div>Giselherhttps://wiki.archlinux.org/index.php?title=Wayland&diff=249964Wayland2013-03-09T09:47:19Z<p>Giselher: Update GTK3 section</p>
<hr />
<div>[[Category:X Server]]<br />
[[fr:Wayland]]<br />
[[ja:Wayland]]<br />
[[zh-CN:Wayland]]<br />
{{Article summary start}}<br />
{{Article summary text|A guide to installing and running the Wayland display server.}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|KMS}}<br />
{{Article summary wiki|Xorg}}<br />
{{Article summary end}}<br />
<br />
'''Wayland''' is a new windowing protocol for Linux. Utilization of Wayland requires changes to and re-installation of parts of your system's software. For more information on Wayland see its [http://wayland.freedesktop.org/ homepage].<br />
<br />
{{Warning|Wayland is under heavy development. Support can not be guaranteed and it may not function as you expect.}}<br />
<br />
== Requirements ==<br />
Currently Wayland will only work with on a system that is utilizing [[KMS]].<br />
<br />
== Installation ==<br />
Wayland is most probably installed on your system already as it is an indirect dependency of {{pkg|gtk2}} and {{pkg|gtk3}}. If it is not installed, you will find the {{pkg|wayland}} package in extra.<br />
<br />
== Usage ==<br />
As Wayland is only a library, it is useless on its own. To use it, you need a compositor (like Weston), Weston demo applications, Qt5 (or Qt4 with QPA enabled) with Wayland plugin, and/or GTK+ with Wayland support.<br />
<br />
== Weston ==<br />
=== Installation ===<br />
You need to install {{pkg|weston}} from community.<br />
{{Note|If you get the following error: "Failed to create XKB context", install {{Pkg|xkeyboard-config}}: {{ic|# pacman -S xkeyboard-config}} }}<br />
<br />
=== Usage ===<br />
Now that Wayland and its requirements are installed you should be ready to test it out. Try switching to a terminal and running:<br />
$ weston-launch<br />
{{Note|There may be some trouble with keyboard & mouse not working unless this is ran as root.}}<br />
<br />
You may also try exporting the following, if having problems with hardware drivers: <br />
$ export EGL_DRIVER=/usr/lib/egl/egl_gallium.so<br />
<br />
Then at a TTY you can run the demos. To launch a terminal emulator:<br />
$ weston-terminal<br />
<br />
To move flowers around the screen:<br />
$ weston-flower <br />
<br />
To test the frame protocol (runs {{ic|glxgears}}):<br />
$ weston-gears<br />
<br />
To display images:<br />
$ weston-image image1.jpg image2.jpg...<br />
<br />
To display PDF Files:<br />
$ weston-view doc1.pdf doc2.pdf...<br />
<br />
== Qt ==<br />
<br />
=== Installation ===<br />
You need to install {{Pkg|qt5-base}}.<br />
<br />
=== Usage ===<br />
At first, you need a working Wayland compositor, like the one from demo applications, or an experimental version of KWin.<br />
<br />
Then compile any qmake-based Qt project:<br />
$ qmake<br />
$ make<br />
<br />
And run it by executing the compiled binary:<br />
$ export QT_QPA_PLATFORM=waylandgl<br />
$ ./binaryname<br />
<br />
=== Qt Compositor ===<br />
There is ongoing work to make [http://labs.qt.nokia.com/2011/03/18/multi-process-lighthouse/ Qt-Compositor], a base layer to make custom Qt compositors on top of Wayland.<br />
<br />
== Other GUI libraries ==<br />
([http://wayland.freedesktop.org/toolkits.html page from official website])<br />
<br />
===GTK+===<br />
<br />
You need to install {{pkg|gtk3}} from testing, which has the Wayland backend enabled.<br />
<br />
With GTK+ 3.0, GTK+ gained support for multiple backends at runtime and can switch between backends in the same way Qt can with lighthouse.<br />
<br />
When both Wayland and X backends are enabled, GTK+ will default to the X11 backend, but this can be overridden by setting the <code>GDK_BACKEND</code> environment variable to <code>wayland</code>.<br />
<br />
Remove {{pkg|libcanberra}} if you get segmentation faults when running gtk applications.<br />
<br />
===Clutter===<br />
<br />
The Clutter toolkit has a Wayland backend that allows it to run as a Wayland client. The backend is in the master branch of the [http://git.gnome.org/browse/clutter main repo] and can be activated by passing <code>--with-flavour=wayland</code> to the configure script.<br />
<br />
===SDL===<br />
<br />
Benjamin Franzke is working on a port of SDL to Wayland, it's available in his [http://cgit.freedesktop.org/~bnf/sdl-wayland/ sdl-wayland repo] on freedesktop.org. Further development upon Benjamins work was done by Andre Heider in his [https://github.com/dhewg/libsdl/tree/wl wayland branch] of libsdl.<br />
<br />
===EFL===<br />
<br />
EFL has complete Wayland support. Please see [http://trac.enlightenment.org/e/wiki/Wayland here] for details.<br />
<br />
==Window managers and desktop shells==<br />
<br />
===KDE===<br />
<br />
There is [http://blog.martin-graesslin.com/blog/2011/03/kwin-at-gsoc-2011/ early work] to make it possible to run KWin (KDE's window manager) on Wayland.<br />
<br />
===GNOME===<br />
<br />
GNOME will be ported to Wayland in a future version.<br />
<br />
===Unity===<br />
Ubuntu desktop shell Unity, using Compiz window manager, was [http://www.markshuttleworth.com/archives/551 announced] to be ported to Wayland.<br />
<br />
<br />
===Pure Wayland===<br />
<br />
{{Warning|Some really quick notes on installing a pure (no X11) wayland system on Arch Linux. This is from source and installed into /usr/local. May break your system. You have been warned. (by elethiomel@gmail.com)}}<br />
<br />
First install a base Arch Linux install with base and base-devel. Do not install xorg or any of its libraries<br />
<br />
<br />
===== Wayland =====<br />
<br />
$ pacman -S libffi<br />
$ git clone git://anongit.freedesktop.org/wayland/wayland<br />
$ cd wayland<br />
$ ./autogen.sh --prefix=/usr/local<br />
$ make<br />
$ make install<br />
<br />
===== DRM and Mesa =====<br />
<br />
$ git clone git://anongit.freedesktop.org/git/mesa/drm<br />
$ cd drm<br />
$ ./autogen.sh --prefix=/usr/local<br />
$ make<br />
$ make install<br />
<br />
$ git clone git://anongit.freedesktop.org/mesa/mesa<br />
$ cd mesa<br />
$ CFLAGS=-DMESA_EGL_NO_X11_HEADERS ./autogen.sh --prefix=/usr/local --enable-gles2 --disable-gallium-egl --with-egl-platforms=wayland,drm --enable-gbm --enable-shared-glapi --with-gallium-drivers=r300,r600,swrast,nouveau --disable-glx --disable-xlib<br />
$ make<br />
$ make install<br />
<br />
===== xorg-macros =====<br />
<br />
$ git clone http://anongit.freedesktop.org/git/xorg/util/macros.git<br />
$ cd macros/<br />
$ ./autogen.sh --prefix=/usr/local/<br />
$ make<br />
$ make install<br />
<br />
===== libxkbcommon =====<br />
<br />
$ git clone git://people.freedesktop.org/xorg/lib/libxkbcommon.git<br />
$ cd libxkbcommon/<br />
$ export ACLOCAL_PATH=/usr/local/share/aclocal/<br />
$ ./autogen.sh --prefix=/usr/local/ --with-xkb-config-root=/usr/local/share/X11/xkb<br />
$ make<br />
$ make install<br />
<br />
===== pixman =====<br />
<br />
$ git clone git://anongit.freedesktop.org/pixman<br />
$ cd pixman/<br />
$ ./autogen.sh --prefix=/usr/local/<br />
$ make<br />
$ make install<br />
<br />
===== cairo =====<br />
<br />
Note - no glx/gl or xcb - EGL only.<br />
<br />
$ pacman -S libpng<br />
$ git clone git://anongit.freedesktop.org/cairo<br />
$ cd cairo<br />
$ CFLAGS=-DMESA_EGL_NO_X11_HEADERS ./autogen.sh --prefix=/usr/local/ --disable-xcb --enable-glesv2 <br />
$ make<br />
$ make install<br />
<br />
===== xkb files =====<br />
<br />
Either<br />
<br />
a) Copy from an existing system a set of xkb layouts<br />
<br />
$ scp -r /usr/share/X11/xkb to /usr/local/share/X11/<br />
<br />
or<br />
<br />
b) build {{ic|xkeyboard-config}} from git with {{ic|--prefix&#61;/usr/local}} and {{ic|--disable-runtime-deps}}<br />
<br />
===== weston =====<br />
<br />
$ git clone git://anongit.freedesktop.org/wayland/weston<br />
$ cd weston/<br />
$ CFLAGS="-I/usr/local/include/libdrm/ -DMESA_EGL_NO_X11_HEADERS" ./autogen.sh --prefix=/usr/local/ --with-cairo-glesv2 --disable-xwayland --disable-x11-compositor --disable- xwayland-test<br />
$ make<br />
$ make install<br />
<br />
==See also==<br />
* [[Cursor Themes]]<br />
<br />
==External links==<br />
* [https://bbs.archlinux.org/viewtopic.php?id=107499 Arch Linux forum discussion]<br />
* [http://wayland.freedesktop.org/docs/html/ Wayland documentation online]</div>Giselherhttps://wiki.archlinux.org/index.php?title=Archiso&diff=220349Archiso2012-08-29T13:56:12Z<p>Giselher: remove second patch package</p>
<hr />
<div>[[Category:Live Arch systems]]<br />
[[el:Archiso]]<br />
[[fr:Archiso]]<br />
[[it:Archiso]]<br />
[[nl:Archiso]]<br />
[[ru:Archiso]]<br />
[[uk:Archiso]]<br />
'''Archiso''' is a small set of bash scripts that is capable of building fully functional Arch Linux based live CD and USB images. It is a very generic tool, so it could potentially be used to generate anything from rescue systems, install disks, to special interest live CD/DVD/USB systems, and who knows what else. Simply put, if it involves Arch on a shiny coaster, it can do it.<br />
The heart and soul of Archiso is mkarchiso. All of its options are documented in its usage output, so its direct usage won't be covered here. Instead, this wiki article will act as a guide for rolling your own live mediums in no time!<br />
<br />
== Setup ==<br />
<br />
Before we begin, we need to grab the archiso scripts which carry out the beef of the work for us. You can get archiso from Git (recommended) or from [https://aur.archlinux.org/packages.php?ID=25996 aur]. We also need a few packages which archiso relies on; the following commands take care of this for us:<br />
<br />
# pacman -S make patch git libisoburn squashfs-tools dosfstools rsync lynx --needed<br />
# git clone git://projects.archlinux.org/archiso.git<br />
# make -C archiso install<br />
<br />
Create a directory to work within, this is where all the modifications to the live image will take place: ~/archlive should do fine.<br />
$ mkdir ~/archlive<br />
<br />
The archiso scripts that were installed to the host system earlier now need to be copied over into the newly created directory you will be working within.<br />
Archiso comes with two "profiles": releng, and baseline.<br />
If you wish to create a fully customised live version of Arch Linux, pre-installed with all your favourite programs and configurations, use "releng".<br />
If you just want to create the most basic live media, with no pre-installed packages and minimalistic configurations, then use "baseline".<br />
<br />
So, depending on your needs, execute the following, replacing 'PROFILE' with either '''releng''' or '''baseline'''.<br />
# cp -r /usr/share/archiso/configs/'''PROFILE'''/ ~/archlive<br />
<br />
If you are using the 'releng' profile to make a fully customised image, then you can proceed onto [[Archiso#Configure_our_live_medium]].<br />
<br />
If you are using the 'baseline' profile to create a bare bones, installation image, then you won't be needing to do any customisations and can proceed onto [[Archiso#Build_the_ISO]]<br />
<br />
== Setup (manual way) ==<br />
{{Note|If you have already completed Setup the 'automatic' way, using the steps above, then you do not need to read this section.}}<br />
<br />
Setup a base filesystem<br />
# mkarchiso init<br />
<br />
Install other packages (optional)<br />
# mkarchiso -p "pkg1 pkg2 pkg3 ... pkgN" install<br />
<br />
At this point, customize anything that you want in root-image, then exit when done.<br />
<br />
# mkarchiso -r "bash" run<br />
<br />
Setup initramfs image.<br />
Copy needed hooks to root-image<br />
<br />
# cp /usr/lib/initcpio/hooks/archiso work/root-image/usr/lib/initcpio/hooks<br />
# cp /usr/lib/initcpio/install/archiso work/root-image/usr/lib/initcpio/install<br />
<br />
Create a config for mkinitcpio '''work/root-image/etc/mkinitcpio-archiso.conf'''<br />
HOOKS="base udev archiso pata scsi sata usb fw filesystems usbinput"<br />
COMPRESSION="xz"<br />
<br />
Create a folder named as your PC's architecture, and generate the initramfs image:<br />
# mkdir work/root-image/boot/i686<br />
# mkarchiso -r "mkinitcpio -c /etc/mkinitcpio-archiso.conf -k /boot/vmlinuz-linux -g /boot/i686/archiso.img" run<br />
<br />
Move kernel/initramfs to boot/<br />
# mkdir -p work/iso/arch/boot/i686<br />
# mv work/root-image/boot/vmlinuz-linux work/iso/arch/boot/i686/vmlinuz<br />
# mv work/root-image/boot/i686/archiso.img work/iso/arch/boot/i686/archiso.img<br />
<br />
Setup syslinux<br />
<br />
Create a directory for it.<br />
# mkdir -p work/iso/arch/boot/syslinux<br />
<br />
Create a '''work/iso/arch/boot/syslinux/syslinux.cfg''' file.<br />
<br />
{{bc|1=<br />
DEFAULT menu.c32<br />
PROMPT 0<br />
MENU TITLE Arch Linux<br />
TIMEOUT 300<br />
<br />
LABEL arch<br />
MENU LABEL Arch Linux<br />
LINUX /arch/boot/i686/vmlinuz<br />
INITRD /arch/boot/i686/archiso.img<br />
APPEND archisolabel=MY_ARCH<br />
<br />
ONTIMEOUT arch<br />
}}<br />
<br />
Copy menu.c32 needed by previous config.<br />
# cp work/root-image/usr/lib/syslinux/menu.c32 work/iso/arch/boot/syslinux/<br />
<br />
Setup isolinux (optional, only needed for booteable iso)<br />
<br />
# mkdir work/iso/isolinux<br />
# cp work/root-image/usr/lib/syslinux/isolinux.bin work/iso/isolinux/<br />
# cp work/root-image/usr/lib/syslinux/isohdpfx.bin work/iso/isolinux/<br />
<br />
Create a '''work/iso/isolinux/isolinux.cfg'''<br />
{{bc|<br />
DEFAULT loadconfig<br />
<br />
LABEL loadconfig<br />
CONFIG /arch/boot/syslinux/syslinux.cfg<br />
APPEND /arch/boot/syslinux/<br />
}}<br />
<br />
Create an '''work/iso/arch/aitab''' file.<br />
# <img> <mnt> <arch> <sfs_comp> <fs_type> <fs_size><br />
root-image / i686 xz ext4 50%<br />
<br />
Build all filesystem images specified in aitab (.fs .fs.sfs .sfs)<br />
# mkarchiso prepare<br />
<br />
Generate an ISO 9660 with "El Torito" boot image (optional)<br />
# mkarchiso -L "MY_ARCH" iso "my-arch.iso"<br />
<br />
== Configure our live medium ==<br />
<br />
This section details configuring the image you will be creating, allowing you to define the packages and configurations you want your live image to contain.<br />
<br />
Change into the directory we created earlier (~/archlive/releng/ if you have been following this guide), you will see a number of files and directories; we are only concerned with a few of these, mainly: <br />
packages.* - this is where you list, line by line, the packages you want to have installed, and<br />
the root-image directory - this directory acts as an overlay and it is where you make all the customisations.<br />
<br />
=== Installing packages ===<br />
<br />
You will want to create a list of packages you want installed on your live CD system. A file full of package names, one-per-line, is the format for this. This is '''''great''''' for special interest live CDs, just specify packages you want and bake the image.<br />
Edit the packages.i686, or packages.x86_64 file depending on whether you are create a 32bit, or 64bit image, respectively.<br />
<br />
{{Tip|You can also create a '''[[custom local repository]]''' for the purpose of preparing custom packages or packages from [[AUR]]/[[ABS]]. Just add your local repository at the first position (for top priority) of your build machine's '''pacman.conf''' and you are good to go!}}<br />
<br />
=== Adding a user ===<br />
<br />
There are two methods to creating a user: either by adding the relevant useradd command to rc.local, or by copying over (and modifying) /etc/shadow, /etc/passwd, and /etc/group.<br />
The latter method shall be discussed here.<br />
<br />
Copy your /etc/shadow, /etc/passwd, and /etc/group from your '''host''' system to the /etc/ directory '''where you now working''' (which should be ~/archlive/releng/root-image/etc)<br />
e.g.<br />
# cp /etc/{shadow,passwd,group} ~/archlive/releng/root-image/etc/<br />
<br />
{{Warning|The shadow file will contain your encrypted password. I recommend before you copy the shadow file over, you change the password of your host user to that which you want your live user to have, copy the shadow file over, and then change back your password.}}<br />
<br />
=== Adding files to image ===<br />
<br />
{{Note|You must be root to do this, do not change the ownership of any of the files you copy over, '''everything''' within the root-image directory must be root owned. Proper ownerships will be sorted out shortly.}}<br />
<br />
The root-image directory acts as an overlay, think of it as root directory '/' on your current system, so any files you place within this directory will be copied over on boot-up.<br />
<br />
So if you have a set of iptables scripts on your current system you want to be used on you live image, copy them over as such:<br />
# cp -r /etc/iptables ~/archlive/releng/root-image/etc<br />
<br />
Placing files in the users home directory is a little different. Do not place them within root-image/home, but instead create a skel directory within root-image/ and place them there. We will then add the relevant commands to the rc.local we are going to create to copy them over on boot and sort out the permissions.<br />
<br />
First, create the skel directory; making sure you are within ~/archlive/releng/root-image/etc directory (if this is where you are working from):<br />
# cd ~/archlive/releng/root-image/etc && mkdir skel<br />
<br />
Now copy the 'home' files to the skel directory, again doing everything as root!<br />
e.g for .bashrc. <br />
# cp ~/.bashrc ~/archlive/releng/root-image/etc/skel/<br />
<br />
Inside the root-image/etc/ directory, create the rc.local file, and '''make sure''' you make it executable:<br />
<br />
# cd ~/archlive/releng/root-image/etc && touch rc.local && chmod +x rc.local<br />
<br />
Now add the all of following to rc.local, replacing 'youruser' with the user you specified earlier.<br />
# Create the user directory for live session<br />
if [ ! -d /home/'''youruser''' ]; then<br />
mkdir /home/'''youruser''' && chown '''youruser''' /home/'''youruser'''<br />
fi<br />
# Copy files over to home<br />
su -c "cp -r /etc/skel/.[a-zA-Z0-9]* /home/'''youruser'''/" '''youruser'''<br />
<br />
=== aitab ===<br />
<br />
The default file should work fine, so you should not need to touch it.<br />
<br />
The aitab file holds information about the filesystems images that must be created by mkarchiso and mounted at initramfs stage from the archiso hook.<br />
It consists of some fields which define the behaviour of images.<br />
<br />
# <img> <mnt> <arch> <sfs_comp> <fs_type> <fs_size><br />
<br />
; <img>: Image name without extension (.fs .fs.sfs .sfs).<br />
; <mnt>: Mount point.<br />
; <arch>: Architecture { i686 | x86_64 | any }.<br />
; <sfs_comp>: SquashFS compression type { gzip | lzo | xz }. A special value of "none" denotes no usage of SquashFS.<br />
; <fs_type>: Set the filesystem type of the image { ext4 | ext3 | ext2 | xfs }. A special value of "none" denotes no usage of a filesystem. In that case all files are pushed directly to SquashFS filesystem.<br />
; <fs_size>: An absolute value of file system image size in MiB (example: 100, 1000, 4096, etc) A relative value of file system free space [in percent] {1%..99%} (example 50%, 10%, 7%). This is an estimation, and calculated in a simple way. Space used + 10% (estimated for metadata overhead) + desired %<br />
<br />
{{Note|Some combinations are invalid. Example both sfs_comp and fs_type are set to none}}<br />
<br />
=== Boot Loader ===<br />
The default file should work fine, so you should not need to touch it.<br />
<br />
Due to the modular nature of isolinux, you are able to use lots of addons since all *.c32 files are copied and available to you. Take a look at the [http://syslinux.zytor.com/wiki/index.php/SYSLINUX official syslinux site] and the [http://projects.archlinux.org/archiso.git/tree/configs/syslinux-iso/boot-files archiso git repo]. Using said addons, it is possible to make visually attractive and complex menus. See [http://syslinux.zytor.com/wiki/index.php/Comboot/menu.c32 here].<br />
<br />
=== Finishing the root-image ===<br />
Some tips that will not be covered in this article because there are other articles on this wiki that already do, but please feel free to add them here.<br />
*Configure an ''inittab'' to start into X at boot time<br />
*Configure the ''hosts'' file<br />
*Configure ''rc.conf'' (no fancy modules required here)<br />
*Configure ''sudoers''<br />
*Configure ''rc.local''<br />
*Put additional artworks onto the medium <br />
*Put arbitrary binary stuff into opt/<br />
<br />
== Build the ISO ==<br />
<br />
Now you are ready to turn your files into the .iso which you can then burn to CD or USB:<br />
Inside the directory you are working with, either ~/archlive/releng, or ~/archlive/baseline, execute:<br />
<br />
# ./build.sh -v build single netinstall<br />
<br />
You can replace 'netinstall' with 'core' if you wish; however, doing so will cache all of the packages pacman downloads into the iso file, which will vastly inrease it's size.<br />
<br />
The script will now download and install the packages you specified to work/*/root-image, create the kernel and init images, apply your customizations and finally build the iso into out/.<br />
<br />
You can now dd the iso file onto a USB using dd, an example of which:<br />
# dd if=~/archlive/releng/out/*.iso of=/dev/sdx<br />
You will have to adjust accordingly, and make sure you choose the right output file! A simple mistake here will destory data on your harddisk.<br />
<br />
== See also ==<br />
*[http://projects.archlinux.org/?p=archiso.git;a=summary Archiso project page]<br />
*[[Archiso_as_pxe_server|Archiso as pxe server]]<br />
*[https://kroweer.wordpress.com/2011/09/07/creating-a-custom-arch-linux-live-usb Step-by-step tutorial on using ArchISO]<br />
*[http://didjix.blogspot.com/ A live DJ distribution powered by ArchLinux and built with Archiso]</div>Giselherhttps://wiki.archlinux.org/index.php?title=Skype&diff=211429Skype2012-06-28T10:09:37Z<p>Giselher: </p>
<hr />
<div>[[bg:Skype]]<br />
[[cs:Skype]]<br />
[[lt:Skype]]<br />
[[ru:Skype]]<br />
[[uk:Skype]]<br />
[[Category:Audio/Video]]<br />
[[Category:Telephony and Voice]]<br />
<br />
==Installing and Running Skype==<br />
{{Pkg|skype}} is available in <nowiki>[</nowiki>[[AUR User Guidelines#.5Bcommunity.5D|community]]] for i686 systems and <nowiki>[</nowiki>[[Arch64 FAQ#Multilib Repository - Multilib_Project|multilib]]] for x86_64 systems [http://www.archlinux.org/news/508/] or as [https://aur.archlinux.org/packages.php?ID=18312 bin32-skype-oss] for the OSS sound system in the AUR. Enable the appropriate repository in {{ic|/etc/pacman.conf}} and then use [[pacman]] to install Skype,<br />
# pacman -S skype<br />
<br />
Running Skype is just as easy. Type {{Ic|skype}} into a terminal or double-click the Skype icon on your desktop or in your DE's application menu.<br />
<br />
==Securing Skype==<br />
There are a couple of reasons you might want to restrict Skype's access to your computer:<br />
* The skype binary is disguised against decompiling, so nobody is (still) able to reproduce what it really does.<br />
* It produces encrypted traffic even when you are not actively using Skype.<br />
* ...<br />
See [http://www1.cs.columbia.edu/~salman/skype/index.html] for more information.<br />
<br />
===AppArmor===<br />
Follow the instructions [[AppArmor|here]] to set up AppArmor.<br />
<br />
The userland tools for AppArmor come with a collection of example profiles. Skype is amongst them. Copy this to the directory where AppArmor profiles are stored.<br />
# cp -ip /etc/apparmor/profiles/extras/usr.bin.skype /etc/apparmor.d/<br />
<br />
For whatever reason, the profile is not complete. You may wish to modify it further. Here is an [http://sprunge.us/ZVcY example]. (If the Mozilla denials annoy you, feel free to uncomment the appropriate lines.)<br />
<br />
To use the profile, first be sure {{Ic|securityfs}} is mounted,<br />
# mount -t securityfs securityfs /sys/kernel/security<br />
<br />
Load the profile by the command,<br />
# apparmor_parser -r /etc/apparmor.d/usr.bin.skype<br />
<br />
Now you can run Skype restricted but as your own user. Denials are logged in {{ic|messages.log}}.<br />
<br />
===TOMOYO===<br />
{{Expansion}}<br />
[[Tomoyo|TOMOYO]]<br />
<br />
===Use Skype with special user===<br />
Instead of using AppArmor or TOMOYO which require the installation of extra packages, one may prefer to add a special user. This user is only used for running Skype within one's normal environment. This approach restricts Skype to reading only the data of this particular user instead of one's main user. (The new user should not be used for any other thing. Skype only.)<br />
<br />
Optionally, we first add a default group for the skype user. I will call the new user and its default group "skype". The security advantage in keeping the "skype" user in its separate group is that it can be restricted from accessing some places other users are allowed in.<br />
# groupadd skype<br />
Then we have to add the new user:<br />
# adduser<br />
Enter the details for the new user (assumed login name: "skype"). If you created the default "skype" group and want to keep "skype" outside the "users" group, enter "skype" when the wizard asks for the initial group. As additional groups we need "audio,video,pulse-access,pulse-rt".<br />
<br />
Now add the following line to {{ic|/home/skype/.bashrc}}:<br />
export DISPLAY=":0.0"<br />
<br />
At last we define the alias (e.g. in {{ic|~/.bashrc}}):<br />
alias skype='xhost +local: && su skype -c skype'<br />
Now we can start Skype as the newly created user simply by running {{Ic|skype}} from the command line and entering the password of the user skype.<br />
<br />
If you are tired of typing in the skype user's password every time, make sure you installed the [[sudo]] package, run {{Ic|visudo}} then add this line at the bottom:<br />
%wheel ALL=(skype) NOPASSWD: /usr/bin/skype<br />
<br />
And use this alias to launch skype:<br />
alias skype='xhost +local: && sudo -u skype /usr/bin/skype'<br />
<br />
I noticed that the newly created user is able to read some of the files in my home directory because the permissions were a+r, so I changed them manually to a-r u+r and changed umask from 022 to 066.<br />
<br />
In order to restrict user "skype" accessing your external drive mounted in {{ic|/media/data}} for instance, make sure first that "skype" does not belong to group "users" (if you used the default group "skype", everything should be fine), then change the accesses on the mount point:<br />
# chown :users /media/data<br />
# chmod o-rwx /media/data<br />
This way, it is ensured that only the owner (normally "root") and "users" can access the specified directory tree while the others, including "skype", will be forbidden.<br />
<br />
==Skype Sound==<br />
Skype supports [[PulseAudio]] since version 2.1 and [[ALSA]] since version 2.0. Earlier versions support only the deprecated [[OSS]].<br />
<br />
===Skype PulseAudio Sound (2.1+)===<br />
Sound should work out of the box, if not you can select another input using pavucontrol (you may have to install it first).<br />
<br />
If you are on x86_64 and use the multilib {{Pkg|skype}} package, you also need {{Pkg|lib32-libpulse}}.<br />
<br />
===Skype ALSA Sound (2.0+)===<br />
Sound should work out of the box, if not you can select a sound device to use in Skype options. If you have problems with Skype blocking your sound device, you only need to add the following to your {{ic|~/.asoundrc}}<br />
pcm.dmixout {<br />
# Just pass this on to the system dmix<br />
type plug<br />
slave {<br />
pcm "dmix"<br />
}<br />
}<br />
then you can start Skype as normal, go to the audio options and select dmixout as your speaker- and ringingdevice.<br />
<br />
===Skype-OSS Sound (Pre-2.0)===<br />
If you have a recent version of Skype, this will not work and is not needed, look at the "important notes" on start of this page.<br />
Option B is preferred over other options.<br />
With option B you can use Skype AND let other programs play sound too.<br />
With option C you can do that too, but option B is way easier to set up.<br />
<br />
An OSS compatible version is available from [http://www.mediafire.com/?2ydhmj4yo3i here]. Then download the PKGBUILD for x86-64 users form [https://aur.archlinux.org/packages.php?ID=18312 here.] Correct the md5sum in the PKGBUILD, and also install {{Pkg|lib32-libxinerama}} (for x86-64 users). Finally, run<br />
$ makepkg -s<br />
to create the pacman installable package.<br />
====A. With OSS or Kernel OSS emulation for ALSA====<br />
Start Skype and make sure no other program is using your soundcard.<br />
If you want to use Skype AND let another program play sound too, look at option B instead.<br />
<br />
====B. Making ALSA + dMix work for Skype====<br />
First of all, we need to install the {{Pkg|alsa-oss}} package with [[pacman]]:<br />
# pacman -S alsa-oss<br />
<br />
Add the following to {{ic|~/.asoundrc}}. If the file does not exist yet, just create it! (Many thanks to Lorenzo Colitti for figuring this out!)<br />
<br />
# .asoundrc to use skype at the same time as other audio apps like xmms<br />
#<br />
# Successfully tested on an IBM x40 with i810_audio using Linux 2.6.15 and<br />
# Debian unstable with skype 1.2.0.18-API. No sound daemons (asound, esd, etc.)<br />
# running. However, YMMV.<br />
#<br />
# For background, see:<br />
#<br />
# https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1228<br />
# https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1224<br />
#<br />
# (C) 2006-06-03 Lorenzo Colitti - http://www.colitti.com/lorenzo/<br />
# Licensed under the GPLv2 or later<br />
<br />
pcm.skype {<br />
type asym<br />
playback.pcm "skypeout"<br />
capture.pcm "skypein"<br />
}<br />
<br />
pcm.skypein {<br />
# Convert from 8-bit unsigned mono (default format set by aoss when<br />
# /dev/dsp is opened) to 16-bit signed stereo (expected by dsnoop)<br />
#<br />
# We cannot just use a "plug" plugin because although the open will<br />
# succeed, the buffer sizes will be wrong and we will hear no sound at<br />
# all.<br />
type route<br />
slave {<br />
pcm "skypedsnoop"<br />
format S16_LE<br />
}<br />
ttable {<br />
0 {0 0.5}<br />
1 {0 0.5}<br />
}<br />
}<br />
<br />
pcm.skypeout {<br />
# Just pass this on to the system dmix<br />
type plug<br />
slave {<br />
pcm "dmix"<br />
}<br />
}<br />
<br />
pcm.skypedsnoop {<br />
type dsnoop<br />
ipc_key 1133<br />
slave {<br />
# "Magic" buffer values to get skype audio to work<br />
# If these are not set, opening /dev/dsp succeeds but no sound<br />
# will be heard. According to the ALSA developers this is due<br />
# to skype abusing the OSS API.<br />
pcm "hw:0,0"<br />
period_size 256<br />
periods 16<br />
buffer_size 16384<br />
}<br />
bindings {<br />
0 0<br />
}<br />
}<br />
<br />
If you get the error message :<br />
<br />
The dmix plugin supports only playback stream<br />
<br />
then add the following to {{ic|.asoundrc}}:<br />
<br />
pcm.asymed {<br />
type asym<br />
playback.pcm "dmix"<br />
capture.pcm "dsnoop"<br />
}<br />
<br />
pcm.!default {<br />
type plug<br />
slave.pcm "asymed"<br />
}<br />
<br />
<br />
Now run Skype in this way each time you want to use it:<br />
ALSA_OSS_PCM_DEVICE="skype" aoss skype<br />
<br />
Optionally you can make a script to start Skype:<br />
<br />
As root, create the file: {{ic|/usr/bin/askype}}<br />
<br />
# Little script to run Skype correctly using the modified .asoundrc<br />
# See: http://wiki.archlinux.org/index.php/Skype for more information!<br />
#<br />
# Questions/Remarks: profox@debianbox.be<br />
<br />
ALSA_OSS_PCM_DEVICE="skype" aoss skype<br />
<br />
Now make sure every user is able to execute the file:<br />
# chmod a+x /usr/bin/askype<br />
<br />
You can also fix the menu entry so you can start Skype from the your window manager's menu:<br />
<br />
Edit the file: {{ic|/usr/share/applications/skype.desktop}}<br />
<br />
[Desktop Entry]<br />
Name=Skype<br />
Comment=P2P software for high-quality voice communication<br />
Exec=askype<br />
Icon=skype.png<br />
Terminal=0<br />
Type=Application<br />
Encoding=UTF-8<br />
Categories=Network;Application;<br />
<br />
Sometimes it takes a while for Skype to start up but once it is loaded it should work ok!<br />
<br />
====C. Using OSS emulation with oss2jack====<br />
{{AUR|oss2jack}} is another way to have OSS emulation without using ALSA directly. Instead, oss2jack creates a OSS device that forwards everything to JACK (JACK Audio Connection Kit), which in turn mixes, then outputs to the standard ALSA device. <br />
<br />
==Skype plugin for Pidgin==<br />
<br />
See [[Pidgin#Skype plugin]].<br />
<br />
==Problems==<br />
<br />
===Skype crashes immediately===<br />
Try creating the directory<br />
~/.Skype/Logs<br />
<br />
===Skype crashes shortly after login===<br />
If Skype crashes shortly after logging in, changing the rights for {{ic|libpulse.so.0.12.4}} (minor version might differ) and {{ic|libpulse-simple.so.0.0.3}} might fix the issue.[https://bugs.launchpad.net/ubuntu/+source/ia32-libs/+bug/646862/comments/14]<br />
<br />
# cd /usr/lib<br />
# chmod ugo-r libpulse.so.0.12.*<br />
# chmod ugo-r libpulse-simple.so.0.0.3<br />
<br />
64bit users might have to cd to {{ic|/usr/lib32}} instead.<br />
<br />
===I can receive multiple audio streams, but I can only send one===<br />
Skype can send and receive audio and I still hear other sounds playing from other applications, but I cannot record my microphone with other applications. That is because Skype or aoss blocks the audio input for itself.<br />
<br />
===No video with GSPCA webcams===<br />
For i686, install {{Pkg|v4l-utils}}, userspace tools and conversion library for Video 4 Linux, and run Skype with<br />
<br />
LD_PRELOAD=/usr/lib/libv4l/v4l1compat.so skype<br />
<br />
to start Skype with v4l1 compatibility.<br />
<br />
For x86_64, install {{Pkg|lib32-v4l-utils}} from [multilib] repository and run Skype with<br />
<br />
LD_PRELOAD=/usr/lib32/libv4l/v4l1compat.so skype<br />
<br />
To make it running from DE menus and independent of Skype updates, you can add alias (e.g. in {{ic|~/.bashrc}}):<br />
<br />
alias skype='LD_PRELOAD=/usr/libxx/libv4l/v4l1compat.so skype'<br />
<br />
where `libxx' should be edited as appropriate.<br />
<br />
===No video with Compiz===<br />
Try this<br />
<br />
$ XLIB_SKIP_ARGB_VISUALS=1 skype<br />
<br />
===Skype does not use my GTK theme, even though other QT apps do===<br />
Recent versions of Skype allow you to change the theme via the Options menu. However, selecting the GTK+ option may not work properly. This is probably because you do not have a 32-bit theme engine installed. Try to find the engine your theme uses in the multilib repository or the [[AUR]]. Once installed, it will still not work unless you have a 32-bit version of GConf installed. You could build and install {{AUR|lib32-gconf}} if desired, but there is an easier workaround. First, create or edit {{ic|~/.gtkrc-2.0}} so that it contains the following line:<br />
<br />
$ gtk-theme-name = "My Theme"<br />
<br />
Replace My Theme by the name of your theme, but leave the quotes. Second, run Skype like this:<br />
<br />
$ export GTK2_RC_FILES="/etc/gtk-2.0/gtkrc:$HOME/.gtkrc-2.0"<br />
$ skype<br />
<br />
The GTK+ theme should now appear correctly. You can make this permanent either by running Skype from a script containing the above 2 lines, or by exporting GTK2_RC_FILES in {{ic|~/.xprofile}} or {{ic|~/.xinitrc}}, depending on how you start X.<br />
<br />
If you cannot change the theme in the Options menu, run Skype using the following command:<br />
<br />
$ /usr/bin/skype --disable-cleanlooks -style GTK<br />
<br />
If you wish menus within desktop environments to load Skype with a GTK theme by default then modify the 'Exec' line of {{ic|/usr/share/applications/skype.desktop}} so that it reads:<br />
<br />
$ Exec=/usr/bin/skype --disable-cleanlooks -style GTK<br />
<br />
Similarly if you have set Skype to autostart then modify {{ic|~/.config/autostart/skype.desktop}} in the same way.<br />
<br />
===The microphone does not work===<br />
Run amixer,<br />
<br />
$ amixer<br />
<br />
and check if you have an output for '''Capture''' similar to the one below.<br />
<br />
Simple mixer control 'Capture',0<br />
Capabilities: cvolume cswitch penum<br />
Capture channels: Front Left - Front Right<br />
Limits: Capture 0 - 15<br />
Front Left: Capture 8 [53%] [12.00dB] [on]<br />
Front Right: Capture 8 [53%] [12.00dB] [on]<br />
<br />
If your output is similar, your microphone is working just fine, and the issue is either hardware related (broken microphone) or your volume needs to be checked. If you do not have an output similar to the one above or, more specifically, if both '''Front Left''' and '''Front Right''' are 0% or show an '''[off]''' tag at the end, then your microphone settings need to be rectified.<br />
<br />
In either case, try to run:<br />
<br />
$ alsamixer<br />
<br />
and press '''F5''' to show all channels. Using the arrow keys navigate all the way to the end and increase '''Capture'''. If you do not see a left and right channel for '''Capture''', press the space bar. Doing this turns the left and right channels on. Check that '''Input Source''' is set to the correct value (e.g. ''[Front Mic]''): navigate through the values with up and down arrow keys. If your microphone is an array built into your monitor, or you have a similar setup, make sure to increase the volume for the '''Digital''' column too. If you have multiple microphones, you may have to play around with the '''Mic Jack''' channel to get your desired setting.<br />
<br />
You may want to save your mixer settings with:<br />
<br />
# alsactl -f /var/lib/alsa/asound.state store<br />
<br />
===No incoming video stream===<br />
This might be related to Cairo dock, though I am not sure.<br />
You need to start skype with:<br />
<br />
export XLIB_SKIP_ARGB_VISUALS=1 && skype<br />
<br />
===Low sound in Skype, but works everywhere else===<br />
If you are sure your microphone is configured correct in ALSA (try recording with a 3rd-party-utility to determent whether it is an ALSA, or Skype problem), it is most likely because Skype is controlling your volume levels. Simply disable this feature in the voice settings page in the Skype configuration window.<br />
<br />
This may also help if your microphone input is automatically lowered until 0.<br />
<br />
===Monster/low-octave "growling" distortion over mic===<br />
Some users with newer kernels are experiencing a monster-like growling distortion of their sound stream on the other end of Skype. This can be fixed by creating a dummy ALSA device or by removing {{ic|~/.Skype/shared.xml}}. See https://bbs.archlinux.org/viewtopic.php?pid=819500#p819500 for more information.<br />
<br />
===Skype can only see pulseaudio, but not ALSA devices===<br />
<br />
Turn PulseAudio autospawn off, normally: $ echo "autospawn = no" > ~/.pulse/client.conf<br />
Kill PulseAudio: $ killall pulseaudio<br />
Shut down and restart Skype<br />
<br />
===Crackling / Noisy sound (mainly using 64-bit OS) ===<br />
<br />
Edit {{ic|/etc/pulse/default.pa}} and change the following line<br />
<br />
load-module module-udev-detect<br />
<br />
to<br />
<br />
load-module module-udev-detect tsched=0<br />
<br />
See also: [[PulseAudio#Glitches.2C_skips_or_crackling]].<br />
<br />
=== Problem with Audio Playback on x86_64 ===<br />
<br />
See [[Pulseaudio#Skype (x86_64 only)]], even if you are not using PulseAudio.<br />
<br />
=== Skype sounds stops media player or other sound sources === <br />
<br />
You can try commenting out following modules in /etc/pulse/default.pa <br />
#module-cork-music-on-phone<br />
#module-role-cork<br />
<br />
If that doesn't help, you can try changing flat-volumes to no in /etc/pulse/daemon.conf.<br />
flat-volumes = no</div>Giselherhttps://wiki.archlinux.org/index.php?title=PulseAudio&diff=211428PulseAudio2012-06-28T10:09:12Z<p>Giselher: revert change: wrong articel</p>
<hr />
<div>[[Category:Audio/Video]]<br />
[[cs:PulseAudio]]<br />
[[es:PulseAudio]]<br />
[[fr:PulseAudio]]<br />
[[it:PulseAudio]]<br />
[[pt:PulseAudio]]<br />
[[ru:PulseAudio]]<br />
[[tr:PulseAudio]]<br />
{{Article summary start}}<br />
{{Article summary text|'''PulseAudio''' is a general purpose sound server. For a list of features, see [[Wikipedia:PulseAudio#Features]].}}<br />
{{Article summary heading|Related Articles}}<br />
{{Article summary wiki|PulseAudio/Examples}}<br />
{{Article summary end}}<br />
<br />
==Installation==<br />
*Required PKG: {{Pkg|pulseaudio}}<br />
*Optional GUIs: {{Pkg|paprefs}} and {{Pkg|pavucontrol}}<br />
*Optional volume control via mapped keyboard keys: {{AUR|pulseaudio_ctl}}<br />
*Optional console mixer: {{AUR|pamixer-git}}<br />
*Optional system tray icon: {{AUR|pasystray-git}}<br />
<br />
{{Note| [http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/PerfectSetup#Should_users_be_in_the_.22audio.22_group.3F PulseAudio wiki] recommends that users should not be part of the "audio" group.}}<br />
<br />
==Running==<br />
{{Note|Pulseaudio requires dbus to function. This is very likely already added in the daemons array, if not consider adding it.}}<br />
{{Note|Most X11 environments start pulseaudio automatically with the X11 session.}}<br />
<br />
In the unlikely event that pulseaudio is not automatically called upon entering X, it can can be started with:<br />
$ pulseaudio --start<br />
<br />
{{Note|if you get the message {{ic|pulseaudio: error while loading shared libraries: libltdl.so.7: cannot open shared object file: No such file or directory}} you need to install {{pkg|libltdl}} }}<br />
<br />
PulseAudio can be stopped with:<br />
$ pulseaudio --kill<br />
<br />
==Equalizer==<br />
<br />
Newer pulseaudio versions have an intergrated 10-band equalizer system. In order to use the equalizer do the following:<br />
<br />
===Load equalizer sink module===<br />
<br />
$ pactl load-module module-equalizer-sink<br />
<br />
===Install and run the gui frontend===<br />
<br />
# pacman -S --needed python2-pyqt<br />
<br />
$ qpaeq<br />
<br />
===Load equalizer module on every boot===<br />
<br />
Edit the file {{ic|/etc/pulse/default.pa}} with your favorite editor and append the following lines:<br />
<br />
### Load the integrated pulseaudio equalizer module<br />
load-module module-equalizer-sink<br />
<br />
==Backend Configuration==<br />
===ALSA===<br />
*Recommended PKG: {{Pkg|pulseaudio-alsa}}<br />
*Optional PKGs: {{Pkg|lib32-libpulse}} and {{Pkg|lib32-alsa-plugins}}<br />
<br />
{{Note|Optional PKGs are needed only if running x86_64 and wanting to have sound for 32 bit programs (like Wine).}}<br />
<br />
For the applications that do not support PulseAudio and support ALSA it is '''recommended''' to install the PulseAudio plugin for ALSA. This package also contains the necessary {{ic|/etc/asound.conf}} for configuring ALSA to use PulseAudio.<br />
<br />
To prevent applications from using ALSA's OSS emulation and bypassing Pulseaudio (thereby preventing other applications from playing sound), make sure the module {{ic|snd_pcm_oss}} is not in the {{ic|MODULES}} array in {{ic|/etc/[[rc.conf]]}}. If it is currently loaded, disable it by executing:<br />
# rmmod snd_pcm_oss<br />
<br />
===OSS===<br />
There are multiple ways of making OSS-only programs play to PulseAudio:<br />
<br />
====osspd====<br />
Recommended PKG: {{Pkg|ossp}}<br />
<br />
Start osspd with:<br />
rc.d start osspd<br />
<br />
Afterwards, add it to DAEMONS in rc.conf.<br />
<br />
====padsp wrapper====<br />
Programs using OSS can work with PulseAudio by starting it with padsp:<br />
<br />
$ padsp OSSprogram<br />
A few examples:<br />
$ padsp aumix<br />
$ padsp sox foo.wav -t ossdsp /dev/dsp<br />
<br />
One can also rename the program OSSprogram-bin and replace it with a script like this: <br />
{{hc|/usr/bin/OSSProgram|<nowiki><br />
#!/bin/sh<br />
if test -x /usr/bin/padsp; then<br />
exec /usr/bin/padsp /usr/bin/OSSprogram-bin "$@"<br />
else<br />
exec /usr/bin/OSSprogram "$@"<br />
fi<br />
</nowiki>}}<br />
<br />
===GStreamer===<br />
To make [[GStreamer]] use PulseAudio, execute {{ic|gstreamer-properties}} (part of ''gnome-media'' package) and select ''PulseAudio Sound Server'' in both Audio Input and Output. Alternatively, this can be done by setting the gconf variables {{ic|/system/gstreamer/0.10/default/audiosink}} to ''pulsesink'' and {{ic|/system/gstreamer/0.10/default/audiosrc}} to ''pulsesrc'':<br />
$ gconftool-2 -t string --set /system/gstreamer/0.10/default/audiosink pulsesink<br />
$ gconftool-2 -t string --set /system/gstreamer/0.10/default/audiosrc pulsesrc<br />
<br />
Some applications (like Rhythmbox) ignore the ''audiosink'' property, but rely instead on ''musicaudiosink'', which cannot be configured using {{ic|gstreamer-properties}} but needs to be manually set using {{ic|gconf-editor}} or the {{ic|gconftool-2}}:<br />
$ gconftool-2 -t string --set /system/gstreamer/0.10/default/musicaudiosink pulsesink<br />
<br />
===OpenAL===<br />
OpenAL Soft should use PulseAudio by default, but can be explicitly configured to do so: {{hc|/etc/openal/alsoft.conf|2=drivers=pulse,alsa}}<br />
<br />
===libao===<br />
Edit the libao configuration file:<br />
{{hc|/etc/libao.conf|2=default_driver=pulse}}<br />
<br />
===ESD===<br />
PulseAudio is a drop-in replacement for the enlightened sound daemon (ESD). While PulseAudio is running, ESD clients should be able to output to it without configuration.<br />
<br />
==Desktop Environments==<br />
===General X11===<br />
{{Note|As mentioned previously, PulseAudio is very likely launched automatically via either {{ic|/etc/X11/xinit/xinitrc.d/pulseaudio}} or the files in {{ic|/etc/xdg/autostart/}} if users have some DE installed.}}<br />
<br />
Check to see if PulseAudio is running:<br />
<br />
$ ps aux | grep pulse<br />
facade 1794 0.0 0.0 360464 6532 ? S<l 15:33 0:00 /usr/bin/pulseaudio --start<br />
facade 1827 0.0 0.0 68888 2608 ? S 15:33 0:00 /usr/lib/pulse/gconf-helper<br />
<br />
If Pulseaudio is not running and users are using X, the following will start PulseAudio with the needed the X11 plugins:<br />
$ start-pulseaudio-x11<br />
<br />
===GNOME===<br />
As of GNOME 3, GNOME fully integrates with PulseAudio and no extra configuration is needed.<br />
<br />
===KDE 3===<br />
PulseAudio is ''not'' a drop-in replacement for aRts. Users of KDE 3 cannot use PulseAudio. However note, recent versions of puleaudio may have eliminated the prohibition:<br />
<br />
See: http://www.pulseaudio.org/wiki/PerfectSetup KDE 3 uses the artsd sound server by default. However, artsd itself can be configured to use an Esound backend. Edit kcmartsrc (either in /etc/kde or /usr/share/config for global configuration or .kde/share/config to configure only one user) like this:<br />
<br />
[Arts]<br />
Arguments=\s-F 10 -S 4096 -a esd -n -s 1 -m artsmessage -c drkonqi -l 3 -f<br />
NetworkTransparent=true<br />
SuspendTime=1<br />
<br />
===KDE 4 and Qt4===<br />
PulseAudio, it will be used by KDE4/Qt4 applications. For more information see the [http://www.pulseaudio.org/wiki/KDE KDE page in the PulseAudio wiki].<br />
<br />
One useful tidbit from that page is to add {{ic|load-module module-device-manager}} to {{ic|/etc/pulse/default.pa}}.<br />
<br />
Additionally, the {{AUR|kdeplasma-addons-applets-veromix}} is available in the AUR as a KDE alternative to pavucontrol.<br />
<br />
===XFCE4===<br />
Applications running under XFCE4 can take advantage of Pulseaudio. To manage Pulseaudio settings you can use {{Pkg|pavucontrol}}.<br />
<br />
==Applications==<br />
===Audacious===<br />
[[Audacious]] natively supports PulseAudio. In order to use it, set Audacious Preferences -> Audio -> Current output plugin to 'PulseAudio Output Plugin'.<br />
<br />
===Java/OpenJDK 6===<br />
Create a wrapper for the java executable using padsp as seen on the [[Java#Java_sound_with_Pulseaudio|Java sound with Pulseaudio]] page.<br />
<br />
===Music Player Daemon (MPD)===<br />
[http://mpd.wikia.com/wiki/PulseAudio configure] [[MPD]] to use PulseAudio.<br />
<br />
===MPlayer===<br />
[[MPlayer]] natively supports PulseAudio output with the "{{ic|-ao pulse}}" option. It can also be configured to default to PulseAudio output, in {{ic|~/.mplayer/config}} for per-user, or {{ic|/etc/mplayer/mplayer.conf}} for system-wide:<br />
{{hc|/etc/mplayer/mplayer.conf|2=ao=pulse}}<br />
<br />
===Skype (x86_64 only)===<br />
Install {{Pkg|lib32-libpulse}}, otherwise the following error will occur when trying to initiate a call: "Problem with Audio Playback".<br />
<br />
==Troubleshooting==<br />
===No sound after install===<br />
====Bad configuration files====<br />
If after starting pulseaudio, the system outputs no sound, it may be necessary to delete the contents of {{ic|~/.pulse}}. Pulseaudio will automatically create new configuration files on its next start.<br />
<br />
====Flash Content====<br />
Since Adobe Flash does not directly support PulseAudio the recommended way is to [https://wiki.archlinux.org/index.php/PulseAudio#ALSA configure ALSA to use the virtual PulseAudio soundcard].<br />
<br />
Alternatively no sound from flash content may be fixed by installing {{AUR|libflashsupport-pulse}} from the AUR (not recommended as it seems to make the flash plugin crash rather frequently).<br />
<br />
{{Pkg|lib32-libpulse}} is another PKG users can consider if on a 64-bit Arch and using [multilib]'s flashplugin:<br />
<br />
# pacman -S lib32-libcanberra-pulse lib32-alsa-plugins<br />
<br />
====No cards====<br />
If PulseAudio starts, run {{ic|pacmd list}}. If no cards are reported, make sure that the ALSA devices are not in use:<br />
$ fuser -v /dev/snd/*<br />
$ fuser -v /dev/dsp<br />
<br />
Make sure any applications using the pcm or dsp files are shut down before restarting PulseAudio.<br />
<br />
====The only device shown is "dummy output"====<br />
This may be caused by different reasons, one of them being the .asoundrc file in $HOME is taking precedence over the systemwide /etc/asound.conf.<br />
<br />
The user file is modified also by the tool '''asoundconf''' or by its graphical variant '''asoundconf-gtk''' (the latter is named "Default sound card" in the menu) as soon as it runs. Prevent the effects of .asoundrc altogether by commenting the last line like this:<br />
<br />
#</home/<yourusername>/.asoundrc.asoundconf><br />
<br />
====KDE4====<br />
It may be that another output device set as preferred in phonon. Make sure that every setting reflects the preferred output device at the top, and check the playback streams tab in kmix to make sure that applications are using the device for output.<br />
<br />
====Muted audio device====<br />
If one experiences no audio output via any means while using ALSA, attempt to unmute the sound card. To do this, launch alsamixer and make sure each column has a green 00 under it (this can be toggled by pressing 'm')<br />
$ alsamixer -c 0<br />
<br />
===Bluetooth headset replay problems===<br />
Some user [https://bbs.archlinux.org/viewtopic.php?id=117420 report] huge delays or even no sound when the bluetooth connection does not send any data. This is due to an idle-suspend-module that puts the related sinks/sources automatically into suspend. As this can cause problems with headset, the responsible module can be deactivated. <br />
<br />
1. cp /etc/pulse/default.pa ~/.pulse/default.pa<br />
2. comment out the "load-module module-suspend-on-idle" line in ~/.pulse/default.pa<br />
3. pulseaudio -k && pulseaudio --start<br />
<br />
[http://robert.orzanna.de/2011/08/10/prevent-idle-suspend-with-a-bluetooth-headset-and-a2dp/ More information]<br />
<br />
===Automatically switch to Bluetooth or USB headset===<br />
Add the following to your /etc/pulse/default.pa:<br />
<br />
# automatically switch to newly-connected devices<br />
load-module module-switch-on-connect<br />
<br />
===Pulse overwrites ALSA settings===<br />
Pulseaudio usually overwrites the ALSA settings- for example set with alsamixer- at start up, even when the alsa daemon is loaded. Since there seems to be no other way to restrict this behaviour, a workaround is to restore the alsa settings again after pulseaudio had started. Add the following command to {{ic|.xinitrc}} {{ic|.bash_login}} or any other autostart file:<br />
<br />
restore_alsa() {<br />
while [ -z "`pidof pulseaudio`" ]; do<br />
sleep 0.5<br />
done<br />
alsactl -f /var/lib/alsa/asound.state restore <br />
}<br />
restore_alsa &<br />
<br />
===Daemon startup failed===<br />
Try resetting PulseAudio. To do that:<br />
$ pulseaudio --kill<br />
$ killall pulseaudio<br />
$ killall -9 pulseaudio<br />
$ rm -rf ~/.pulse*<br />
$ rm -rf /tmp/pulse*<br />
<br />
Afterwards, start PulseAudio again.<br />
<br />
===padevchooser===<br />
If one cannot launch the PulseAudio Device Chooser, first (re)start the Avahi daemon as follows:<br />
$ rc.d restart avahi-daemon<br />
<br />
===Glitches, skips or crackling===<br />
The PulseAudio sound server uses a timer-based audio scheduling instead of the traditional interrupt-driven approach. Timer-based scheduling may expose issues in some ALSA drivers. To turn timer-based scheduling off, replace the line:<br />
load-module module-udev-detect <br />
in {{ic|/etc/pulse/default.pa}} by:<br />
load-module module-udev-detect tsched=0<br />
Then restart the PulseAudio server.<br />
<br />
===Choppy sound===<br />
Choppy sound in pulsaudio can result from wrong settings for the sample rate in {{Ic|/etc/pulse/daemon.conf}}. Try changing the line <br />
; default-sample-rate = 44100<br />
to <br />
default-sample-rate = 48000<br />
and restart the PulseAudio server.<br />
<br />
If one experiences choppy sound in applications using openAL, change the sample rate in /etc/openal/alsoft.conf:<br />
frequency = 48000<br />
<br />
===Volume adjustment does not work properly===<br />
Check:<br />
{{ic|/usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common}}<br />
<br />
If the volume does not appear to increment/decrement properly using {{ic|alsamixer}} or {{ic|amixer}}, it may be due to pulseaudio having a larger number of increments (65537 to be exact). Try using larger values when changing volume (e.g. {{ic|amixer set Master 655+}}).<br />
<br />
===Volume gets louder every time a new application is started===<br />
Per default, it seems as if changing the volume in an application sets the global system volume to that level instead of only affecting the respective application. Applications setting their volume on startup will therefore cause the system volume to "jump".<br />
<br />
Fix this by uncommenting <br />
flat-volumes = no<br />
in<br />
/etc/pulse/daemon.conf<br />
and then restarting PulseAudio by executing<br />
pulseaudio --kill && pulseaudio --start<br />
<br />
When Pulse comes back after a few seconds, applications will not alter the global system volume anymore but have their own volume level again.<br />
<br />
{{Note|A previously installed and removed pulseaudio-equalizer may leave behind remnants of the setup in {{Ic|$HOME/.pulse/default.pa}} which can also cause maximized volume trouble. Comment that out as needed.}}<br />
<br />
===No mic on ThinkPad T400/T500/T420===<br />
Run<br />
alsamixer -c 0<br />
Maximize the volume of/unmute the "Internal Mic".<br />
<br />
Once you see the device with<br />
arecord -l<br />
you might still need to adjust the settings. The microphone and the audio jack are duplexed. Set the configuration of the internal audio in pavucontrol to ''Analog Stereo Duplex''.<br />
<br />
===No mic input on Acer Aspire One===<br />
Install pavucontrol, unlink the microphone channels and turn down the left one to 0.<br />
Reference: http://getsatisfaction.com/jolicloud/topics/deaf_internal_mic_on_acer_aspire_one#reply_2108048<br />
<br />
===Sound output is only mono on M-Audio Audiophile 2496 sound card===<br />
Add the following to /etc/pulseaudio/default.pa:<br />
load-module module-alsa-sink sink_name=delta_out device=hw:M2496 format=s24le channels=10 channel_map=left,right,aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7<br />
load-module module-alsa-source source_name=delta_in device=hw:M2496 format=s24le channels=12 channel_map=left,right,aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7,aux8,aux9<br />
set-default-sink delta_out<br />
set-default-source delta_in<br />
<br />
===Static Noise in Microphone Recording===<br />
If we are getting static noise in skype, gnome-sound-recorder, arecord, etc.'s recordings then the sound card samplerate is incorrect. That is why there is static noise in linux microphone recordings. To fix this We need to set sample-rate in /etc/pulse/daemon.conf for the sound hardware.<br />
<br />
====1. Determine soundcards in the system====<br />
This requires alsa-utils and related packages to be installed:<br />
$ arecord --list-devices<br />
<br />
output:<br />
**** List of CAPTURE Hardware Devices ****<br />
card 0: Intel [HDA Intel], device 0: ALC888 Analog [ALC888 Analog]<br />
Subdevices: 1/1<br />
Subdevice #0: subdevice #0<br />
card 0: Intel [HDA Intel], device 2: ALC888 Analog [ALC888 Analog]<br />
Subdevices: 1/1<br />
Subdevice #0: subdevice #0<br />
<br />
soundcard is hw:0,0<br />
<br />
====2. Determine sampling-rate of the sound card====<br />
arecord -f dat -r 60000 -D hw:0,0 -d 5 test.wav<br />
<br />
output:<br />
"Recording WAVE 'test.wav' : Signed 16 bit Little Endian, Rate 60000 Hz, Stereo<br />
Warning: rate is not accurate (requested = 60000Hz, '''got = 96000Hz''')<br />
please, try the plug plugin<br />
<br />
observe, the '''got = 96000Hz''', this is the max sample-rate of our card.<br />
<br />
====3. Setting the soundcard's sampling rate into pulse audio configuration====<br />
the default sample-rate in pulseaudio is<br />
grep "sample-rate" /etc/pulse/daemon.conf<br />
<br />
output:<br />
; default-sample-rate = 44100<br />
<br />
It is 44100 and is disabled. Let us set our sound card's settings into pulseaudio configuation file<br />
su -c "sed 's/; default-sample-rate = 44100/default-sample-rate = 96000/g' -i /etc/pulse/daemon.conf"<br />
<br />
Let us verify the changes to deamon.conf<br />
grep "sample-rate" /etc/pulse/daemon.conf <br />
output:<br />
default-sample-rate = 96000<br />
and it is done.<br />
<br />
====4. Restart pulseaudio to apply the new settings====<br />
pulseaudio --kill<br />
pulseaudio --start<br />
<br />
====5. Finally check by recording and playing it back====<br />
Let us record some voice using mic for say 10 seconds. Make sure the mic is not muted and all<br />
arecord -f cd -d 10 test-mic.wav<br />
<br />
After 10 seconds, let us play the recording...<br />
aplay test-mic.wav<br />
<br />
Now hopefully, there is no static noise in microphone recording anymore.<br />
<br />
=== My Bluetooth device is paired but does not play any sound ===<br />
[[Bluetooth#My_device_is_paired_but_no_sound_is_played_from_it|See the article in Bluetooth section]]<br />
<br />
=== Subwoofer stops working after end of every song ===<br />
Known issue: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/494099<br />
<br />
To fix this, must edit: {{ic|/etc/pulse/daemon.conf}} and enable {{ic|enable-lfe-remixing}} :<br />
{{hc|/etc/pulse/daemon.conf|<nowiki><br />
enable-lfe-remixing = yes<br />
</nowiki>}}<br />
<br />
=== Pulseaudio uses wrong microphone ===<br />
If Pulseaudio uses the wrong microphone, and changing the Input Device with Pavucontrol did not help, take a look at alsamixer. It seems that Pavucontrol does not always set the input source correctly.<br><br />
Run:<br />
<br />
$ alsamixer<br />
<br />
press F6 and choose your sound card, e.g. HDA Intel. Now press F5 to display all items. Try to find the item: {{ic|Input Source}}. With the up/down arrow keys you are able to change the input source. <br><br />
Now try if the correct microphone is used for recording.<br />
<br />
==External links==<br />
*[http://www.pulseaudio.org/wiki/PerfectSetup http://www.pulseaudio.org/wiki/PerfectSetup] - A good guide to make your configuration perfect<br />
*[http://www.alsa-project.org/main/index.php/Asoundrc http://www.alsa-project.org/main/index.php/Asoundrc] - Alsa wiki on .asoundrc<br />
*[http://www.pulseaudio.org/ http://www.pulseaudio.org/] - PulseAudio official site<br />
*[http://www.pulseaudio.org/wiki/FAQ http://www.pulseaudio.org/wiki/FAQ] - PulseAudio FAQ</div>Giselherhttps://wiki.archlinux.org/index.php?title=PulseAudio&diff=211427PulseAudio2012-06-28T10:08:23Z<p>Giselher: </p>
<hr />
<div>[[Category:Audio/Video]]<br />
[[cs:PulseAudio]]<br />
[[es:PulseAudio]]<br />
[[fr:PulseAudio]]<br />
[[it:PulseAudio]]<br />
[[pt:PulseAudio]]<br />
[[ru:PulseAudio]]<br />
[[tr:PulseAudio]]<br />
{{Article summary start}}<br />
{{Article summary text|'''PulseAudio''' is a general purpose sound server. For a list of features, see [[Wikipedia:PulseAudio#Features]].}}<br />
{{Article summary heading|Related Articles}}<br />
{{Article summary wiki|PulseAudio/Examples}}<br />
{{Article summary end}}<br />
<br />
==Installation==<br />
*Required PKG: {{Pkg|pulseaudio}}<br />
*Optional GUIs: {{Pkg|paprefs}} and {{Pkg|pavucontrol}}<br />
*Optional volume control via mapped keyboard keys: {{AUR|pulseaudio_ctl}}<br />
*Optional console mixer: {{AUR|pamixer-git}}<br />
*Optional system tray icon: {{AUR|pasystray-git}}<br />
<br />
{{Note| [http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/PerfectSetup#Should_users_be_in_the_.22audio.22_group.3F PulseAudio wiki] recommends that users should not be part of the "audio" group.}}<br />
<br />
==Running==<br />
{{Note|Pulseaudio requires dbus to function. This is very likely already added in the daemons array, if not consider adding it.}}<br />
{{Note|Most X11 environments start pulseaudio automatically with the X11 session.}}<br />
<br />
In the unlikely event that pulseaudio is not automatically called upon entering X, it can can be started with:<br />
$ pulseaudio --start<br />
<br />
{{Note|if you get the message {{ic|pulseaudio: error while loading shared libraries: libltdl.so.7: cannot open shared object file: No such file or directory}} you need to install {{pkg|libltdl}} }}<br />
<br />
PulseAudio can be stopped with:<br />
$ pulseaudio --kill<br />
<br />
==Equalizer==<br />
<br />
Newer pulseaudio versions have an intergrated 10-band equalizer system. In order to use the equalizer do the following:<br />
<br />
===Load equalizer sink module===<br />
<br />
$ pactl load-module module-equalizer-sink<br />
<br />
===Install and run the gui frontend===<br />
<br />
# pacman -S --needed python2-pyqt<br />
<br />
$ qpaeq<br />
<br />
===Load equalizer module on every boot===<br />
<br />
Edit the file {{ic|/etc/pulse/default.pa}} with your favorite editor and append the following lines:<br />
<br />
### Load the integrated pulseaudio equalizer module<br />
load-module module-equalizer-sink<br />
<br />
==Backend Configuration==<br />
===ALSA===<br />
*Recommended PKG: {{Pkg|pulseaudio-alsa}}<br />
*Optional PKGs: {{Pkg|lib32-libpulse}} and {{Pkg|lib32-alsa-plugins}}<br />
<br />
{{Note|Optional PKGs are needed only if running x86_64 and wanting to have sound for 32 bit programs (like Wine).}}<br />
<br />
For the applications that do not support PulseAudio and support ALSA it is '''recommended''' to install the PulseAudio plugin for ALSA. This package also contains the necessary {{ic|/etc/asound.conf}} for configuring ALSA to use PulseAudio.<br />
<br />
To prevent applications from using ALSA's OSS emulation and bypassing Pulseaudio (thereby preventing other applications from playing sound), make sure the module {{ic|snd_pcm_oss}} is not in the {{ic|MODULES}} array in {{ic|/etc/[[rc.conf]]}}. If it is currently loaded, disable it by executing:<br />
# rmmod snd_pcm_oss<br />
<br />
===OSS===<br />
There are multiple ways of making OSS-only programs play to PulseAudio:<br />
<br />
====osspd====<br />
Recommended PKG: {{Pkg|ossp}}<br />
<br />
Start osspd with:<br />
rc.d start osspd<br />
<br />
Afterwards, add it to DAEMONS in rc.conf.<br />
<br />
====padsp wrapper====<br />
Programs using OSS can work with PulseAudio by starting it with padsp:<br />
<br />
$ padsp OSSprogram<br />
A few examples:<br />
$ padsp aumix<br />
$ padsp sox foo.wav -t ossdsp /dev/dsp<br />
<br />
One can also rename the program OSSprogram-bin and replace it with a script like this: <br />
{{hc|/usr/bin/OSSProgram|<nowiki><br />
#!/bin/sh<br />
if test -x /usr/bin/padsp; then<br />
exec /usr/bin/padsp /usr/bin/OSSprogram-bin "$@"<br />
else<br />
exec /usr/bin/OSSprogram "$@"<br />
fi<br />
</nowiki>}}<br />
<br />
===GStreamer===<br />
To make [[GStreamer]] use PulseAudio, execute {{ic|gstreamer-properties}} (part of ''gnome-media'' package) and select ''PulseAudio Sound Server'' in both Audio Input and Output. Alternatively, this can be done by setting the gconf variables {{ic|/system/gstreamer/0.10/default/audiosink}} to ''pulsesink'' and {{ic|/system/gstreamer/0.10/default/audiosrc}} to ''pulsesrc'':<br />
$ gconftool-2 -t string --set /system/gstreamer/0.10/default/audiosink pulsesink<br />
$ gconftool-2 -t string --set /system/gstreamer/0.10/default/audiosrc pulsesrc<br />
<br />
Some applications (like Rhythmbox) ignore the ''audiosink'' property, but rely instead on ''musicaudiosink'', which cannot be configured using {{ic|gstreamer-properties}} but needs to be manually set using {{ic|gconf-editor}} or the {{ic|gconftool-2}}:<br />
$ gconftool-2 -t string --set /system/gstreamer/0.10/default/musicaudiosink pulsesink<br />
<br />
===OpenAL===<br />
OpenAL Soft should use PulseAudio by default, but can be explicitly configured to do so: {{hc|/etc/openal/alsoft.conf|2=drivers=pulse,alsa}}<br />
<br />
===libao===<br />
Edit the libao configuration file:<br />
{{hc|/etc/libao.conf|2=default_driver=pulse}}<br />
<br />
===ESD===<br />
PulseAudio is a drop-in replacement for the enlightened sound daemon (ESD). While PulseAudio is running, ESD clients should be able to output to it without configuration.<br />
<br />
==Desktop Environments==<br />
===General X11===<br />
{{Note|As mentioned previously, PulseAudio is very likely launched automatically via either {{ic|/etc/X11/xinit/xinitrc.d/pulseaudio}} or the files in {{ic|/etc/xdg/autostart/}} if users have some DE installed.}}<br />
<br />
Check to see if PulseAudio is running:<br />
<br />
$ ps aux | grep pulse<br />
facade 1794 0.0 0.0 360464 6532 ? S<l 15:33 0:00 /usr/bin/pulseaudio --start<br />
facade 1827 0.0 0.0 68888 2608 ? S 15:33 0:00 /usr/lib/pulse/gconf-helper<br />
<br />
If Pulseaudio is not running and users are using X, the following will start PulseAudio with the needed the X11 plugins:<br />
$ start-pulseaudio-x11<br />
<br />
===GNOME===<br />
As of GNOME 3, GNOME fully integrates with PulseAudio and no extra configuration is needed.<br />
<br />
===KDE 3===<br />
PulseAudio is ''not'' a drop-in replacement for aRts. Users of KDE 3 cannot use PulseAudio. However note, recent versions of puleaudio may have eliminated the prohibition:<br />
<br />
See: http://www.pulseaudio.org/wiki/PerfectSetup KDE 3 uses the artsd sound server by default. However, artsd itself can be configured to use an Esound backend. Edit kcmartsrc (either in /etc/kde or /usr/share/config for global configuration or .kde/share/config to configure only one user) like this:<br />
<br />
[Arts]<br />
Arguments=\s-F 10 -S 4096 -a esd -n -s 1 -m artsmessage -c drkonqi -l 3 -f<br />
NetworkTransparent=true<br />
SuspendTime=1<br />
<br />
===KDE 4 and Qt4===<br />
PulseAudio, it will be used by KDE4/Qt4 applications. For more information see the [http://www.pulseaudio.org/wiki/KDE KDE page in the PulseAudio wiki].<br />
<br />
One useful tidbit from that page is to add {{ic|load-module module-device-manager}} to {{ic|/etc/pulse/default.pa}}.<br />
<br />
Additionally, the {{AUR|kdeplasma-addons-applets-veromix}} is available in the AUR as a KDE alternative to pavucontrol.<br />
<br />
===XFCE4===<br />
Applications running under XFCE4 can take advantage of Pulseaudio. To manage Pulseaudio settings you can use {{Pkg|pavucontrol}}.<br />
<br />
==Applications==<br />
===Audacious===<br />
[[Audacious]] natively supports PulseAudio. In order to use it, set Audacious Preferences -> Audio -> Current output plugin to 'PulseAudio Output Plugin'.<br />
<br />
===Java/OpenJDK 6===<br />
Create a wrapper for the java executable using padsp as seen on the [[Java#Java_sound_with_Pulseaudio|Java sound with Pulseaudio]] page.<br />
<br />
===Music Player Daemon (MPD)===<br />
[http://mpd.wikia.com/wiki/PulseAudio configure] [[MPD]] to use PulseAudio.<br />
<br />
===MPlayer===<br />
[[MPlayer]] natively supports PulseAudio output with the "{{ic|-ao pulse}}" option. It can also be configured to default to PulseAudio output, in {{ic|~/.mplayer/config}} for per-user, or {{ic|/etc/mplayer/mplayer.conf}} for system-wide:<br />
{{hc|/etc/mplayer/mplayer.conf|2=ao=pulse}}<br />
<br />
===Skype (x86_64 only)===<br />
Install {{Pkg|lib32-libpulse}}, otherwise the following error will occur when trying to initiate a call: "Problem with Audio Playback".<br />
<br />
==Troubleshooting==<br />
===No sound after install===<br />
====Bad configuration files====<br />
If after starting pulseaudio, the system outputs no sound, it may be necessary to delete the contents of {{ic|~/.pulse}}. Pulseaudio will automatically create new configuration files on its next start.<br />
<br />
====Flash Content====<br />
Since Adobe Flash does not directly support PulseAudio the recommended way is to [https://wiki.archlinux.org/index.php/PulseAudio#ALSA configure ALSA to use the virtual PulseAudio soundcard].<br />
<br />
Alternatively no sound from flash content may be fixed by installing {{AUR|libflashsupport-pulse}} from the AUR (not recommended as it seems to make the flash plugin crash rather frequently).<br />
<br />
{{Pkg|lib32-libpulse}} is another PKG users can consider if on a 64-bit Arch and using [multilib]'s flashplugin:<br />
<br />
# pacman -S lib32-libcanberra-pulse lib32-alsa-plugins<br />
<br />
====No cards====<br />
If PulseAudio starts, run {{ic|pacmd list}}. If no cards are reported, make sure that the ALSA devices are not in use:<br />
$ fuser -v /dev/snd/*<br />
$ fuser -v /dev/dsp<br />
<br />
Make sure any applications using the pcm or dsp files are shut down before restarting PulseAudio.<br />
<br />
====The only device shown is "dummy output"====<br />
This may be caused by different reasons, one of them being the .asoundrc file in $HOME is taking precedence over the systemwide /etc/asound.conf.<br />
<br />
The user file is modified also by the tool '''asoundconf''' or by its graphical variant '''asoundconf-gtk''' (the latter is named "Default sound card" in the menu) as soon as it runs. Prevent the effects of .asoundrc altogether by commenting the last line like this:<br />
<br />
#</home/<yourusername>/.asoundrc.asoundconf><br />
<br />
====KDE4====<br />
It may be that another output device set as preferred in phonon. Make sure that every setting reflects the preferred output device at the top, and check the playback streams tab in kmix to make sure that applications are using the device for output.<br />
<br />
====Muted audio device====<br />
If one experiences no audio output via any means while using ALSA, attempt to unmute the sound card. To do this, launch alsamixer and make sure each column has a green 00 under it (this can be toggled by pressing 'm')<br />
$ alsamixer -c 0<br />
<br />
===Bluetooth headset replay problems===<br />
Some user [https://bbs.archlinux.org/viewtopic.php?id=117420 report] huge delays or even no sound when the bluetooth connection does not send any data. This is due to an idle-suspend-module that puts the related sinks/sources automatically into suspend. As this can cause problems with headset, the responsible module can be deactivated. <br />
<br />
1. cp /etc/pulse/default.pa ~/.pulse/default.pa<br />
2. comment out the "load-module module-suspend-on-idle" line in ~/.pulse/default.pa<br />
3. pulseaudio -k && pulseaudio --start<br />
<br />
[http://robert.orzanna.de/2011/08/10/prevent-idle-suspend-with-a-bluetooth-headset-and-a2dp/ More information]<br />
<br />
===Automatically switch to Bluetooth or USB headset===<br />
Add the following to your /etc/pulse/default.pa:<br />
<br />
# automatically switch to newly-connected devices<br />
load-module module-switch-on-connect<br />
<br />
===Pulse overwrites ALSA settings===<br />
Pulseaudio usually overwrites the ALSA settings- for example set with alsamixer- at start up, even when the alsa daemon is loaded. Since there seems to be no other way to restrict this behaviour, a workaround is to restore the alsa settings again after pulseaudio had started. Add the following command to {{ic|.xinitrc}} {{ic|.bash_login}} or any other autostart file:<br />
<br />
restore_alsa() {<br />
while [ -z "`pidof pulseaudio`" ]; do<br />
sleep 0.5<br />
done<br />
alsactl -f /var/lib/alsa/asound.state restore <br />
}<br />
restore_alsa &<br />
<br />
===Daemon startup failed===<br />
Try resetting PulseAudio. To do that:<br />
$ pulseaudio --kill<br />
$ killall pulseaudio<br />
$ killall -9 pulseaudio<br />
$ rm -rf ~/.pulse*<br />
$ rm -rf /tmp/pulse*<br />
<br />
Afterwards, start PulseAudio again.<br />
<br />
===padevchooser===<br />
If one cannot launch the PulseAudio Device Chooser, first (re)start the Avahi daemon as follows:<br />
$ rc.d restart avahi-daemon<br />
<br />
===Glitches, skips or crackling===<br />
The PulseAudio sound server uses a timer-based audio scheduling instead of the traditional interrupt-driven approach. Timer-based scheduling may expose issues in some ALSA drivers. To turn timer-based scheduling off, replace the line:<br />
load-module module-udev-detect <br />
in {{ic|/etc/pulse/default.pa}} by:<br />
load-module module-udev-detect tsched=0<br />
Then restart the PulseAudio server.<br />
<br />
===Choppy sound===<br />
Choppy sound in pulsaudio can result from wrong settings for the sample rate in {{Ic|/etc/pulse/daemon.conf}}. Try changing the line <br />
; default-sample-rate = 44100<br />
to <br />
default-sample-rate = 48000<br />
and restart the PulseAudio server.<br />
<br />
If one experiences choppy sound in applications using openAL, change the sample rate in /etc/openal/alsoft.conf:<br />
frequency = 48000<br />
<br />
===Volume adjustment does not work properly===<br />
Check:<br />
{{ic|/usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common}}<br />
<br />
If the volume does not appear to increment/decrement properly using {{ic|alsamixer}} or {{ic|amixer}}, it may be due to pulseaudio having a larger number of increments (65537 to be exact). Try using larger values when changing volume (e.g. {{ic|amixer set Master 655+}}).<br />
<br />
===Volume gets louder every time a new application is started===<br />
Per default, it seems as if changing the volume in an application sets the global system volume to that level instead of only affecting the respective application. Applications setting their volume on startup will therefore cause the system volume to "jump".<br />
<br />
Fix this by uncommenting <br />
flat-volumes = no<br />
in<br />
/etc/pulse/daemon.conf<br />
and then restarting PulseAudio by executing<br />
pulseaudio --kill && pulseaudio --start<br />
<br />
When Pulse comes back after a few seconds, applications will not alter the global system volume anymore but have their own volume level again.<br />
<br />
{{Note|A previously installed and removed pulseaudio-equalizer may leave behind remnants of the setup in {{Ic|$HOME/.pulse/default.pa}} which can also cause maximized volume trouble. Comment that out as needed.}}<br />
<br />
===No mic on ThinkPad T400/T500/T420===<br />
Run<br />
alsamixer -c 0<br />
Maximize the volume of/unmute the "Internal Mic".<br />
<br />
Once you see the device with<br />
arecord -l<br />
you might still need to adjust the settings. The microphone and the audio jack are duplexed. Set the configuration of the internal audio in pavucontrol to ''Analog Stereo Duplex''.<br />
<br />
===No mic input on Acer Aspire One===<br />
Install pavucontrol, unlink the microphone channels and turn down the left one to 0.<br />
Reference: http://getsatisfaction.com/jolicloud/topics/deaf_internal_mic_on_acer_aspire_one#reply_2108048<br />
<br />
===Sound output is only mono on M-Audio Audiophile 2496 sound card===<br />
Add the following to /etc/pulseaudio/default.pa:<br />
load-module module-alsa-sink sink_name=delta_out device=hw:M2496 format=s24le channels=10 channel_map=left,right,aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7<br />
load-module module-alsa-source source_name=delta_in device=hw:M2496 format=s24le channels=12 channel_map=left,right,aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7,aux8,aux9<br />
set-default-sink delta_out<br />
set-default-source delta_in<br />
<br />
===Static Noise in Microphone Recording===<br />
If we are getting static noise in skype, gnome-sound-recorder, arecord, etc.'s recordings then the sound card samplerate is incorrect. That is why there is static noise in linux microphone recordings. To fix this We need to set sample-rate in /etc/pulse/daemon.conf for the sound hardware.<br />
<br />
====1. Determine soundcards in the system====<br />
This requires alsa-utils and related packages to be installed:<br />
$ arecord --list-devices<br />
<br />
output:<br />
**** List of CAPTURE Hardware Devices ****<br />
card 0: Intel [HDA Intel], device 0: ALC888 Analog [ALC888 Analog]<br />
Subdevices: 1/1<br />
Subdevice #0: subdevice #0<br />
card 0: Intel [HDA Intel], device 2: ALC888 Analog [ALC888 Analog]<br />
Subdevices: 1/1<br />
Subdevice #0: subdevice #0<br />
<br />
soundcard is hw:0,0<br />
<br />
====2. Determine sampling-rate of the sound card====<br />
arecord -f dat -r 60000 -D hw:0,0 -d 5 test.wav<br />
<br />
output:<br />
"Recording WAVE 'test.wav' : Signed 16 bit Little Endian, Rate 60000 Hz, Stereo<br />
Warning: rate is not accurate (requested = 60000Hz, '''got = 96000Hz''')<br />
please, try the plug plugin<br />
<br />
observe, the '''got = 96000Hz''', this is the max sample-rate of our card.<br />
<br />
====3. Setting the soundcard's sampling rate into pulse audio configuration====<br />
the default sample-rate in pulseaudio is<br />
grep "sample-rate" /etc/pulse/daemon.conf<br />
<br />
output:<br />
; default-sample-rate = 44100<br />
<br />
It is 44100 and is disabled. Let us set our sound card's settings into pulseaudio configuation file<br />
su -c "sed 's/; default-sample-rate = 44100/default-sample-rate = 96000/g' -i /etc/pulse/daemon.conf"<br />
<br />
Let us verify the changes to deamon.conf<br />
grep "sample-rate" /etc/pulse/daemon.conf <br />
output:<br />
default-sample-rate = 96000<br />
and it is done.<br />
<br />
====4. Restart pulseaudio to apply the new settings====<br />
pulseaudio --kill<br />
pulseaudio --start<br />
<br />
====5. Finally check by recording and playing it back====<br />
Let us record some voice using mic for say 10 seconds. Make sure the mic is not muted and all<br />
arecord -f cd -d 10 test-mic.wav<br />
<br />
After 10 seconds, let us play the recording...<br />
aplay test-mic.wav<br />
<br />
Now hopefully, there is no static noise in microphone recording anymore.<br />
<br />
=== My Bluetooth device is paired but does not play any sound ===<br />
[[Bluetooth#My_device_is_paired_but_no_sound_is_played_from_it|See the article in Bluetooth section]]<br />
<br />
=== Subwoofer stops working after end of every song ===<br />
Known issue: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/494099<br />
<br />
To fix this, must edit: {{ic|/etc/pulse/daemon.conf}} and enable {{ic|enable-lfe-remixing}} :<br />
{{hc|/etc/pulse/daemon.conf|<nowiki><br />
enable-lfe-remixing = yes<br />
</nowiki>}}<br />
<br />
=== Pulseaudio uses wrong microphone ===<br />
If Pulseaudio uses the wrong microphone, and changing the Input Device with Pavucontrol did not help, take a look at alsamixer. It seems that Pavucontrol does not always set the input source correctly.<br><br />
Run:<br />
<br />
$ alsamixer<br />
<br />
press F6 and choose your sound card, e.g. HDA Intel. Now press F5 to display all items. Try to find the item: {{ic|Input Source}}. With the up/down arrow keys you are able to change the input source. <br><br />
Now try if the correct microphone is used for recording.<br />
<br />
=== Pulseaudio sounds stops media player or other sound sources === <br />
<br />
You can try commenting out following modules in /etc/pulse/default.pa <br />
#module-cork-music-on-phone<br />
#module-role-cork<br />
<br />
If that doesn't help, you can try changing flat-volumes to no in /etc/pulse/daemon.conf.<br />
flat-volumes = no<br />
<br />
==External links==<br />
*[http://www.pulseaudio.org/wiki/PerfectSetup http://www.pulseaudio.org/wiki/PerfectSetup] - A good guide to make your configuration perfect<br />
*[http://www.alsa-project.org/main/index.php/Asoundrc http://www.alsa-project.org/main/index.php/Asoundrc] - Alsa wiki on .asoundrc<br />
*[http://www.pulseaudio.org/ http://www.pulseaudio.org/] - PulseAudio official site<br />
*[http://www.pulseaudio.org/wiki/FAQ http://www.pulseaudio.org/wiki/FAQ] - PulseAudio FAQ</div>Giselherhttps://wiki.archlinux.org/index.php?title=Wayland&diff=211426Wayland2012-06-28T07:06:34Z<p>Giselher: </p>
<hr />
<div>[[Category:X Server]]<br />
[[zh-CN:Wayland]]<br />
{{Article summary start}}<br />
{{Article summary text|A guide to installing and running the Wayland display server.}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|KMS}}<br />
{{Article summary wiki|Xorg}}<br />
{{Article summary end}}<br />
<br />
'''Wayland''' is a new windowing protocol for Linux. Utilization of Wayland requires changes to and re-installation of parts of your system's software. Therefore this article will assume you are familiar with the [[Arch Build System]], or at the least the ideas behind [[PKGBUILD]] and [[makepkg]]. For more information on Wayland see its [http://wayland.freedesktop.org/ homepage].<br />
<br />
{{Warning|Wayland is under heavy development and is still an early experiment. Support can not be guaranteed and it may not function as you expect.}}<br />
<br />
== Requirements ==<br />
Currently Wayland will only work with on a system that is utilizing [[KMS]].<br />
<br />
== Installation ==<br />
You need to build and install {{AUR|wayland-git}} and {{AUR|mesa-full-wayland}} from [[AUR]]. Replacement of the Mesa stack is required because the stock one does not support Wayland.<br />
<br />
== Usage ==<br />
As Wayland is only a library, it is useless on its own. To use it, you need a compositor (like Weston), Weston demo applications, Qt with QPA (Lighthouse) support and Wayland plugin, and/or GTK with Wayland support.<br />
<br />
== Weston ==<br />
=== Installation ===<br />
You need to build and install {{AUR|cairo-gl-git}}, {{AUR|libxkbcommon-git}} and {{AUR|weston-git}} from [[AUR]].<br />
<br />
=== Usage ===<br />
Now that Wayland and its requirements are installed you should be ready to test it out. Try switching to a terminal and running:<br />
# weston<br />
Note I was having trouble with keyboard & mouse not working unless this was run as root<br />
<br />
You can also try: <br />
# EGL_DRIVER=/usr/lib/egl/egl_gallium.so<br />
if you have troubles with nouveau driver.<br />
<br />
Then at a TTY you can run the demos:<br />
<br />
# weston-terminal<br />
Should launch a terminal emulator.<br />
<br />
# weston-flower <br />
Moves a flower around the screen. This tests the frame protocol.<br />
<br />
# weston-gears<br />
Runs glxgears on Wayland.<br />
<br />
# weston-image image1.jpg image2.jpg...<br />
Displays images.<br />
<br />
# weston-view doc1.pdf doc2.pdf...<br />
Displays PDF files.<br />
<br />
== Qt ==<br />
<br />
=== Installation ===<br />
You need to build and install {{AUR|qt-qpa}} from [[AUR]]. It contains a development version of Qt 4.8 compiled with QPA (Lighthouse) support. It installs into /opt/qt-qpa because it's binary incompatible with non-QPA version of Qt (like the stock one).<br />
<br />
=== Usage ===<br />
At first, you need a working Wayland compositor, like the one from demo applications, or an experimental version of KWin.<br />
<br />
Then compile any qmake-based Qt project:<br />
# export PATH=/opt/qt-qpa/bin:$PATH<br />
# export LD_LIBRARY_PATH=/opt/qt-qpa/lib<br />
# qmake<br />
# make<br />
<br />
And run it by executing the compiled binary:<br />
# export LD_LIBRARY_PATH=/opt/qt-qpa/lib<br />
# export QT_QPA_PLATFORM=waylandgl<br />
# ./binaryname<br />
<br />
=== Qt Compositor ===<br />
There is ongoing work to make [http://labs.qt.nokia.com/2011/03/18/multi-process-lighthouse/ Qt-Compositor], a base layer to make custom Qt compositors on top of Wayland.<br />
<br />
== Other GUI libraries ==<br />
([http://wayland.freedesktop.org/toolkits.html page from official website])<br />
<br />
===GTK+===<br />
<br />
With GTK+ 3.0, GTK+ gained support for multiple backends at runtime and can switch between backends in the same way Qt can with lighthouse. The Wayland support is on the upstream GTK+ master branch but disabled by default. To try GTK+ on Wayland, check out gtk+ and pass <code>--enable-wayland</code> to configure:<br />
<br />
# git clone git://git.gnome.org/gtk+<br />
# cd gtk+<br />
# ./configure --prefix=/usr --enable-x11-backend --enable-wayland-backend --enable-debug=yes<br />
# make<br />
<br />
When both Wayland and X backends are enabled, GTK+ will default to the X11 backend, but this can be overridden by setting the <code>GDK_BACKEND</code> environment variable to <code>wayland</code>.<br />
<br />
{{Note|Alternatively, you can install {{AUR|gtk3-git}} from the [[AUR]].}}<br />
<br />
===Clutter===<br />
<br />
The Clutter toolkit has a Wayland backend that allows it to run as a Wayland client. The backend is in the master branch of the [http://git.gnome.org/browse/clutter main repo] and can be activated by passing <code>--with-flavour=wayland</code> to the configure script.<br />
<br />
===SDL===<br />
<br />
Benjamin Franzke is working on a port of SDL to Wayland, it's available in his [http://cgit.freedesktop.org/~bnf/sdl-wayland/ sdl-wayland repo] on freedesktop.org.<br />
<br />
===EFL===<br />
<br />
EFL has complete Wayland support. Please see [http://trac.enlightenment.org/e/wiki/Wayland here] for details.<br />
<br />
==Window managers and desktop shells==<br />
<br />
===KDE===<br />
<br />
The KDE Wayland support is expected to come in three phases, with the first two phases expected to be completed this year during the KDE SC 4.8 and 4.9 development cycles. Please see [http://community.kde.org/KWin/Wayland here] for details.<br />
<br />
Also, there is [http://blog.martin-graesslin.com/blog/2011/03/kwin-at-gsoc-2011/ early work] to make it possible to run KWin (KDE's window manager) on Wayland.<br />
<br />
===GNOME===<br />
<br />
GNOME will be ported to Wayland in a future version.<br />
<br />
===Unity===<br />
Ubuntu desktop shell Unity, using Compiz window manager, was [http://www.markshuttleworth.com/archives/551 announced] to be ported to Wayland.<br />
<br />
==Troubleshooting==<br />
<br />
===Invisible cursor===<br />
<br />
Make sure you have a default directory in ~/.icons with a file called index.theme. In this file you can set your mouse cursor theme. <br />
More at [[X11_Cursors]].<br />
<br />
<br />
==More Information==<br />
For more information you can see the ongoing [https://bbs.archlinux.org/viewtopic.php?id=107499 forum discussion] on Wayland.</div>Giselherhttps://wiki.archlinux.org/index.php?title=AUR_helpers/Graphical&diff=178969AUR helpers/Graphical2012-01-18T08:35:08Z<p>Giselher: Change GConf to DConf in the GNOME Packagekit Section</p>
<hr />
<div>[[Category:Arch User Repository (English)]]<br />
[[Category:Package management (English)]]<br />
{{i18n|Pacman GUI Frontends}}<br />
<br />
This is a list of frontends for the [[pacman]] CLI tool. The list includes full featured GUI frontends, informational tools, and a variety of system tray notifiers. The list also includes categories for Gtk2 based and Qt based software.<br />
<br />
{{Warning|None of these tools are officially supported by Arch Linux/Pacman developers.}}<br />
<br />
== Pacman Frontends ==<br />
=== X11 ===<br />
====PacmanXG====<br />
PacmanXG is a GUI front-end for pacman. Not depends either GTK nor Qt. Just X. This graphical tool allows to do the following:<br />
* Install/remove/upgrade packages<br />
* Search packages / filter packages<br />
* Retrieve package info include screenshots<br />
* Downgrade packages (need downgrade utility from AUR)<br />
* Refresh package database, synchronize mirrors.<br />
* Update system in one click<br />
* YAOURT support (in testing)<br />
<br />
'''AUR Package:''' https://aur.archlinux.org/packages.php?ID=52039 <br><br />
'''Screenshots''' http://almin-soft.nx0.ru/photo-cat-photo-cat-pacmanxg.html <br><br />
'''Direct link to binary:''' http://almin-soft.nx0.ru/media/files/binaries/download.php?get=pacmanXG.tar.bz2<br />
<br />
=== GNOME/GTK+ ===<br />
====Wakka====<br />
Wakka is a gtk based package manager for Arch Linux, derived from the work done on GtkPacman. The goal is to clean up the code and rework the program to be stable and extensible.<br />
<br />
'''AUR Package:''' https://aur.archlinux.org/packages.php?ID=47037 <br><br />
'''Project:''' http://code.google.com/p/wakka-package-manager/<br />
<br />
====GNOME PackageKit====<br />
GNOME PackageKit is a distribution-agnostic collection of utilities for managing packages. Using the alpm backend, it supports the following features:<br />
<br />
*Install and remove packages from the repos.<br />
*Periodically refresh package databases and prompt for updates.<br />
*Install packages from tarballs.<br />
*Search for packages by name, description, category or file.<br />
*Show package dependencies, files and reverse dependencies.<br />
*Ignore IgnorePkgs and hold HoldPkgs.<br />
*Report optional dependencies, .pacnew files, etc.<br />
<br />
You can change the remove operation from -Rc to -Rsc by setting the DConf key org.gnome.packagekit.enable-autoremove.<br />
<br />
Packages:<br />
pacman -S gnome-packagekit gnome-settings-daemon-updates<br />
<br />
If you do not wish to install PulseAudio, you can install {{Package AUR|gnome-settings-daemon-nopulse}} from the AUR.<br />
<br />
=== KDE/Qt ===<br />
====KPackageKit/Apper====<br />
KPackageKit or Apper as it is now called is a GUI front-end for [http://www.packagekit.org/ PackageKit]. Pacman integration is accomplished via the {{Package Official|packagekit}} package in [community] which gained upstream support for pacman. This graphical tool allows to do the following from KDE's systemsettings:<br />
* Install/remove/upgrade packages<br />
* Search packages / filter packages<br />
* Retrieve package info<br />
* Refresh package database<br />
* Choose which repositories will be updated<br />
* Automatically refresh database (Hourly, daily etc.)<br />
* Automatically update packages<br />
<br />
While pacman support in PackageKit is relatively new, it works with no major problems, providing ease of use, simplicity, and good integration with KDE (and PolicyKit).<br />
<br />
'''Homepage:''' http://kde-apps.org/content/show.php/Apper?content=84745 <br><br />
'''AUR Package:''' https://aur.archlinux.org/packages.php?ID=53061 <br><br />
'''Screenshots:''' http://kde-apps.org/content/show.php/Apper?content=84745<br />
<br />
====AppSet====<br />
AppSet is an advanced and feature rich GUI front-end for Package Managers. AppSet has the following features:<br />
* Software sections (games, office, multimedia, internet etc.)<br />
* Shows homepages for selected packages in an embedded web browser<br />
* Shows distributions news with an embedded feed reader<br />
* Upgrades, installs and removes packages<br />
* Shows available upgrades with a Tray Icon<br />
* Updates database periodically<br />
* Informs about dependencies (for example when trying to remove a package needed by others)<br />
* Cache clean command (to free disk space)<br />
* Intelligent launcher that uses what is already installed to get administrative privileges (by searching for kdesu, gksu or at last for an xterm where it starts with a sudo command)<br />
* Now with AUR support with Packer as backend<br />
<br />
AppSet needs only QT libs as dependence for installation. It can be used in any desktop environment. Currently only works for Archlinux using pacman.<br />
<br />
'''Homepage:''' http://appset.sourceforge.net/ <br><br />
'''AUR Package:''' https://aur.archlinux.org/packages.php?ID=43869 <br><br />
'''Screenshots''' http://sourceforge.net/project/screenshots.php?group_id=376825<br />
<br />
=== NCurses ===<br />
====pcurses====<br />
Package management in a curses frontend, including:<br />
<br />
* regexp filtering and searching any package property<br />
* customizable colorcoding<br />
* customizable sorting<br />
* external command execution with package list string replacements<br />
* user defined macros and hotkeys<br />
<br />
'''Homepage:''' https://github.com/schuay/pcurses <br><br />
'''AUR Package:''' https://aur.archlinux.org/packages.php?ID=42685 <br><br />
'''Screenshots''' https://bbs.archlinux.org/viewtopic.php?id=122749<br />
<br />
== Pacman / AUR Package Browser ==<br />
===PkgBrowser===<br />
Pkgbrowser is an application for searching and browsing Arch packages, showing details on selected packages.<br />
<br />
*Search and browse Arch packages including the AUR<br />
*Purely an informational application that cannot be used to install, remove or update packages <br />
*By design, is an accessory to CLI package management via pacman<br />
*Further details on use via manual accessed from help menu<br />
<br />
<br />
'''Forum:''' https://bbs.archlinux.org/viewtopic.php?id=117297 <br><br />
'''AUR Package:''' https://aur.archlinux.org/packages.php?ID=48372 <br><br />
'''Screenshot and source code:''' http://code.google.com/p/pkgbrowser/ <br><br />
<br />
===Pacinfo===<br />
Pacinfo is an application to browse the installed packages and show information like screenshot, installed files, installation date and others.<br />
Written in Mono/GTK#<br />
<br />
'''AUR Package:''' https://aur.archlinux.org/packages.php?ID=46065 <br><br />
'''Website:''' http://code.google.com/p/pacinfo/ <br><br />
<br />
== System Tray Notifiers ==<br />
===Archup===<br />
archup is a small C application which informs the user when system-updates for Archlinux are available. Archup uses GTk+ and libnotify to show a desktop notification if updates are available.<br />
<br />
*Homepage: [[archup]], http://www.nongnu.org/archup/<br />
*AUR Package Details: http://aur.archlinux.org/packages.php?ID=35792<br />
*Screenshots: http://www.nongnu.org/archup/, http://developer.berlios.de/dbimage.php?id=4687 , http://developer.berlios.de/dbimage.php?id=4688<br />
<br />
===Aarchup===<br />
aarchup is a fork of archup. Has the same options as archup plus a few other features. For differences between both please check changelog at the topic https://bbs.archlinux.org/viewtopic.php?id=119129<br />
<br />
*Homepage: https://github.com/aericson/aarchup/<br />
*AUR Package Details: http://aur.archlinux.org/packages.php?ID=49100<br />
*Screenshots: http://i.imgur.com/yTNvg.png<br />
<br />
===pacman-notifier===<br />
Written in Ruby, uses Gtk. Shows an icon in the system tray and popup notifications (using libnotify) for new packages.<br />
<br />
*Homepage: https://github.com/v01d/pacman-notifier/wiki<br />
*AUR Package Details: http://aur.archlinux.org/packages.php?ID=15193<br />
*Screenshots: https://github.com/v01d/pacman-notifier/wiki<br />
<br />
===Pacupdate===<br />
Pacupdate is a small application that notifies the user about new updates for Arch Linux. If Pacupdate finds out that a update is available, it will display a notification in SystemTray.<br />
<br />
*Homepage (out of date): http://code.google.com/p/pacupdate/ '''Do not''' install packages with 'pacman -Sy foo' as [https://bbs.archlinux.org/viewtopic.php?id=89328 it may lead to breakage].<br />
*AUR Package Details: http://aur.archlinux.org/packages.php?ID=25082<br />
*Screenshots:<br />
<br />
===Yapan===<br />
Yapan - Yet Another Package mAnager Notifier - is written in C++ and Qt. It shows an icon in the system tray and popup notifications for new packages and supports other package manager like clyde or yaourt.<br />
<br />
*Homepage: https://bitbucket.org/otsug/yapan/wiki/Home , https://bbs.archlinux.org/viewtopic.php?id=113078<br />
*AUR Package Details: https://aur.archlinux.org/packages.php?ID=46213<br />
*Screenshots: https://bitbucket.org/otsug/yapan/wiki/Home<br />
<br />
===ZenMan===<br />
PacMan frontend (tray update notifier) for GTK/GNOME/zenity/libnotify.<br />
<br />
*Homepage:<br />
*AUR Package Details: http://aur.archlinux.org/packages.php?ID=25948<br />
*Screenshots: http://show.harvie.cz/screenshots/zenman-screenshot-2.png<br />
<br />
===pkgnotify.sh===<br />
A very simple 14 line shell script that displays the number of available updates in the dzen2 title window and a list of these updates in the slave window. Depends on yaourt, dzen2 and inotify-tools.<br />
<br />
*Homepage: http://pointfree.net/repo/?r=dzen2_scripts;a=headblob;f=/src/pkgnotify/pkgnotify.sh<br />
*AUR Package Details:<br />
*Screenshots: http://andreasbwagner.tumblr.com/post/853471635/arch-linux-update-notifier-for-dzen2<br />
<br />
== Inactive Software Packages ==<br />
*[http://gtkpacman.berlios.de/ GtkPacman]<br />
*[http://guzuta.berlios.de/ Guzuta]<br />
*[http://chakra-project.org/wiki/index.php/Shaman Shaman]<br />
*[http://code.google.com/p/pacmon/ pacmon]<br />
*[https://gna.org/projects/paku/ Paku]<br />
*[http://www.kde-apps.org/content/show.php/YAPG+-+Yet+Another+Pacman+Gui+?content=60052 YAPG]<br />
*[http://sourceforge.net/projects/zenitypacgui/ zenity_pacgui]</div>Giselher