Public bug reported:
Kubuntu 16.04 --
I was experiencing a long delay when logging in, on the order of 20+
seconds. After entering the password on the splash screen, it would stay
there before showing the desktop.
journalctl revealed a timeout form pulseaudio waiting for a bluetooth
service (I don't not use bluetooth, and it is disabled, but I believe I
saw this even when I enabled it?)
Jun 26 10:43:42 machinename org.kde.KScreen[1988]: kscreen: Primary output
changed from KScreen::Output(Id: 68 , Name: "HDMI1" ) ( "HDMI1" ) to
KScreen::Output(Id: 68 , Name: "HDMI1" ) ( "HDMI1" )
Jun 26 10:44:02 machinename dbus[982]: [system] Failed to activate service
'org.bluez': timed out
Jun 26 10:44:02 machinename pulseaudio[2121]: [pulseaudio] bluez5-util.c:
GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive
a reply. Possible causes include: the remote application did not send a reply,
the message bus security policy blocked the reply, the reply timeout expired,
or the network connection was broken.
I can fix the problem by editing /etc/pulse/default.pa and commenting
out both bluetooth lines ("load-module module-bluetooth-policy" and
"load-module module-bluetooth-discover" -- not sure if both are actually
necessary.)
I have seen other bugs relating to blocking calls to bluetooth causing
problems. Perhaps there are a few left.
** Affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
** Tags: blocking bluetooth bluez pulse pulseaudio slow splash timeout
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1596344
Title:
pulseaudio causes long login delay waiting for bluetooth
Status in pulseaudio package in Ubuntu:
New
Bug description:
Kubuntu 16.04 --
I was experiencing a long delay when logging in, on the order of 20+
seconds. After entering the password on the splash screen, it would
stay there before showing the desktop.
journalctl revealed a timeout form pulseaudio waiting for a bluetooth
service (I don't not use bluetooth, and it is disabled, but I believe
I saw this even when I enabled it?)
Jun 26 10:43:42 machinename org.kde.KScreen[1988]: kscreen: Primary output
changed from KScreen::Output(Id: 68 , Name: "HDMI1" ) ( "HDMI1" ) to
KScreen::Output(Id: 68 , Name: "HDMI1" ) ( "HDMI1" )
Jun 26 10:44:02 machinename dbus[982]: [system] Failed to activate service
'org.bluez': timed out
Jun 26 10:44:02 machinename pulseaudio[2121]: [pulseaudio] bluez5-util.c:
GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive
a reply. Possible causes include: the remote application did not send a reply,
the message bus security policy blocked the reply, the reply timeout expired,
or the network connection was broken.
I can fix the problem by editing /etc/pulse/default.pa and commenting
out both bluetooth lines ("load-module module-bluetooth-policy" and
"load-module module-bluetooth-discover" -- not sure if both are
actually necessary.)
I have seen other bugs relating to blocking calls to bluetooth causing
problems. Perhaps there are a few left.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1596344/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
