https://bugs.kde.org/show_bug.cgi?id=444084
pa...@web.de changed: What |Removed |Added ---------------------------------------------------------------------------- Component|common |libkscreen --- Comment #1 from pa...@web.de --- Some additional observations: The output is defined in libkscreen, not in kscreen itself. Therefore, I changed relevant component. Inside kscreen, the output is, e.g., defined in backends/xrandr/xrandrconfig.cpp or backends/xcbeventlistener.cpp. There, qCDebug is used as output function, which seems to be correct on first look, because especially qCWarning is not used (as for other warnings in the file which are not triggered). The journal does not get the messages via the regular logging mechanisms, but really via stdout, which can be shown by using "journalctl --priority warning --boot -o verbose". A shortened output looks like this: Wed 2021-10-20 06:43:05.567398 CEST _TRANSPORT=stdout _UID=1000 _GID=1000 _SYSTEMD_OWNER_UID=1000 _SYSTEMD_UNIT=user@1000.service _SYSTEMD_SLICE=user-1000.slice PRIORITY=4 _SYSTEMD_CGROUP=/user.slice/user-1000.slice/user@1000.service/app.slice/dbus.service _SYSTEMD_USER_UNIT=dbus.service _SYSTEMD_USER_SLICE=app.slice SYSLOG_IDENTIFIER=org.kde.KScreen _COMM=kscreen_backend _EXE=/usr/lib/x86_64-linux-gnu/libexec/kf5/kscreen_backend_launcher _CMDLINE=/usr/lib/x86_64-linux-gnu/libexec/kf5/kscreen_backend_launcher MESSAGE=kscreen.xcb.helper: RRNotify_CrtcChange _PID=1325 -- You are receiving this mail because: You are watching all bug changes.