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#38877 - [pulseaudio] delay after KDM login in KDE before kmix/kickoff can be used

Attached to Project: Arch Linux
Opened by corentin (cocopat99) - Tuesday, 11 February 2014, 23:47 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 06 July 2015, 04:29 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 1
Private No

Details

Description:
I got a delay after login in KDE, i can't start application before waiting a short delay, kickoff (menu) is frozen, kmix not started.
After this little delay, all work fine.

Additional info:
* package version(s) : pulseaudio 4.0-6
* config and/or log files etc. : fresh install

Steps to reproduce:
Install kde
Install kmix
Install pulseaudio

Workaround :
I found on internet people with same issue, it seem to be caused by the simultaneous presence of :
/etc/xdg/autostart/pulseaudio.desktop
/etc/xdg/autostart/pulseaudio-kde.desktop
I removed /etc/xdg/autostart/pulseaudio.desktop and the delay is gone.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Monday, 06 July 2015, 04:29 GMT
Reason for closing:  No response
Comment by Jan Alexander Steffens (heftig) - Wednesday, 12 February 2014, 09:34 GMT
Still an issue using 4.99.3-1, in [testing]?
Comment by corentin (cocopat99) - Thursday, 13 February 2014, 01:12 GMT
Thank you for taking care of my report.

I activated [testing]
Synchronised pacman
Reinstalled pulseaudio (4.99.3-1) with : pacman -S pulseaudio
/etc/xdg/autostart/pulseaudio.desktop is back

I rebooted 10 time, got the delay again at second reboot, but now, delay is gone.
I noticed a change (removed time and hostname from journal) :

With pulseaudio 4.0-6 and without /etc/xdg/autostart/pulseaudio.desktop
$journalctl -b -10 --no-pager | grep pulse
rtkit-daemon[399]: Successfully made thread 398 of process 398 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
rtkit-daemon[399]: Successfully made thread 402 of process 398 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
rtkit-daemon[399]: Successfully made thread 403 of process 398 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
rtkit-daemon[399]: Successfully made thread 404 of process 398 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
rtkit-daemon[399]: Successfully made thread 405 of process 398 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
rtkit-daemon[399]: Successfully made thread 406 of process 398 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
pulseaudio[398]: [pulseaudio] bluez4-util.c: org.bluez.Manager.GetProperties() failed: org.freedesktop.DBus.Error.UnknownMethod: Method "GetProperties" with signature "" on interface "org.bluez.Manager" doesn't exist
rtkit-daemon[399]: Successfully made thread 726 of process 726 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
pulseaudio[726]: [pulseaudio] pid.c: Daemon already running.

With pulseaudio 4.99.3-1
journalctl -b -8 --no-pager | grep pulse
rtkit-daemon[660]: Successfully made thread 659 of process 659 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
rtkit-daemon[660]: Successfully made thread 719 of process 659 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
rtkit-daemon[660]: Successfully made thread 724 of process 659 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
rtkit-daemon[660]: Successfully made thread 725 of process 659 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
rtkit-daemon[660]: Successfully made thread 726 of process 659 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
rtkit-daemon[660]: Successfully made thread 727 of process 659 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
rtkit-daemon[660]: Successfully made thread 732 of process 732 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
pulseaudio[732]: Daemon already running.
rtkit-daemon[660]: Successfully made thread 734 of process 734 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
pulseaudio[734]: Daemon already running.
rtkit-daemon[660]: Successfully made thread 737 of process 737 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
pulseaudio[737]: [pulseaudio] pid.c: Daemon already running.
rtkit-daemon[660]: Successfully made thread 741 of process 741 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
pulseaudio[741]: [pulseaudio] pid.c: Daemon already running.

I don't know if it can be usefull.
It seem that pulseaudio is started more often (but detect he is already demonized like in version 4.0.6)
It seem something changed with bluetooth (i don't use bluetooth with pulseaudio)

Maybe the "bug" is gone in testing.

(Sorry for my english)
Comment by corentin (cocopat99) - Thursday, 13 February 2014, 01:17 GMT
I forgot a journal :

With pulseaudio 4.0.6 and with /etc/xdg/autostart/pulseaudio.desktop
$journalctl -b -11 --no-pager | grep pulse
pulseaudio[398]: [pulseaudio] bluez4-util.c: org.bluez.Manager.GetProperties() failed: org.freedesktop.DBus.Error.UnknownMethod: Method "GetProperties" with signature "" on interface "org.bluez.Manager" doesn't exist
pulseaudio[794]: [pulseaudio] pid.c: Daemon already running.

rtfkit don't appear in this journal
Comment by Steven Noonan (neunon) - Wednesday, 02 April 2014, 01:08 GMT
I've hit this issue, and my solution was to add:

NotStartIn=KDE;

to /etc/xdg/autostart/pulseaudio.desktop.
Comment by Steven Noonan (neunon) - Friday, 04 April 2014, 20:38 GMT
Er, sorry, typo'd that. It should read 'NotShowIn=KDE;'

Sources:
https://bugs.freedesktop.org/show_bug.cgi?id=58758
https://bugs.kde.org/show_bug.cgi?id=312560
Comment by Doug Newgard (Scimmia) - Wednesday, 13 May 2015, 20:41 GMT
Still an issue? How about with plasma 5?

Loading...