Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#33807 - [pulseaudio] Problems with Gnome

Attached to Project: Arch Linux
Opened by Marc Straube (durag) - Monday, 11 February 2013, 01:56 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Sunday, 05 May 2013, 22:14 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
After installing an Arch base system with Gnome from the actual image 2013-02-01 there are some Pulseaudio errors:

Feb 10 16:25:01 hightower rtkit-daemon[489]: Successfully made thread 488 of process 488 (/usr/bin/pulseaudio) owned by '120' high priority at nice level -11.
Feb 10 16:25:14 hightower rtkit-daemon[489]: Successfully made thread 606 of process 606 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
Feb 10 16:25:15 hightower rtkit-daemon[489]: Successfully made thread 636 of process 636 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
Feb 10 16:25:15 hightower pulseaudio[636]: [pulseaudio] pid.c: Daemon already running.
Feb 10 16:28:55 hightower pulseaudio[1000]: [pulseaudio] module-jackdbus-detect.c: Unable to contact D-Bus session bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
Feb 10 16:28:55 hightower pulseaudio[1000]: [pulseaudio] module.c: Failed to load module "module-jackdbus-detect" (argument:""): initialization failed.
Feb 10 16:28:55 hightower pulseaudio[1000]: [pulseaudio] socket-server.c: bind(): Die Adresse wird bereits verwendet
Feb 10 16:28:55 hightower pulseaudio[1000]: [pulseaudio] module.c: Failed to load module "module-esound-protocol-unix" (argument: ""): initialization failed.
Feb 10 16:28:55 hightower pulseaudio[1000]: [pulseaudio] main.c: Module load failed.
Feb 10 16:28:55 hightower pulseaudio[1000]: [pulseaudio] main.c: Module load failed.
Feb 10 16:28:55 hightower pulseaudio[1000]: [pulseaudio] main.c: Failed to initialize daemon.
Feb 10 16:28:55 hightower pulseaudio[997]: [pulseaudio] main.c: Daemon startup failed.


After removing /etc/xdg/autostart/pulseaudio.desktop and /etc/xdg/autostart/pulseaudio-kde.desktop and rebooting the PC the errors are gone.

# journalctl | grep 'pulseaudio'

Feb 10 17:41:42 hightower rtkit-daemon[485]: Successfully made thread 484 of process 484 (/usr/bin/pulseaudio) owned by '120' high priority at nice level -11.
Feb 10 17:41:55 hightower rtkit-daemon[485]: Successfully made thread 625 of process 625 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.


Some applications still got problems to work with Pulseaudio.

# ps aux | grep pulse
rebel 727 0.7 0.2 444316 10288 ? S<l 03:02 0:00 /usr/bin/pulseaudio --start --log-target=syslog
rebel 731 0.0 0.0 71236 2652 ? S 03:02 0:00 /usr/lib/pulse/gconf-helper
rebel 843 0.0 0.0 17396 1184 pts/0 D+ 03:03 0:00 grep pulse


After executing following commands, sound works for these programs.
rm -rf .config/pulse/
killall pulseaudio
killall -9 pulseaudio

Running ps aux | grep pulse again shows up with different STAT-Codes. The priority of the pulseaudio process is not high anymore.
rebel 4016 4.2 0.2 510124 11528 ? Sl 03:06 0:02 /usr/bin/pulseaudio --start --log-target=syslog
rebel 4020 0.0 0.0 71368 2700 ? S 03:06 0:00 /usr/lib/pulse/gconf-helper
rebel 4046 0.0 0.0 19456 1216 pts/0 R+ 03:07 0:00 grep pulse

Additional info:
pulseaudio 3.0-2
gnome-shell 3.6.2-1



Steps to reproduce:
Perform a basic installation of Arch. After that install xorg-server and gnome.
This task depends upon

Closed by  Gerardo Exequiel Pozzi (djgera)
Sunday, 05 May 2013, 22:14 GMT
Reason for closing:  Fixed
Additional comments about closing:  3.99.1-1
Comment by Marc Straube (durag) - Monday, 11 February 2013, 02:00 GMT
Here are my threads from the bbs: https://bbs.archlinux.org/viewtopic.php?id=157856 and https://bbs.archlinux.de/viewtopic.php?id=23402
If it could help, I can also provide you with a full step-by-step installation guide how I set up the system.
Comment by Marc Straube (durag) - Tuesday, 12 February 2013, 00:33 GMT
I got new expertise on the case. Pulseaudio is definitely the origin of the problem.
I've done a basic installation again. After that I installed xfce4, tvtime, sundtek (from AUR) and slim -> Sound is working in this configuration and there where no errors in the logs.
So I installed pulseaudio and pavucontrol and rebooted the system. Again I got no sound with my tvcard and Pulseaudio is dropping many errors. I've attached a log file in this comment.
Comment by Marc Straube (durag) - Tuesday, 12 February 2013, 22:57 GMT
I get rid of almost every error after downgrading to pulseaudio-2.1 and libpulse-2.1-1.

Just this one error stays:
$ sudo journalctl -b | grep pulseaudio
Feb 13 00:45:05 hightower rtkit-daemon[593]: Successfully made thread 592 of process 592 (/usr/bin/pulseaudio) owned by '120' high priority at nice level -11.
Feb 13 00:45:19 hightower rtkit-daemon[593]: Successfully made thread 769 of process 769 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
Feb 13 00:45:21 hightower rtkit-daemon[593]: Successfully made thread 794 of process 794 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
Feb 13 00:45:21 hightower pulseaudio[794]: [pulseaudio] pid.c: Daemon already running.


I also tested pulseaudio-2.99.3 and libpulse-3.99.3-1 but with this version sound is gone again!

Should I report this to upstream?
Comment by keerthan (jck) - Wednesday, 06 March 2013, 21:32 GMT
I also face the same problem. Downgrading to 2.1 fixes it for me.
Comment by Jan Alexander Steffens (heftig) - Saturday, 04 May 2013, 21:34 GMT
Still an issue? Also try 3.99.1-1 from [testing].
Comment by Marc Straube (durag) - Sunday, 05 May 2013, 17:25 GMT
Hey! Thank you for the information! Sound works again with 3.99.1-1 from [testing]!!!

Loading...