Bug 413481 - plasmashell crashes in Plasma::FrameSvgPrivate::generateBackground() on login
Summary: plasmashell crashes in Plasma::FrameSvgPrivate::generateBackground() on login
Status: RESOLVED WORKSFORME
Alias: None
Product: libplasma
Classification: Frameworks and Libraries
Component: libplasmaquick (other bugs)
Version First Reported In: 5.63.0
Platform: Exherbo Linux
: NOR crash
Target Milestone: ---
Assignee: Marco Martin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-10-26 15:57 UTC by Ingmar Vanhassel
Modified: 2024-07-02 21:33 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
dmesg (62.48 KB, text/plain)
2019-10-26 15:57 UTC, Ingmar Vanhassel
Details
coredumpctl gdb 841 (12.60 KB, text/plain)
2019-10-26 15:58 UTC, Ingmar Vanhassel
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ingmar Vanhassel 2019-10-26 15:57:59 UTC
Created attachment 123495 [details]
dmesg

SUMMARY
I cannot log in to KDE atm.
dmesg shows a segfault. I'll attach a backtrace & the coredump


STEPS TO REPRODUCE
1. Enter login & password
2. Press enter to login
3. plasmashell segfaults

OBSERVED RESULT
Plasmashell segfaults


EXPECTED RESULT


SOFTWARE/OS VERSIONS
macOS: 
Linux/KDE Plasma: Latest linux kernel 5.3.7
(available in About System)
KDE Plasma Version: 5.17.0
KDE Frameworks Version: 5.63.0
Qt Version: 5.13.1

ADDITIONAL INFORMATION
- X.org server 1.20.5 using modesetting driver
- Intel haswell on-board graphics chip
- Tested with 5.17.1, same error. BT is from 5.17.0
- I noticed this in dmesg: broken atomic modeset userspace detected, disabling atomic
Comment 1 Ingmar Vanhassel 2019-10-26 15:58:47 UTC
Created attachment 123496 [details]
coredumpctl gdb 841

gdb coredump + BT
Comment 2 Ingmar Vanhassel 2019-10-26 15:59:47 UTC
Coredump is available at http://dev.exherbo.org/~ingmar/logs/plasmashell/

At 4,4 MB it's to big to be uploaded here.
Comment 3 Christoph Feck 2019-11-21 15:29:28 UTC
Crash happens in QtGui.

Relevant part of the backtrace:

[Current thread is 1 (Thread 0x7f78501f3d40 (LWP 841))]
(gdb) bt
#0  0x0000000000000000 in ?? ()
#1  0x00007f78543b9470 in QImage::fill (color=..., this=0x55edb44cf970) at ../../include/QtGui/../../src/gui/painting/qrgb.h:91
#2  QImage::fill (this=this@entry=0x55edb44cf970, color=...) at image/qimage.cpp:1796
#3  0x00007f78543fabfe in QRasterPlatformPixmap::fill (this=0x55edb44cf940, color=...) at image/qpixmap_raster.cpp:200
#4  0x00007f78543f3a4f in QPixmap::fill (this=0x55edb44aa760, color=...) at image/qpixmap.cpp:924
#5  0x00007f7855dcef07 in Plasma::FrameSvgPrivate::generateFrameBackground (this=this@entry=0x55edb42c7680, frame=...) at /usr/x86_64-pc-linux-gnu/include/qt5/QtCore/qsharedpointer_impl.h:312
#6  0x00007f7855dcffa6 in Plasma::FrameSvgPrivate::generateBackground (this=0x55edb42c7680, frame=...)
    at /var/tmp/paludis/build/kde-frameworks-plasma-framework-5.63.0/work/plasma-framework-5.63.0/src/plasma/framesvg.cpp:479
#7  0x00007f7855dd0e5c in Plasma::FrameSvgPrivate::alphaMask (this=0x55edb42c7680)
    at /var/tmp/paludis/build/kde-frameworks-plasma-framework-5.63.0/work/plasma-framework-5.63.0/src/plasma/framesvg.cpp:428
#8  0x00007f7855dd10e1 in Plasma::FrameSvg::mask (this=0x55edb4549a50) at /var/tmp/paludis/build/kde-frameworks-plasma-framework-5.63.0/work/plasma-framework-5.63.0/src/plasma/framesvg.cpp:314
#9  0x00007f78562360ee in Plasma::FrameSvgItem::mask (this=<optimized out>)
    at /var/tmp/paludis/build/kde-frameworks-plasma-framework-5.63.0/work/plasma-framework-5.63.0/src/declarativeimports/core/framesvgitem.cpp:461
#10 0x00007f785621a40a in PlasmaQuick::DialogPrivate::updateTheme (this=0x55edb4546b30)
    at /var/tmp/paludis/build/kde-frameworks-plasma-framework-5.63.0/work/plasma-framework-5.63.0/src/plasmaquick/dialog.cpp:245
Comment 4 Nate Graham 2021-02-23 20:26:32 UTC
I notice that this crash is happening in built-from-source code. Is it still happening with a fresh checkout of current git master? We've been porting plasmashell away from QtGui so there's a chance this has already been fixed.

Thanks!
Comment 5 Bug Janitor Service 2021-03-10 04:33:37 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2021-03-25 04:34:03 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!