From kde-bugs-dist Sun Jan 31 21:39:13 2016 From: Mark Ferguson via KDE Bugzilla Date: Sun, 31 Jan 2016 21:39:13 +0000 To: kde-bugs-dist Subject: [KScreen] [Bug 355928] kscreen reports change of primary screen without apparent reason Message-Id: X-MARC-Message: https://marc.info/?l=kde-bugs-dist&m=145427636329381 https://bugs.kde.org/show_bug.cgi?id=3D355928 Mark Ferguson changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |markfergy@gmail.com --- Comment #13 from Mark Ferguson --- I had the same issue when in Kubuntu when I upgraded to Plasma 5.5.3 and KD= E=E2=80=99s Frameworks 5.18.0 from Plasma 5.4.3 and KDE Applications 15.08.3. Prior to = the upgrade I did not see this log message at all. org.kde.KScreen[1335]: kscreen: Primary output changed from KScreen::Output= (Id: 639 , Name: "DP-2" ) ( "DP-2" ) to KScreen::Output(Id: 639 , Name: "DP-2" )= ( "DP-2" ) I downgraded again to Plasma 5.4.3 (KDE Applications 15.08.3.) because the system logs where starting to fill up with these log messages. This error message comes form the libkscreen package (src/config.cpp) The method that prints this message is called void Config::setPrimaryOutput(const OutputPtr &newPrimary) It is actually classified as a debug message so I am wondering if it is a l= og level issue or a bug which is causing this method to be called more often t= han it should? As mention I do not see this message in the system logs on Plasma 5.4.3 (KDE Applications 15.08.3.). Though I could get the message on the command line = when running kscreen-console. I could also stop the message by creating ~/.config/QtProject/qtlogging.ini and adding: [Rules] kscreen.debug=3Dfalse I am guessing if upgrading again to Plasma 5.5.3 (KDE=E2=80=99s Frameworks = 5.18.0) the log messages could be turned of by adding the qtlogging.ini change above to= the /etc/xdg/QtProject/ directory. I haven't been able to test whether this would work and I will probably won= 't have time this week. I would also be reluctant to do this unless it can be confirmed that the calling of Config::setPrimaryOutput so many times is not= a bug? --=20 You are receiving this mail because: You are watching all bug changes.=