Bug 480963 - Kwin spams QObject::startTimer related warning in systemd journal during user input
Summary: Kwin spams QObject::startTimer related warning in systemd journal during user...
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 5.93.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2024-02-06 17:16 UTC by Ridge
Modified: 2024-03-08 03:47 UTC (History)
4 users (show)

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


Attachments
My kwinrc (3.45 KB, text/plain)
2024-02-06 17:16 UTC, Ridge
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ridge 2024-02-06 17:16:14 UTC
Created attachment 165621 [details]
My kwinrc

SUMMARY
In Plasma 6 RC2, once I start typing or moving my cursor, kwin spams "QObject::startTimer: Timers cannot have negative intervals" in the systemd journal. Several of these pop up every second.

If I don't move my mouse or use the keyboard, it stops.



STEPS TO REPRODUCE
1.  On a systemd based computer, sign in to a Plasma 6 RC2 session
2.  Execute journalctl -f in a terminal
3.  Move the mouse or type anywhere while observing the journal

OBSERVED RESULT
Almost hundreds of QObject::startTimer related warnings can pop up each second.

EXPECTED RESULT
Nothing special should be logged during input.

SOFTWARE/OS VERSIONS
Linux kernel: 6.7.4
KDE Plasma Version: 5.93.0
KDE Frameworks Version:  5.249.0
Qt Version: 6.7.0 Beta 2

ADDITIONAL INFORMATION
Tried two different mice just in case.

This does NOT happen on my Lenovo IdeaPad 5 Pro 16ACH6, which is also using Arch Linux with the same software versions mentioned above.

I have not had time to test in a Neon Unstable environment yet. I will do so later today.
Comment 1 Ridge 2024-02-06 17:25:10 UTC
I also can't reproduce this on a clean boot, but I have seen it a few times before the past week or so. Just can't figure out what triggers it.
Comment 2 Nate Graham 2024-02-06 20:27:26 UTC
I can't reproduce it right now, FWIW.
Comment 3 Ridge 2024-02-06 20:42:36 UTC
Yes, it seems tricky to reproduce, I'm keeping journalctl -f open while I use my computer to see if I can catch it. If it doesn't happen again for a while I'll just close this as a fluke, if that's preferable.
Comment 4 thecookie94 2024-02-07 11:16:10 UTC
Had this on my last boot as well. Will try to investigate more if I end up seeing it again as I don't know what triggers it either, unfortunately.
That last boot has been on for a while though and the system has been in sleep mode as well.

"Feb 06 10:58:33 HOSTNAME kwin_wayland[1383]: QObject::startTimer: Timers cannot have negative intervals" gets reported hundreds of times per second

arch, plasma 6 rc2, 3700x+5700xt
Comment 5 David Edmundson 2024-02-07 14:22:50 UTC
We are unsure which timer this is. Can you confirm if any other 3rd party scripts are running? We had a check for all ours but nothing was obvious.
If you can put a breakpoint on that line in qtimer.cpp from another computer that would be best.
Comment 6 Ridge 2024-02-07 14:37:27 UTC
Hi thecookie, thanks for confirming it's not just me.
I'll happily try to help and do what you requested David, but I'm not a developer, just a user, so it might take a bit of time to get that figured out 😁 I'll be looking up info on how to use breakpoints later, I also asked for help with it in the KDE Bugs Matrix room.
Comment 7 Bug Janitor Service 2024-02-22 03:46:18 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 8 Bug Janitor Service 2024-03-08 03:47:07 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!