https://bugs.kde.org/show_bug.cgi?id=362590
--- Comment #1 from flo <flol2...@aol.com> --- 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?!. -- You are receiving this mail because: You are watching all bug changes.
