| Summary: | kscreen floods .xsession-errors with messages | ||
|---|---|---|---|
| Product: | [Plasma] KScreen | Reporter: | Vadym Krevs <vkrevs> |
| Component: | kded | Assignee: | Daniel Vrátil <dvratil> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | diegocg, kde, rafaelalcantaraperez, sebas, thiago |
| Priority: | NOR | ||
| Version First Reported In: | 5.5.2 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Vadym Krevs
2016-01-06 10:21:44 UTC
Also, systemd's journal is filled with numerous identical messages ( at least 20000) Jan 07 14:54:59 HOSTNAME org.kde.KScreen[29960]: kscreen: Primary output changed from KScreen::Output(Id: 735 , Name: "DVI-I-1" ) ( "DVI-I-1" ) to KScreen::Output(Id: 735 , Name: "DVI-I-1" ) ( "DVI-I-1" ) <AOL> Me too </AOL> Can't see why it is telling us it is setting something to which it already has been set. I assume this is to do with screens not being shown when the main monitor has been disconnected. Nope, my two monitors at work (and the single laptop screen at home) are not being physically connected and disconnected all the time ... Can confirm...I only have one screen, I have never disconnected it, but every few minutes I get this: kscreen: Primary output changed from KScreen::Output(Id: 71 , Name: "HDMI3" ) ( "HDMI3" ) to KScreen::Output(Id: 71 , Name: "HDMI3" ) ( "HDMI3" ) kscreen: Primary output changed from KScreen::Output(Id: 71 , Name: "HDMI3" ) ( "HDMI3" ) to KScreen::Output(Id: 71 , Name: "HDMI3" ) ( "HDMI3" ) Confirmed. FWIW, the messages seem to have disappeared in the latest Plasma release (5.6) 5.6.2 here and it's still producing debugging output. Thiago, are you sure you have - libkscreen 5.6.2 installed? - restarted your kded5 in the past few months? ;) I've removed the bogus debug message in libkscreen dcc520fe3715 which is from last November. There are still a lot of messages, but nowhere as many as before. I don't think I should call this a flood anymore. Messages are like: [ 312.010] kded5(1693 1693): kscreen: starting external backend launcher for "" [ 312.011] plasmashell(1748 1748): kscreen: starting external backend launcher for "" [ 312.013] kwin(1728 1728): QXcbConnection: XCB error: 3 (BadWindow), sequence: 63480, resource id: 20971528, major code: 18 (ChangeProperty), minor code: 0 [ 312.024] kded5(1693 1693): kscreen.kded: Change detected [ 312.310] kded5(1693 1693): kscreen.kded: Saving current config to file [ 312.310] kded5(1693 1693): kscreen.kded: Calculating config ID for KScreen::Config(0x26b1740) [ 312.310] kded5(1693 1693): kscreen.kded: Part of the Id: "8f1a4a6b5eec2d11cb59060b47b3610a" [ 312.310] kded5(1693 1693): kscreen.kded: Config ID: "b0002e5da0363ca4c838e70f9a3faa6c" [ 312.310] kded5(1693 1693): kscreen.kded: Config saved on: "/home/thiago/.local/share/kscreen/b0002e5da0363ca4c838e70f9a3faa6c" It happens in bursts. It might be due to a faulty connection... It's not a faulty connection, it's actually useful debug output (we have some bugs involving dynamic screen configuration, that's where we need this information -- I hope we'll be able to get rid of it rather sooner than later, of course). I've changed it to categorized logging, so you can disable it. Categories are in kdebugsettings, but disabling kscreen.* will help as well. |