Re: plasma5 timeout with bluetooth
Hi, >> It sounds like this bug: >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804908 > > Yes, thank you. This eventually explains why the bluetooth service is not > starting. > > But it does not explain why plasma5 is waiting 50 s for this service. > XFCE and cinnamon are starting just fine. So i can not understand why plasma5 > behaves like that. https://bugs.kde.org/show_bug.cgi?id=354230 https://git.reviewboard.kde.org/r/125785/ https://quickgit.kde.org/?p=plasma-nm.git&a=commit&h=48a45eb Best wishes, Boris
Re: plasma5 timeout with bluetooth
Am 13.11.2015 um 18:56 schrieb Holger Schramm: > Am 13.11.2015 um 08:16 schrieb Matthias Bodenbinder: >> Hi, >> >> my plasma5 is hanging for ca. 50 s after login when bluetooth is enabled. As >> soon as I do "systemctl disable bluetooth.service" the login proceeds just >> fine. As soon as I do "systemctl enable bluetooth.service" I have to wait >> for about 50 s. >> >> The log file says: >> >> Nov 13 08:07:16 rakete dbus[1270]: [system] Activating via systemd: service >> name='org.bluez' unit='dbus-org.bluez.service' >> Nov 13 08:07:41 rakete dbus[1270]: [system] Failed to activate service >> 'org.bluez': timed out >> Nov 13 08:07:41 rakete dbus[1270]: [system] Activating via systemd: service >> name='org.bluez' unit='dbus-org.bluez.service' >> Nov 13 08:08:06 rakete dbus[1270]: [system] Failed to activate service >> 'org.bluez': timed out >> >> The background service "bluetooth" in plasma5 systemsettings is disabled. It >> looks like plasma5 is waiting for this service in any case. > > It sounds like this bug: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804908 > Yes, thank you. This eventually explains why the bluetooth service is not starting. But it does not explain why plasma5 is waiting 50 s for this service. XFCE and cinnamon are starting just fine. So i can not understand why plasma5 behaves like that. Matthias
Re: plasma5 timeout with bluetooth
Am 13.11.2015 um 08:16 schrieb Matthias Bodenbinder: > Hi, > > my plasma5 is hanging for ca. 50 s after login when bluetooth is enabled. As > soon as I do "systemctl disable bluetooth.service" the login proceeds just > fine. As soon as I do "systemctl enable bluetooth.service" I have to wait for > about 50 s. > > The log file says: > > Nov 13 08:07:16 rakete dbus[1270]: [system] Activating via systemd: service > name='org.bluez' unit='dbus-org.bluez.service' > Nov 13 08:07:41 rakete dbus[1270]: [system] Failed to activate service > 'org.bluez': timed out > Nov 13 08:07:41 rakete dbus[1270]: [system] Activating via systemd: service > name='org.bluez' unit='dbus-org.bluez.service' > Nov 13 08:08:06 rakete dbus[1270]: [system] Failed to activate service > 'org.bluez': timed out > > The background service "bluetooth" in plasma5 systemsettings is disabled. It > looks like plasma5 is waiting for this service in any case. It sounds like this bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804908 -- Holger
plasma5 timeout with bluetooth
Hi, my plasma5 is hanging for ca. 50 s after login when bluetooth is enabled. As soon as I do "systemctl disable bluetooth.service" the login proceeds just fine. As soon as I do "systemctl enable bluetooth.service" I have to wait for about 50 s. The log file says: Nov 13 08:07:16 rakete dbus[1270]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' Nov 13 08:07:41 rakete dbus[1270]: [system] Failed to activate service 'org.bluez': timed out Nov 13 08:07:41 rakete dbus[1270]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' Nov 13 08:08:06 rakete dbus[1270]: [system] Failed to activate service 'org.bluez': timed out The background service "bluetooth" in plasma5 systemsettings is disabled. It looks like plasma5 is waiting for this service in any case. Kind Regards Matthias
