| Summary: | plasmashell crashes in ImageColors::postProcess() when returning from hibernation or suspend | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-kirigami | Reporter: | Lyon Lemmens <lyon.lemmens> |
| Component: | general | Assignee: | kdelibs bugs <kdelibs-bugs-null> |
| Status: | REPORTED --- | ||
| Severity: | crash | CC: | kde, nate, notmart, qydwhotmail, tobias, yonatan3058 |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 5.102.0 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Manjaro | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
output of kquitapp5 plasmashell && kstart5 plasmashell >& plasmashell.log
KCrash Document |
||
|
Description
Lyon Lemmens
2022-12-22 13:40:17 UTC
Created attachment 154758 [details]
output of kquitapp5 plasmashell && kstart5 plasmashell >& plasmashell.log
@Lyon Lemmens: What Graphic Card do you use? I have an Nvidia Card, using the proprietary driver. Operating System: Manjaro Linux KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel Version: 5.15.85-1-MANJARO (64-bit) Graphics Platform: Wayland Graphics Processor: NVIDIA GeForce GTX 750 Ti I've got an integrated video card on my intel nuc: Lspcinsays: Intel Corporation Alder Lake-P Integrated Graphics Controller (rev 0c) (In reply to Lyon Lemmens from comment #3) > I've got an integrated video card on my intel nuc: > Lspcinsays: Intel Corporation Alder Lake-P Integrated Graphics Controller > (rev 0c) Interesting, so it is not an Nvidia or Wayland issue. We are missing symbols for #4 0x00007f41681a7f03 in () at /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/libKirigamiPlugin.so which is the only part of KDE code. Please install the symbols and reopen if you still have a crash (In reply to David Edmundson from comment #5) > We are missing symbols for #4 0x00007f41681a7f03 in () at > /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/libKirigamiPlugin.so > > which is the only part of KDE code. > > Please install the symbols and reopen if you still have a crash So you want a log with debug symbols of Kirigami2? Or should other packages also have debug symbols activated? And if its not Kirigami2, it is related to Qt? Created attachment 155087 [details]
KCrash Document
One crash that occured.
Thanks. Pasting inline for searchability: [KCrash Handler] #4 0x00007f565a236c28 in QtQml::qmlAttachedPropertiesObject(QObject*, QObject* (*)(QObject*), bool) () at /usr/lib/libQt5Qml.so.5 #5 0x00007f5640ba15af in qmlAttachedPropertiesObject<Kirigami::PlatformTheme>(QObject const*, bool) (obj=<optimized out>, create=<optimized out>) at /usr/include/qt/QtQml/qqml.h:703 #6 0x00007f5640b9b077 in ImageColors::postProcess(ImageData&) const (this=this@entry=0x55e4fe781450, imageData=...) at /usr/src/debug/kirigami2/kirigami2-5.101.0/src/imagecolors.cpp:450 #7 0x00007f5640b9e94d in ImageColors::generatePalette(QImage const&) const (this=0x55e4fe781450, sourceImage=<optimized out>) at /usr/src/debug/kirigami2/kirigami2-5.101.0/src/imagecolors.cpp:436 #8 0x00007f5640ba311b in operator() (__closure=0x55e4fee9f840) at /usr/src/debug/kirigami2/kirigami2-5.101.0/src/imagecolors.cpp:181 #9 QtConcurrent::StoredFunctorCall0<ImageData, ImageColors::update()::<lambda()>::<lambda()> >::runFunctor (this=0x55e4fee9f7a0) at /usr/include/qt/QtConcurrent/qtconcurrentstoredfunctioncall.h:60 #10 QtConcurrent::RunFunctionTask<ImageData>::run() (this=0x55e4fee9f7a0) at /usr/include/qt/QtConcurrent/qtconcurrentrunbase.h:108 #11 0x00007f5658ae8211 in () at /usr/lib/libQt5Core.so.5 #12 0x00007f5658ae42ea in () at /usr/lib/libQt5Core.so.5 #13 0x00007f565849f8fd in () at /usr/lib/libc.so.6 #14 0x00007f5658521a60 in () at /usr/lib/libc.so.6 Can anyone reproduce this on Frameworks 5.101 or later? (In reply to Nate Graham from comment #9) > Can anyone reproduce this on Frameworks 5.101 or later? My version is: KDE Frameworks Version: 5.101.0 *** Bug 463877 has been marked as a duplicate of this bug. *** Unable to find anything wrong from Qt source code. I wonder how attached properties can crash a program. *** Bug 464061 has been marked as a duplicate of this bug. *** (In reply to Nate Graham from comment #9) > Can anyone reproduce this on Frameworks 5.101 or later? I'm also experiencing this on Frameworks 5.101.0, I reported it in #463877 Still an issue with 5.102.0, crash log shows the same, but I can also post a new one if needed. Is there anything else that can be done? git bisect or something? Does someone remember a working version? It should be before 5.98.0. |