https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #22 from Jonathan Lopes <joniwe...@gmail.com> --- Created attachment 166664 --> https://bugs.kde.org/attachment.cgi?id=166664&action=edit gdb output from QObject::startTimer breakpoint (In reply to Dāvis from comment #21) > Created attachment 166630 [details] > kwin_wayland > > (In reply to Jonathan Lopes from comment #16) > > [...] > > If I had enough time, I could try to plug a debugger on kwin_wayland to find > > what is causing this problem. However, I have basically zero experience with > > C++ debugging (although I can figure out with basic directions), so even if > > I find some time to do it, I don't even know where to start. > > It's described in > https://community.kde.org/KWin/Debugging#TL;DR_for_bug_reporters > But I think "continue" there is wrong, atleast that didn't work for me, but > this worked fine > $ sudo -E gdb -pid (pidof kwin_wayland) -batch -ex "thread apply all > backtrace" I should've read the documentation first, would've saved me a lot of time, but there it is, I've attached the backtrace from two calls to QObject::startTimer with a negative interval, both points to the same location: > #0 QObject::startTimer > (this=0x58f34afb5dc0, interval=std::chrono::duration = { -1ms }, > timerType=Qt::CoarseTimer) > at > /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qobject.cpp:1883 > #1 0x000077a34d9991f7 in QTimer::start (this=0x58f34afb5dc0) > at > /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qtimer.cpp:192 > #2 0x000077a3502041ee in KWin::IdleDetector::activity (this=0x58f34bc25920) > at /usr/src/debug/kwin/kwin-6.0.1/src/idledetector.cpp:53 > #3 KWin::IdleDetector::activity (this=0x58f34bc25920) > at /usr/src/debug/kwin/kwin-6.0.1/src/idledetector.cpp:50 > #4 0x000077a35021636d in KWin::InputRedirection::simulateUserActivity > (this=<optimized out>) > at /usr/src/debug/kwin/kwin-6.0.1/src/input.cpp:3235 -- You are receiving this mail because: You are watching all bug changes.
