[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-bugs-dist
Subject: [KScreen] [Bug 355928] kscreen reports change of primary screen without apparent reason
From: Mark Ferguson via KDE Bugzilla <bugzilla_noreply () kde ! org>
Date: 2016-01-31 21:39:13
Message-ID: bug-355928-17878-DX4Or6WqUJ () http ! bugs ! kde ! org/
[Download RAW message or body]
https://bugs.kde.org/show_bug.cgi?id=355928
Mark Ferguson <markfergy@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |markfergy@gmail.com
--- Comment #13 from Mark Ferguson <markfergy@gmail.com> ---
I had the same issue when in Kubuntu when I upgraded to Plasma 5.5.3 and KDE's
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 log
level issue or a bug which is causing this method to be called more often than
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=false
I am guessing if upgrading again to Plasma 5.5.3 (KDE's 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?
--
You are receiving this mail because:
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic