[sru] plasma-nm blocks temporarily on startup w/o bluetooth device – KDE/Plasma very slow to launch (Kubuntu 15.10)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plasma-nm |
Fix Released
|
Medium
|
|||
plasma-nm (Ubuntu) |
Fix Released
|
Undecided
|
Philip Muškovac | ||
Wily |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
Plasma NM does synchronous DBus calls do bluez for the bluetooth status, which in some situations can take up to 30s to finish/reach a timeout.
As Plasma itself waits for Plasma NM to initialize, this can cause the Plasma login to take half a minute without any response.
[Test Case]
First of all, you need a system that is affected by this.
- Try to log in an see that it takes unusually long to do so (~30s)
- Enable wily-proposed and update plasma-nm
- Reboot and verify that the login now takes 5-10s
[Regression potential]
This is mostly just reworking existing BT activation code, so the worst that should happen is the adapter getting enabled a while after the Desktop finished loading. As that's a normal use case when you enable an adapter by hand later on this shouldn't cause any issues.
[Original Description]
On my four PCs upgraded from Kubuntu 15.04 to 15.10, I have the same problem: for two days, KDE/Plasma is very long to launch. The desktop begins to appear but I must wait nearly one minute for all plasma widgets and icons to appear. And I repeat, this is happening on 4 different machines !
Once everything is finally launched, the system seems OK.
Update: removing the network manager app from the taskbar solves the problem.
description: | updated |
Changed in plasma-nm (Ubuntu): | |
assignee: | nobody → kiran (skirankumars31) |
assignee: | kiran (skirankumars31) → nobody |
Changed in plasma-nm (Ubuntu): | |
assignee: | nobody → Philip Muškovac (yofel) |
status: | Confirmed → Triaged |
Changed in plasma-nm (Ubuntu Wily): | |
assignee: | nobody → Philip Muškovac (yofel) |
Changed in plasma-nm: | |
importance: | Unknown → Medium |
status: | Unknown → Fix Released |
tags: | added: kubuntu wily |
Changed in plasma-nm (Ubuntu): | |
status: | Triaged → Fix Committed |
Changed in plasma-nm (Ubuntu Wily): | |
assignee: | Philip Muškovac (yofel) → nobody |
status: | New → In Progress |
description: | updated |
summary: |
+ [sru] plasma-nm blocks temporarily on startup w/o bluetooth device – KDE/Plasma very slow to launch (Kubuntu 15.10) |
summary: |
- [sru] plasma-nm blocks temporarily on startup w/o bluetooth device – - KDE/Plasma very slow to launch (Kubuntu 15.10) + [regression] [sru] plasma-nm blocks temporarily on startup w/o bluetooth + device – KDE/Plasma very slow to launch (Kubuntu 15.10) |
summary: |
- [regression] [sru] plasma-nm blocks temporarily on startup w/o bluetooth - device – KDE/Plasma very slow to launch (Kubuntu 15.10) + [sru] plasma-nm blocks temporarily on startup w/o bluetooth device – + KDE/Plasma very slow to launch (Kubuntu 15.10) |
tags: | added: regression-release |
Hello
i just upgraded an Kubuntu 15.04 to 15.10 today.
After ssdm login, plasma starts launching, I can see wallpaper and desktop icons, but taskbar is empty. Nothing can be done during 30 first seconds with mouse or keyboard in this tty.
During this time, in another tty1 I can see cpu at 3% only...
I reproduce the problem at every startup and at every login with my usual login or with a newly created account.
Bootchart shows a python3 process sleeping a long time and then plasmashell finishes to load..
How to identify this process or to debug it?
Reproducible: Always
I can attach bootchart.svg if necessary