Bug 362590 - after login, it takes much time after starting the desktop
Summary: after login, it takes much time after starting the desktop
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (other bugs)
Version First Reported In: 5.5.5
Platform: Kubuntu Linux
: NOR normal
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-02 16:25 UTC by flo
Modified: 2020-12-08 04:34 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description flo 2016-05-02 16:25:52 UTC
After login ( so type in user information on SSDM displaymanager), the loading bar enters very fast full state. Then it additional 30-40s to laod the Desktop. When the loading bar is full, I can press ALT+TAB to swtich between applications and I see for a few moments the status bar (for wlan, devices, clock etc.) 
I purged kde-connect, enabled and disabled wifi and bluetooth but nothing changed.
System:
Dell Latitude E7440 with Intel Wifi and Bluetooth wit fresh install of Kubuntu 16.04

Reproducible: Always

Steps to Reproduce:
1. logout
2. login
3. 

Actual Results:  
it take a lot of time to login

Expected Results:  
the login time does not take so much time
Comment 1 flo 2016-05-02 16:40:21 UTC
I look at syslog and found this (maybe) interesting detail: KScreen seems to configure very often, unless there is "nothing" to configure (laptop connected with DisplayPort to monitor, but the login problem also happens when using the laptop-monitor):

May  2 18:31:05 mylaptop org.kde.KScreen[1473]: kscreen: Primary output changed from KScreen::Output(Id: 70 , Name: "DP1-2" ) ( "DP1-2" ) to KScreen::Output(Id: 70 , Name: "DP1-2" ) ( "DP1-2" )
May  2 18:31:25 mylaptop org.kde.KScreen[1473]: message repeated 60 times: [ kscreen: Primary output changed from KScreen::Output(Id: 70 , Name: "DP1-2" ) ( "DP1-2" ) to KScreen::Output(Id: 70 , Name: "DP1-2" ) ( "DP1-2" )]
May  2 18:31:25 mylaptop org.kde.KScreen[1473]: kscreen: Primary output changed from KScreen::Output(Id: 70 , Name: "DP1-2" ) ( "DP1-2" ) to KScreen::Output(Id: 70 , Name: "DP1-2" ) ( "DP1-2" )
May  2 18:31:25 mylaptop org.kde.KScreen[1473]: message repeated 18 times: [ kscreen: Primary output changed from KScreen::Output(Id: 70 , Name: "DP1-2" ) ( "DP1-2" ) to KScreen::Output(Id: 70 , Name: "DP1-2" ) ( "DP1-2" )]


After this, there are some other logs. But also a lot of messages like this:
May  2 18:31:33 mylaptop org.kde.KScreen[3012]: kscreen.xrandr: Connected output 67 to CRTC 63
May  2 18:31:33 mylaptop org.kde.KScreen[3012]: kscreen.xrandr: Connected output 70 to CRTC 64

I think KScreen wants to configure with xrandr the output and it seems to work?!.
Comment 2 paolo.perrone.int 2016-05-10 21:38:13 UTC
I can reproduce. 
ThinkPad T450s, fresh install of Kubuntu 16.04. 
Same long waiting time at the end of the splash, same messages in the system log. And during that "break" in the loading, the laptop fan runs very loudly.

But: this does not happen if I have a second monitor plugged in. In that case, the system loads normally without taking "breaks".
Comment 3 Justin Zobel 2020-11-08 10:58:49 UTC
Thanks for the reports.

I am unable to reproduce this issue on Plasma from git master.

Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved, thanks.
Comment 4 Bug Janitor Service 2020-11-23 04:33:58 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2020-12-08 04:34:23 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!