https://bugs.kde.org/show_bug.cgi?id=460081
aux...@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDSINFO |REPORTED Resolution|BACKTRACE |--- --- Comment #2 from aux...@gmail.com --- This is 100% reproducible. The backtrace looks similar to the one in https://bugs.kde.org/show_bug.cgi?id=459860: >#0 0x00007f363bd21de6 in KWin::Workspace::takeActivity(KWin::Window*, >QFlags<KWin::Workspace::ActivityFlag>) ?(this=0x5636d25e5460, >window=0x5636d2961220, flags=...) > at /usr/src/debug/kwin5-5.25.5-1.2.x86_64/src/activation.cpp:355 >#1 0x00007f363be5a8bf in KWin::Workspace::delayFocus() (this=0x5636d25e5460) >at /usr/src/debug/kwin5-5.25.5-1.2.x86_64/src/workspace.cpp:1343 >#2 0x00007f363aa6405d in () at /lib64/libQt5Core.so.5 >#3 0x00007f363aa67e9a in QTimer::timeout(QTimer::QPrivateSignal) () at >/lib64/libQt5Core.so.5 >#4 0x00007f363aa587ed in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 >#5 0x00007f3639f4a3fe in QApplicationPrivate::notify_helper(QObject*, >QEvent*) () at /lib64/libQt5Widgets.so.5 >#6 0x00007f363aa2d178 in QCoreApplication::notifyInternal2(QObject*, QEvent*) >() at /lib64/libQt5Core.so.5 >#7 0x00007f363aa83c01 in QTimerInfoList::activateTimers() () at >/lib64/libQt5Core.so.5 >#8 0x00007f363aa821e0 in >QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () >at /lib64/libQt5Core.so.5 >#9 0x00005636d058781d in >QUnixEventDispatcherQPA::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) >(this=<optimized out>, flags=...) at qunixeventdispatcher.cpp:63 >#10 0x00007f363aa2bbeb in >QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at >/lib64/libQt5Core.so.5 >#11 0x00007f363aa33d56 in QCoreApplication::exec() () at /lib64/libQt5Core.so.5 >#12 0x00005636d04b39a0 in main(int, char**) (argc=<optimized out>, >argv=<optimized out>) at >/usr/src/debug/kwin5-5.25.5-1.2.x86_64/src/main_wayland.cpp:642 -- You are receiving this mail because: You are watching all bug changes.