| Summary: | Random crashing | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Sid <me> |
| Component: | generic-crash | Assignee: | Sid <me> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | adeptsmail, alexeya, git, kde, nate, qydwhotmail |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 5.27.1 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Plasmashell backtrace
Plasmashell error when run from console |
||
|
Description
Sid
2023-02-25 10:44:21 UTC
Darn, sorry this is happening. Any chance you can install debug symbols for Plasma and get a new backtrace? Created attachment 156911 [details]
Plasmashell backtrace
this is the backtrace
Created attachment 156912 [details]
Plasmashell error when run from console
This is an error I got from running plasmashell via console (`plasmashell -n -d`). This was not the same run as the one with the backtrace (since i kinda forgot to run `thread apply all backtrace` (woops sorry), but this error has also happened a few times)
Hi there No problem! You guys are doing amazing work. I have attached the backtrace as well as a crash image now, please let me know if i can provide anything else that might help with the diagnosis Thanks Thanks! Unfortunately the new backtrace you've provided doesn't look the same as the original one, and it's not clear there's a crash at all. "QBuffer::writeData: memory allocation error" doesn't look good either . :/ Oh yeah, I see. Could it be that multiple things are causing it to crash? should I maybe record multiple backtraces and add them all? Hi, yeah I think I'm fairly certain that its something to do with the taskbar, the taskbar is the most visible issue when plasmashell dies. now i dont know if its a cause or a symptom, but more often then not its the taskbar that freezes first (with everything else working just fine) before everything comes crashing down Hi. I have similar symptoms: plasma crashes 5-10 times per day. KDE Neon user 5.27.2 Qt Version: 5.15.8 Kernel: 5.19 AMD graphics as well, X11 session. I feel that it started with 5.26 or 5.25. Maybe this string from logs could be meaningful: Mar 12 11:05:34 adept-XPS-13-9360 kwin_x11[1331661]: kwin_core: XCB error: 152 (BadDamage), sequence: 58753, resource id: 5517981, major code: 143 (DAMAGE), minor code: 3 (Subtract) For me, most often, it reproduces when I have multiple notifications simultaneously. But even without a notification, it can crash. Please LMK if I can help somehow. Thanks I'm also getting multiple random daily crashes. Although the mouse still works, all windows are frozen. Getting to a terminal with Alt-Ctrl-F2, I can see processes still running. I have tried a few things from there. If I try to kill and restart plasmashell, I get errors:
qt.qpa.xcb: could not connect to display
qt.qpa.plugin: Count not load the Qt platform plugin "xcb" in "" even through it was found.
This application failed to start because no Qt platform plugin could be initiatlized.
In order to recover I thus have to do a hard reboot.
In the journalctl logs, besides the type of entries already mentioned (kwin_x11: kwin_core: XCB error: 152 (BadDamage)), I also see the following type of entry about 10 to 15 seconds before the whole window manager freezes over:
plasmashell[2151]: Could not find the Plasmoid for Plasma::FrameSvgItem(0x56017bc10820) QQmlContext(0x560177a81aa0) QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
plasmashell[2151]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationItem.qml:220:21: QML SelectableLabel: Binding loop detected for property "implicitHeight"
I really don't know whether this bears any relationship to the problem.
Operating System: Kubuntu 22.10
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.6
Kernel Version: 5.19.0-35-generic (64-bit)
Graphics Platform: X11
Processors: 20 × 12th Gen Intel® Core™ i7-12700H
Memory: 31,1 GiB of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: LENOVO
Product Name: 21DES04W00
System Version: ThinkPad X1 Extreme Gen 5
Can confirm.
==========
Operating System: KDE neon 5.27
KDE Plasma Version: 5.27.3
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 5.19.0-35-generic (64-bit)
Graphics Platform: X11
Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz
Memory: 15.3 GB of RAM
=================
In random case kwin crashes.
~/.xsession-errors says nothing
syslog is very poor:
=>
Mar 19 12:30:35 notebook-a kwin_x11[141060]: kwin_core: XCB error: 152 (BadDamage), sequence: 1670, resource id: 16777259, major code: 143 (DAMAGE), minor code: 3 (Subtract)
Some logs before crash:
....
Mar 19 12:30:35 notebook-a plasmashell[141120]: file:///home/user/.local/share/plasma/plasmoids/org.kde.plasma.eventcalendar/contents/ui/MeteogramView.qml:36:2: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
Mar 19 12:30:35 notebook-a plasmashell[141120]: file:///home/user/.local/share/plasma/plasmoids/org.kde.plasma.eventcalendar/contents/ui/PopupView.qml:85:2: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
Mar 19 12:30:35 notebook-a plasmashell[141120]: file:///home/user/.local/share/plasma/plasmoids/org.kde.plasma.eventcalendar/contents/ui/DaysCalendar.qml:425:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
Mar 19 12:30:35 notebook-a plasmashell[141120]: message repeated 83 times: [ file:///home/user/.local/share/plasma/plasmoids/org.kde.plasma.eventcalendar/contents/ui/DaysCalendar.qml:425:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }]
Mar 19 12:30:35 notebook-a plasmashell[141120]: file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/private/containmentlayoutmanager/BasicAppletContainer.qml:169: TypeError: Cannot read property 'width' of null
Mar 19 12:30:35 notebook-a plasmashell[141120]: org.kde.plasma.containmentlayoutmanager: Error: cannot change the containment to AppletsLayout
Mar 19 12:30:35 notebook-a plasmashell[141120]: org.kde.plasma.containmentlayoutmanager: Error: cannot change the containment to AppletsLayout
Mar 19 12:30:35 notebook-a akonadiserver[141368]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Mar 19 12:30:35 notebook-a plasmashell[141120]: org.kde.plasma.containmentlayoutmanager: Error: cannot change the containment to AppletsLayout
Mar 19 12:30:35 notebook-a plasmashell[141120]: org.kde.plasma.containmentlayoutmanager: Error: cannot change the containment to AppletsLayout
Mar 19 12:30:35 notebook-a plasmashell[141120]: 13
Mar 19 12:30:35 notebook-a kwin_x11[141060]: kwin_core: XCB error: 152 (BadDamage), sequence: 1670, resource id: 16777259, major code: 143 (DAMAGE), minor code: 3 (Subtract)
@Jean-Sébastien Caux, how do you try to start plasmashell? DISPLAY=:0.0 plasmashell ? Today I restarted plasmashell killall plasmashell && kstart5 plasmashell and saw some new errors when it failed: QWidget::paintEngine: Should no longer be called QPainter::begin: Paint device returned engine == 0, type: 1 QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setCompositionMode: Painter not active QPainter::setCompositionMode: Painter not active qt.gui.imageio.jpeg: Corrupt JPEG data: premature end of data segment (In reply to Yuriy Vidineev from comment #11) > @Jean-Sébastien Caux, how do you try to start plasmashell? > DISPLAY=:0.0 plasmashell ? I was trying `killall plasmashell && plasmashell &` and also `killall kwin_x11 && kwin_x11 --replace` and also `kquitapp plasmashell` and the `kstart5 plasmashell` but none of those worked. *** This bug has been marked as a duplicate of bug 460895 *** |