Slow login to kde5 waiting on breeze splash
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
breeze (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
I still get the slow login as happened with kubuntu 15.10 now on a fresh install of kubuntu 16.04 on multiple systems.
The pause is identical to as happened in this bug which is marked as closed, but it does not appear to be bluetooth related this time: https:/
The kde throbber reaches 100% very quickly and then there is a pause where there is no activity and then the desktop finally appears many seconds later. A systemd analyze blame shows the following as top10:
5.997s NetworkManager-
2.469s postgresql@
2.457s postgresql@
2.365s postgresql@
646ms networking.service
558ms ModemManager.
534ms accounts-
520ms systemd-
436ms grub-common.service
423ms ondemand.service
Switching to xfce4 there is no delay at all on login.
summary: |
- Slow login to kde5 waiting on networkmanager + Slow login to kde5 waiting on ?networkmanager |
no longer affects: | plasma-nm (Ubuntu) |
summary: |
- Slow login to kde5 waiting on ?networkmanager + Slow login to kde5 waiting on breeze splash |
no longer affects: | breeze-qt4 (Ubuntu) |
tags: | added: xenial |
Changed in breeze (Ubuntu): | |
importance: | Undecided → High |
Hi,
I have the same problems (Kubuntu 16.10, SDDM, network-manager, notebook with Skylake Core-i3-6100U with external HDMI-Monitor both 1920x1080px). I did some experiments to find the cause:
1. create a new user test2
2. reboot
3. login as test2
4. --> Fast login to the Plasma --> Since network-manager and plasma-applet is running this does not seem to cause the 30s delay
Now I tried out some adjustments in the system setting like
a) Plasma theme
b) start with a empty session
c) show no options in the exit dialogue
and rebooted after each adjustment. The login was fast after them! So, there does not seem to be a general problem with saving Plasma settings.
Then I tried to chase the bug:
5. In system setting I set my external monitor as primary display and disabled the internal notebook monitor.
6. reboot
7. Login as test2 and there is the 30s-delay!
8. Change the display back to internal notebook
9. reboot
7. Login as test2 and there is still the 30s-delay!
Thus, the delay seems not to be caused by network-manager but of the display stuff. But I could not find anything in ~./xsession-erros or /var/log/X.org.log.
Do you know how to debug it?