Summary: | Crash in QAbstractAnimationJob::stateChanged while Konversation is running | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | jy6x2b32pie9 |
Component: | generic-crash | Assignee: | Plasma Bugs List <plasma-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | 7c6s4b+cc6efdty3btf0, akselmo, bugseforuns, email, jfebrer, kde, kdebugs, kdedev, mdeneen+kde, nate, notmart, ped, ulterno |
Priority: | HI | Keywords: | drkonqi, multiscreen, qt-crash |
Version First Reported In: | 6.1.0 | ||
Target Milestone: | 1.0 | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | Qt 6.9.2 | |
Sentry Crash Report: | https://crash-reports.kde.org/organizations/kde/issues/7089/ | ||
Attachments: |
New crash information added by DrKonqi
backtrace |
Description
jy6x2b32pie9
2024-05-28 17:13:14 UTC
Created attachment 169917 [details]
New crash information added by DrKonqi
DrKonqi auto-attaching complete backtrace.
#6 0x00007f172c089f9b in QAbstractAnimationJob::stateChanged (this=this@entry=0x7f171c085d30, newState=newState@entry=QAbstractAnimationJob::Running, oldState=oldState@entry=QAbstractAnimationJob::Stopped) at /var/tmp/portage/dev-qt/qtdeclarative-6.7.1/work/qtdeclarative-everywhere-src-6.7.1/src/qml/animations/qabstractanimationjob.cpp:601 #7 0x00007f172c0ae362 in QAbstractAnimationJob::setState (this=0x7f171c085d30, newState=QAbstractAnimationJob::Running) at /var/tmp/portage/dev-qt/qtdeclarative-6.7.1/work/qtdeclarative-everywhere-src-6.7.1/src/qml/animations/qabstractanimationjob.cpp:352 #8 QAbstractAnimationJob::setState (this=0x7f171c085d30, newState=QAbstractAnimationJob::Running) at /var/tmp/portage/dev-qt/qtdeclarative-6.7.1/work/qtdeclarative-everywhere-src-6.7.1/src/qml/animations/qabstractanimationjob.cpp:297 #9 0x00007f172c897382 in QQuickAnimatorController::beforeNodeSync (this=<optimized out>) at /usr/include/qt6/QtCore/qsharedpointer_impl.h:274 #10 0x00007f172ca2d0af in QQuickWindowPrivate::syncSceneGraph (this=0x5600316d7270) at /usr/include/qt6/QtCore/qscopedpointer.h:90 #11 0x00007f172c7bab75 in QSGRenderThread::sync (this=this@entry=0x56002ff82440, inExpose=inExpose@entry=true) at /var/tmp/portage/dev-qt/qtdeclarative-6.7.1/work/qtdeclarative-everywhere-src-6.7.1/src/quick/scenegraph/qsgthreadedrenderloop.cpp:552 #12 0x00007f172c7d8af3 in QSGRenderThread::syncAndRender (this=this@entry=0x56002ff82440) at /var/tmp/portage/dev-qt/qtdeclarative-6.7.1/work/qtdeclarative-everywhere-src-6.7.1/src/quick/scenegraph/qsgthreadedrenderloop.cpp:715 #13 0x00007f172c7e18f3 in QSGRenderThread::run (this=0x56002ff82440) at /var/tmp/portage/dev-qt/qtdeclarative-6.7.1/work/qtdeclarative-everywhere-src-6.7.1/src/quick/scenegraph/qsgthreadedrenderloop.cpp:974 #14 0x00007f172b1eb19d in operator() (__closure=<optimized out>) at /var/tmp/portage/dev-qt/qtbase-6.7.1/work/qtbase-everywhere-src-6.7.1/src/corelib/thread/qthread_unix.cpp:326 #15 (anonymous namespace)::terminate_on_exception<QThreadPrivate::start(void*)::<lambda()> > (t=<optimized out>) at /var/tmp/portage/dev-qt/qtbase-6.7.1/work/qtbase-everywhere-src-6.7.1/src/corelib/thread/qthread_unix.cpp:262 #16 QThreadPrivate::start (arg=0x56002ff82440) at /var/tmp/portage/dev-qt/qtbase-6.7.1/work/qtbase-everywhere-src-6.7.1/src/corelib/thread/qthread_unix.cpp:285 #17 0x00007f172abf9821 in ??? () at /usr/lib64/libc.so.6 #18 0x00007f172ac7b96c in ??? () at /usr/lib64/libc.so.6 *** Bug 486912 has been marked as a duplicate of this bug. *** *** Bug 485798 has been marked as a duplicate of this bug. *** *** Bug 481718 has been marked as a duplicate of this bug. *** We believe this is fixed in Qt, please reopen if an issue persists with Qt 6.8 *** Bug 495581 has been marked as a duplicate of this bug. *** Bug 495581 experiences the crash with Qt 6.8.0; re-opening. *** Bug 494760 has been marked as a duplicate of this bug. *** Created attachment 179380 [details]
backtrace
It crashes. It still crashes.
Operating System: Gentoo Linux 2.17
KDE Plasma Version: 6.3.3
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.13.7-gentoo (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5700U with Radeon Graphics
Memory: 15.0 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: LENOVO
Product Name: 82KD
System Version: Lenovo V15 G2 ALC
window has bogus value, qt tries to unwind exception, dereferences bogus value that points to unmapped memory and crashes... *** Bug 499324 has been marked as a duplicate of this bug. *** This has 30 events in Sentry, and a number of duplicate report. Marking as High I can reproduce this at will and able to perform whatever procedures needed to find the cause, saw crashes with gdb attached. Have qtbase, qtdeclarative and plasmashell build with -Og -ggdb already... If I connect to laptop with crashing plasmashell over ssh and do `loginctl unlock-session` then plasmashell doesn't crash... Or not. Apparently, it decided not to crash only once, and resumed crashing afterwards. I think I isolated cause of the crash? If konversation is running, plasmashell crashes. If konversation is not running, plasmashell survives lock and unlock, (In reply to jy6x2b32pie9 from comment #17) > I think I isolated cause of the crash? If konversation is running, > plasmashell crashes. If konversation is not running, plasmashell survives > lock and unlock, Hey, I can confirm that I use Konversation, so that's an interesting find! I'm not able to reproduce this right now on git-master Screen lock timeout - 1 min Konversation running 1. Laptop closed with external monitor attached, disable laptop monitor in settings. 2. Turn off monitor. 3. Let KDE lock screen. 4. Turn monitor on (for me it turns on automatically when the laptop lid is opened) 5. Unlock KDE. Leaving this for more experienced plasmashell contributors to look at Can you try: Laptop. External monitor connected, Konversation is running, lid is closed. External keyboard is connected. 1. Lock screen with Meta-L (or your shortcut for screenlock) 2. Press Esc to blank and turn off monitor. 3. Wait a little. 4. Press any key to bring monitor back, to KDE lock screen. There is double click of hardware disconnecting and connecting sounds. 5. Unlock. 6. Plasma crashes for me. (In reply to TraceyC from comment #19) > I'm not able to reproduce this right now on git-master > > Screen lock timeout - 1 min > Konversation running > 1. Laptop closed with external monitor attached, disable laptop monitor in > settings. > 2. Turn off monitor. > 3. Let KDE lock screen. > 4. Turn monitor on (for me it turns on automatically when the laptop lid is > opened) > 5. Unlock KDE. > > Leaving this for more experienced plasmashell contributors to look at If you are on IRC I can send you a message while your desktop is locked. Perhaps the bug is triggered by Konversation presenting a notification while the screen is locked? *** Bug 504131 has been marked as a duplicate of this bug. *** *** Bug 506952 has been marked as a duplicate of this bug. *** I tried to repro this but had no luck. What I tried was: - set screen to turn off on locking - open konversations and connect to network - close it to tray - lock screen and it turns off Then on anothee device i send a query, but no crash. I also tried to keep systemtray pinned open, so that it covers the area where the notification pops up. But didnt work either. (In reply to Akseli Lahtinen from comment #24) > I tried to repro this but had no luck. > > What I tried was: > > - set screen to turn off on locking > - open konversations and connect to network > - close it to tray > - lock screen and it turns off > > Then on anothee device i send a query, but no crash. > > I also tried to keep systemtray pinned open, so that it covers the area > where the notification pops up. But didnt work either. Forgot to share my system info Operating System: Fedora Linux 42 KDE Plasma Version: 6.4.80 KDE Frameworks Version: 6.17.0 Qt Version: 6.9.1 Kernel Version: 6.15.7-200.fc42.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 16 GiB of RAM (15.5 GiB usable) Graphics Processor: AMD Radeon RX 6600 Well. Changed hardware. Now I can't replicate it myself. Sentry has 270 events with 19 user reports, as recently as 3 days ago, so this is definitely still ongoing. Different reported causes: - System wake - Connecting to TV over HDMI - Connecting / reconnecting external monitor - KDE Wallet Sentry implies this is fixed with Qt 6.9.2. Please open a new ticket if this crash occurs again |