Summary: | Plasma crash right after login | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Andrei Rybak <rybak.a.v> |
Component: | generic-crash | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | burneddi, d.christopeit, lemondejojo, nate, plasma-bugs, rocketraman, shoppa0815, t.zaspel |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.23.2 | ||
Target Milestone: | 1.0 | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
New crash information added by DrKonqi
journal output at the time of the crash New crash information added by DrKonqi |
Description
Andrei Rybak
2021-10-31 22:30:30 UTC
I observe the same bug on Kubuntu 21.10 (with enabled kde backport's ppa, thus currently using plasmashell 5.23.2). I also notice that whenever this bug occurred, I am no longer able to modify graphical shell components. The bug happens about 80% of the times at session start. Sometimes, running `pkill plasmashell && sleep 5s && plasmashell` from Krunner helps, sometimes the bug fires again then. Created attachment 143611 [details]
New crash information added by DrKonqi
plasmashell (5.23.2) using Qt 5.15.2
- What I was doing when the application crashed:
1. Start my Laptop (Tuxedo Infinity Book S 15 (Gen 6 with OpenSUSE thumbleweed).
2. Type in the password for drive encryption.
3. Type in the password to login.
4. I got the report, that KDE is crashed.
- Unusual behavior I noticed:
Not sure but to my mind this bug occures since I tried out KDE with Wayland.
-- Backtrace (Reduced):
#6 QQuickWindowPrivate::dirtyItem (this=0x37) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.1.x86_64/src/quick/items/qquickwindow.cpp:1335
#7 0x00007fb8fded1248 in QQuickItemPrivate::dirty (this=this@entry=0x5627f6c849d0, type=type@entry=QQuickItemPrivate::ChildrenChanged) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.1.x86_64/src/quick/items/qquickitem.cpp:6189
#8 0x00007fb8fded9755 in QQuickItemPrivate::addChild (this=0x5627f6c849d0, child=<optimized out>, child@entry=0x7fb8e8019830) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.1.x86_64/src/quick/items/qquickitem.cpp:2929
#9 0x00007fb8fdedb832 in QQuickItem::setParentItem (this=0x7fb8e8019830, parentItem=parentItem@entry=0x5627f6c86ab0) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.1.x86_64/src/quick/items/qquickitem.cpp:2702
#10 0x00007fb8fdefe780 in qquickitem_autoParent (obj=0x7fb8e8019830, parent=0x5627f6c86ab0) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde36-1.1.x86_64/src/quick/items/qquickitemsmodule.cpp:139
*** Bug 447063 has been marked as a duplicate of this bug. *** *** Bug 446993 has been marked as a duplicate of this bug. *** One piece of important information, at least in my case, is that the crash happens when my monitors wake up, not at the actual login. It's possible that my case is also related to monitors waking up. I'm using a laptop with external monitor. Laptop's monitor is disabled, but it only applies after logging into Plasma. Created attachment 144636 [details]
journal output at the time of the crash
Not completely sure if this is the same crash, but seeing you mention monitors makes me suspect it is. In my case this has been happening since I got a new monitor that is a different resolution than my other monitor (and different orientation; I run my secondary monitor in portrait mode), so I think in my case it's caused by two different-resolution monitors waking up. One of my monitors takes 5-10 seconds longer to wake up than the other, which may also have a contributing effect.
In my case the issue is far older than this report (I've been having it since November 2020, when I got a new monitor), but for a while it went away when I switched from an NVidia GPU to an AMD one -- only to return after I upgraded to Plasma 5.23.
I'm attaching journal output from one crash from a few days ago.
PS: at least on Fedora the easiest way to restart Plasmashell is with "systemctl --user restart plasma-plasmashell". If your system doesn't have a systemd service for Plasmashell for some reason, you can use something like this, though beware that any error output from Plasmashell will be discarded if you do this: "nohup plasmashell --replace &> /dev/null & disown"
I have a multi-monitor setup also. 3 monitors, all the same resolution. 2/3 are a different model than the other (though same brand, Dell). In my case the monitors do wake up at different times as well, though in my case that seems to more be a function of the video card than the monitor model, and there is not a significant difference between them. (In reply to burneddi from comment #7) > at least on Fedora the easiest way to restart Plasmashell is with "systemctl --user restart plasma-plasmashell" On Fedora, is this a new approach to running Plasmashell? Interestingly, if I run plasmashell this way, as opposed to just restarting it the way I always used to (`kstart plasmashell &> /dev/null`) it no longer crashes on monitor wakeup. It still crashes for me even though it runs as a systemd service. Not every time, but maybe 70% of the time when my monitors wake up. (In reply to burneddi from comment #10) > It still crashes for me even though it runs as a systemd service. Not every > time, but maybe 70% of the time when my monitors wake up. I can confirm this as well. I still do get crashes on monitor wake-up, even when running as a systemd service. You would think crashers with backtraces would be easy to fix... *** This bug has been marked as a duplicate of bug 396359 *** The crash (at least the one reported in dup issue https://bugs.kde.org/show_bug.cgi?id=446993) no longer happens for me on: Operating System: Fedora Linux 35 KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.12-200.fc35.x86_64 (64-bit) Graphics Platform: X11 Created attachment 152443 [details]
New crash information added by DrKonqi
plasmashell (5.24.4) using Qt 5.15.2
- What I was doing when the application crashed:
* Log in after a fresh start
* Crash symbol appears in taskbar before doing anything productive.
-- Backtrace (Reduced):
#4 QQuickWindowPrivate::dirtyItem (this=0x1) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-150400.2.5.x86_64/src/quick/items/qquickwindow.cpp:1334
#5 0x00007f4ff8738d25 in QQuickItemPrivate::dirty (this=<optimized out>, type=<optimized out>) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-150400.2.5.x86_64/src/quick/items/qquickitem.cpp:6189
#6 0x00007f4ff873a1e9 in QQuickItem::setImplicitSize (this=0x3077310, w=<optimized out>, h=<optimized out>) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-150400.2.5.x86_64/src/quick/items/qquickitem.cpp:6979
#7 0x00007f4ff87a693b in QQuickImage::pixmapChange (this=0x3077310) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-150400.2.5.x86_64/src/quick/items/qquickimage.cpp:845
#8 0x00007f4ff87a44d4 in QQuickImageBase::requestFinished (this=0x3077310) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-150400.2.5.x86_64/src/quick/items/qquickimagebase.cpp:385
|