Bug 435158 - kscreen_backend_launcher fills syslog
Summary: kscreen_backend_launcher fills syslog
Status: RESOLVED WORKSFORME
Alias: None
Product: KScreen
Classification: Plasma
Component: common (show other bugs)
Version: 5.21.3
Platform: Arch Linux Linux
: LO minor
Target Milestone: ---
Assignee: kscreen-bugs-null@kde.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-30 17:08 UTC by temptempor
Modified: 2022-12-08 05:15 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Example logs (8.15 KB, text/x-log)
2021-03-30 17:08 UTC, temptempor
Details

Note You need to log in before you can comment on or make changes to this bug.
Description temptempor 2021-03-30 17:08:50 UTC
Created attachment 137182 [details]
Example logs

SUMMARY

Getting loads of messages about my screen configuration though nothing changes.


STEPS TO REPRODUCE
1. Have two screens?
2. Be on Plasma 5.2x.x


OBSERVED RESULT
3. Lost and lots of messages generated nearly every minute about screens

EXPECTED RESULT
I didn't change my screen config so I expected nothing to be logged? Can we have a button to just disable all those logs? Because of course kscreen isn't in the scope of kdebugdialog5.

SOFTWARE/OS VERSIONS

Operating System: Arch Linux
KDE Plasma Version: 5.21.3
KDE Frameworks Version: 5.80.0
Qt Version: 5.15.2
Kernel Version: 5.11.10
OS Type: 64-bit
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor
Memory: 31.3 Gio of RAM
Graphics Processor: AMD RX6900XT

ADDITIONAL INFORMATION

Example:

> mars 30 19:04:18 PHARCHXTI kscreen_backend_launcher[4442]: kscreen.xrandr: XRandR::setConfig
mars 30 19:04:18 PHARCHXTI kscreen_backend_launcher[4442]: kscreen.xrandr: Requested screen size is QSize(2560, 1440)
mars 30 19:04:18 PHARCHXTI kscreen_backend_launcher[4442]: kscreen.xrandr: Needed CRTCs:  1
mars 30 19:04:18 PHARCHXTI kscreen_backend_launcher[4442]: kscreen.xrandr: Actions to perform: 
                                                                    Primary Output: false
[...]
Comment 1 Nate Graham 2022-11-08 22:00:16 UTC
Thank you for the bug report. Unfortunately we were not able to get to it yet. Can we ask you to please check if this is still an issue with Plasma 5.25 or 5.26?

If it is, please change the status to CONFIRMED when replying. If not, or if you can't because you no longer use this setup, you can change the status to RESOLVED WORKSFORME. Thanks a lot!
Comment 2 Bug Janitor Service 2022-11-23 05:15:56 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2022-12-08 05:15:27 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!