Bug 370915 - kscreen is filling log with events after each resume
Summary: kscreen is filling log with events after each resume
Status: RESOLVED NOT A BUG
Alias: None
Product: KScreen
Classification: Plasma
Component: common (show other bugs)
Version: 5.8.0
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Sebastian Kügler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-15 13:42 UTC by Bruno Friedmann
Modified: 2016-11-10 12:22 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
Kscreen excessive logs (53.30 KB, text/plain)
2016-10-15 13:43 UTC, Bruno Friedmann
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bruno Friedmann 2016-10-15 13:42:03 UTC
Until 5.8.0 was delivered to openSUSE Tumbleweed, a monitor resume event was producing no logging.
Now each time there's a suspend or wake up event with monitor you get over verbose information in systems logs.



Reproducible: Always

Steps to Reproduce:
1. Install 5.8.0 plasma and kscreen related component
2. Wait a suspend monitor event
3. Wake up the monitor

Actual Results:  
Oct 15 15:23:54 qt-kt.labaroche.ioda.net org.kde.KScreen[3598]: kscreen.xcb.helper: RRNotify_OutputProperty (ignored)
---- too much line to be included as comment for bugzilla, see attachement ---
Oct 15 15:23:58 qt-kt.labaroche.ioda.net org.kde.KScreen[3598]: kscreen.xrandr: Emitting configChanged()


Expected Results:  
One line of log

As this abnormal behavior look like the old bug 
https://bugs.kde.org/show_bug.cgi?id=361688

I've checked the status of variables in ~/.config/QtProject/qtlogging.ini 
kscreen.kded=false
kscreen=false
kscreen.edid=false
kscreen.fake=false
kscreen.qscreen=false
kscreen.xcb.helper=false
kscreen.xcb_helper=false
kscreen.xrandr=false
kscreen.xrandr11=false

even if the file is no more present the log are still recorded.
Comment 1 Bruno Friedmann 2016-10-15 13:43:55 UTC
Created attachment 101574 [details]
Kscreen excessive logs
Comment 2 Bruno Friedmann 2016-10-15 13:47:00 UTC
I'm using kernel 4.7.6 + nvidia 370.28 proprietary drivers
Comment 3 Sebastian Kügler 2016-11-10 12:22:08 UTC
Have you tried kscreen.*=false or kscreen.xcb.helper.*=false?


We need this logging in order to fix problems, I don't plan to remove it in the near future.