Description of problem: There is a log of error messages in systemd journal Version-Release number of selected component (if applicable): Mageia 7- ksreen. How reproducible: Review var/log/journal and error messages in konsole with: journalctl -l Steps to Reproduce: 1. Put in konsole journalctl -l 2. Export the output 3. Review the error messages of kscreen
On my computer, journal occupies 3.7 Gb, and on another computer other than 2 Gb with many Kscreen errors on both computers.
(In reply to Jose Manuel López from comment #1) > On my computer, journal occupies 3.7 Gb, and on another computer other than > 2 Gb with many Kscreen errors on both computers. What do you mean by 'journal'? For example, on my box $ du -s /var/log/journal/ 1.1G /var/log/journal/ but this contains 32 journal files of the order 10-100Mb. Doing what you did 'journalctl -l' showed the journals from months ago. To look at just the current session: $ journalctl -b --no-hostname [shortens the lines] and to see kscreen msgs for just the current session: $ journalctl -b --no-hostname | grep kscreen Running under Plasma here: $ journalctl -b | wc -l 2001 $ journalctl -b | grep kscreen | wc -l 86 showing just 86/2001 kscreen journal msgs for this session - admittedly a lot, but not excessive. Can you try these things to test whether your system is producing excessive kscreen journal messages? If it is, please do: $ journalctl -b --no-hostname | grep kscreen > kscreen.txt and attach that file to this bug. If the file is very big, please compress it first with 'xz'.
CC: (none) => lewyssmith
Does this still valid? Closing it on 2020-08-26.
CC: (none) => ouaurelien
There is some change upstream that such warning are gone in new versions of Plasma. Actually in Cauldron, Plasma 5.19.4 (KScreen) no longer produce error level log. Closing Worksome
CC: ouaurelien => (none)Resolution: (none) => WORKSFORMEKeywords: (none) => UPSTREAMStatus: NEW => RESOLVED