You are not logged in.
I just tried out Xmonad for the first time but I can not get pulseaudio to work. The problem is, I start Xmonad using startx on tty1, it then launches on tty2, but pulseaudio seems to somehow remember me logging in on tty1 and only plays sound when I'm on tty1.
So if I start a sound application in xmonad on tty2, I hear nothing, but when I switch to the terminal on tty1 from which I started xmonad, I get the sound perfectly, until I switch back to tty2...
Is the only solution to start pulseaudio system-wide instead of per-session or is there just some configuration option that I've been unable to find?
I googled and look on the wiki pages for xmonad and pulseaudio. I also tried starting xmonad both with just a plain "exec xmonad" in .xinitrc and with a ck-launch-session in between.
Sound works fine in gnome, by the way.
Anyone a suggestion? ![]()
Offline
1.Is your user in the audio group?
2. How did you used to start X before trying xmonad, i.e., same way of logging in on tty1 and then startx or something else?
3. Have you updated your system, as consolekit has been removed from the repositories, and maybe that's the reason.
4. Test if plain alsa works.
Also, take a look here:
https://bugs.launchpad.net/ubuntu/+sour … bug/213149
Last edited by x33a (2012-11-03 17:23:25)
Offline
You don't need ck-launch-session nor be in the audio group (or anything other than users). You shouldn't run pulseaudio system-wide either.
For logind permissions to be applied to X it needs to be started on the same tty which you logged in on. Most Display Managers should handle this correctly.
Please paste your ~/.xinitrc, the output of pacman -Q xorg-xinit and lastly; Update: Are you currently booting with systemd?
Edit: The reason your sound isn't working is because you don't have an authenticated session on tty2, this means that the ACL's drop the permissions. See here (again) and take note of '/usr/lib/udev/rules.d/70-uaccess.rules'. Follow the rest of that section and the link to Preserving your Session.
Last edited by Earnestly (2012-11-05 00:30:01)
Offline
Okay, my main environment is currently gnome and because I have some important work that has to be finished next week, I delayed the upgrade to gnome 3.6 because I cannot afford a broken system right now and I see a number a troublesome threads about gnome 3.6.
As it seems that this might be a ck <> logind issue, I'll try this again next week after I've upgraded my system to all that new stuff. Thanks for the pointers! I'll post back here with more details if I still don't get it to work then.
Offline