[arch-general] systemd-pulseaudio-no sound card
Dear list, I have spent now many hours trying to understand why pulseaudio is not working when I boot with systemd, but works when booting with sysvinit. I found the culprit could be this: [gabx@magnolia:~]$ aplay -l aplay: device_list:252: no soundcards found... What is strange is that all my devices are recognised and modules loaded. $ lspci -v 01:00.1 Audio device: NVIDIA Corporation GF114 HDMI Audio Controller (rev a1) Subsystem: ASUSTeK Computer Inc. Device 838b Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at fa080000 (32-bit, non-prefetchable) [size=16K] Capabilities: <access denied> Kernel driver in use: snd_hda_intel 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) Subsystem: ASUSTeK Computer Inc. Device 8444 Flags: bus master, fast devsel, latency 0, IRQ 57 Memory at fa300000 (64-bit, non-prefetchable) [size=16K] Capabilities: <access denied> Kernel driver in use: snd_hda_intel $ lsmod snd_hda_intel 25700 0 $ loginctl SESSION UID USER SEAT 1 1000 gabx seat0 1 sessions listed. $ loginctl seat-status seat0 ├ /sys/devices/pci0000:00/0000:00:1b.0/sound/card0 │ (sound:card0) "PCH" ├ /sys/devic...:00/0000:00:01.0/0000:01:00.1/sound/card1 │ (sound:card1) "NVidia" $ pulseaudio E: [pulseaudio] pid.c: Daemon already running. E: [pulseaudio] main.c: pa_pid_file_create() failed. when I open the volum control in XFCE panel: GStreamer was unable to detect any sound device. Some sound system specific GStreamer package maybe missing. It may also be a permissions problem. To sum up, I don't understand why my sound devices are not recognized. I may have misconfigured something in systemd set up, but I have no idea. Thank you for your help, as this is the only issue when booting with systemd.
On Wed, 2012-08-29 at 16:04 +0200, Arno Gaboury wrote:
this is the only issue when booting with systemd.
There is a certain irony in the fact that the "only" issue is regarding to systemd + pulseaudio and not when booting with sysvinit ;D. Rollin', rollin', rollin' ...
On 29/08/12||16:16, Ralf Mardorf wrote:
On Wed, 2012-08-29 at 16:04 +0200, Arno Gaboury wrote:
this is the only issue when booting with systemd.
There is a certain irony in the fact that the "only" issue is regarding to systemd + pulseaudio and not when booting with sysvinit ;D.
Rollin', rollin', rollin' ...
i do not want to participate to the already much too long and boring flame about systemd, but yes, it is ironic to see my only issue comes from pulseaudio, writen by the same guru that wrote systemd!
On Wed, Aug 29, 2012 at 4:42 PM, Arno Gaboury <arnaud.gaboury@gmail.com> wrote:
On 29/08/12||16:16, Ralf Mardorf wrote:
On Wed, 2012-08-29 at 16:04 +0200, Arno Gaboury wrote:
this is the only issue when booting with systemd.
There is a certain irony in the fact that the "only" issue is regarding to systemd + pulseaudio and not when booting with sysvinit ;D.
Rollin', rollin', rollin' ...
i do not want to participate to the already much too long and boring flame about systemd, but yes, it is ironic to see my only issue comes from pulseaudio, writen by the same guru that wrote systemd!
what daemons are you running under initscripts and what under systemd? -- Kwpolska <http://kwpolska.tk> stop html mail | always bottom-post www.asciiribbon.org | www.netmeister.org/news/learn2quote.html GPG KEY: 5EAAEA16
On 29/08/12||18:53, Kwpolska wrote:
On Wed, Aug 29, 2012 at 4:42 PM, Arno Gaboury <arnaud.gaboury@gmail.com> wrote:
On 29/08/12||16:16, Ralf Mardorf wrote:
On Wed, 2012-08-29 at 16:04 +0200, Arno Gaboury wrote:
this is the only issue when booting with systemd.
There is a certain irony in the fact that the "only" issue is regarding to systemd + pulseaudio and not when booting with sysvinit ;D.
Rollin', rollin', rollin' ...
i do not want to participate to the already much too long and boring flame about systemd, but yes, it is ironic to see my only issue comes from pulseaudio, writen by the same guru that wrote systemd!
what daemons are you running under initscripts and what under systemd?
rc.conf : DAEMONS=(syslog-ng dbus iptables networkmanager !net-profiles netfs ntpd @sshd crond libvirtd acpid @avahi-daemon @mpd) now with systemd, $ ps aux | lsee give me: -systemd-journald -systemd-udevd -avahi-daemon -avahi-dnsconfd -s -mpd --no-daemon -systemd-logind -libvirtd -crond -n -sshd -D -Networkmanager --no-daemon -dbus-daemon --system --adress=systemd: --nofork --nopidfile --systemd-activation -polkitd --no-debug -syslog-ng -F -acpid -f -ntpd -g -u -dhcpd -console-kit-daemon --no-daemon -dbus-launch --sh-syntax --exit-with-session -dbus-daemon --fork --print-pid5 --print-adress 7 --session -pulseaudio --start -rtkit-daemon -xfconfd -gvfsd -upowerd -udiskd --no-debug -gconfd-2 I guess the list is too long ! My issue comes from permission. On console mod, $ aplay -l returns correctly the devices. When I am on X, it doesn't.
-- Kwpolska <http://kwpolska.tk> stop html mail | always bottom-post www.asciiribbon.org | www.netmeister.org/news/learn2quote.html GPG KEY: 5EAAEA16
My issue comes from permission. On console mod, $ aplay -l returns correctly the devices. When I am on X, it doesn't.
Might be a PolicyKit issue. How do you start your X server / desktop manager? -- Sébastien Leblanc
On 29 August 2012 13:20, Sébastien Leblanc <leblancsebas@gmail.com> wrote:
My issue comes from permission. On console mod, $ aplay -l returns correctly the devices. When I am on X, it doesn't.
Might be a PolicyKit issue. How do you start your X server / desktop manager?
Guuhhh, ConsoleKit... -- Sébastien Leblanc
Disregard that, I did not know enough of systemd to know that it uses a mechanism named 'loginctl' instead of ConsoleKit... -- Sébastien Leblanc
On 29/08/12||13:20, Sébastien Leblanc wrote:
My issue comes from permission. On console mod, $ aplay -l returns correctly the devices. When I am on X, it doesn't.
Might be a PolicyKit issue. How do you start your X server / desktop manager?
-- Sébastien Leblanc
Maybe. I startx with : exec startxfce4 --with-ck-launch.
Am Wed, 29 Aug 2012 19:32:54 +0200 schrieb Arno Gaboury <arnaud.gaboury@gmail.com>:
On 29/08/12||13:20, Sébastien Leblanc wrote:
My issue comes from permission. On console mod, $ aplay -l returns correctly the devices. When I am on X, it doesn't.
Might be a PolicyKit issue. How do you start your X server / desktop manager?
-- Sébastien Leblanc
Maybe. I startx with :
exec startxfce4 --with-ck-launch.
Try only: exec startxfce4 When I start Xfce with exec ck-launch-session startxfce4 I get some issues with permissions, too. The action buttons don't work and I only can logout but not halt or reboot (both grayed out) when I use ck-launch-session. Without it I have absolutely no problems. I don't know if this could affect your issue, too. I'd recommend not using PA anyway. Heiko
On Aug 29, 2012 7:33 PM, "Arno Gaboury" <arnaud.gaboury@gmail.com> wrote:
On 29/08/12||13:20, Sébastien Leblanc wrote:
My issue comes from permission. On console mod, $ aplay -l returns correctly the devices. When I am on X, it doesn't.
Might be a PolicyKit issue. How do you start your X server / desktop
manager?
-- Sébastien Leblanc
Maybe. I startx with :
exec startxfce4 --with-ck-launch.
My guess is that your graphical session is not registered properly with pam. You can verify this by checking if your session is 'active' according to loginctl. The blog post i mentioned explains how to work around this. Tom
participants (6)
-
Arno Gaboury
-
Heiko Baums
-
Kwpolska
-
Ralf Mardorf
-
Sébastien Leblanc
-
Tom Gundersen