Bug 405351 - Plasma crashes with frameworks-plasma 5.56.0
Summary: Plasma crashes with frameworks-plasma 5.56.0
Status: RESOLVED FIXED
Alias: None
Product: libplasma
Classification: Frameworks and Libraries
Component: libplasma (show other bugs)
Version: 5.56.0
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Laurent Montel
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-11 14:05 UTC by Yannick
Modified: 2019-03-13 10:41 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.57.0


Attachments
crash report (10.52 KB, text/plain)
2019-03-11 14:05 UTC, Yannick
Details
backtrace (11.56 KB, text/plain)
2019-03-11 16:41 UTC, Yannick
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Yannick 2019-03-11 14:05:24 UTC
Created attachment 118717 [details]
crash report

With plasma-frameworks 5.56.0, both Plasma X11 and Wayland crashes at login.
On the X11 session, the screen turns black and the taskbar disappears after a while, but I could export the crash log in time.

STEPS TO REPRODUCE
Start a Plasma session (X11 or Wayland).

OBSERVED RESULT
The screen turns black and the taskbar disappears.

EXPECTED RESULT
The session starts correctly.

SOFTWARE/OS VERSIONS
Arch Linux 
KDE Plasma : 5.15.2
KDE Frameworks : 5.56.0
Qt : 5.12.1
Kernel : 5.0.0-arch1-1-ARCH
OS type : 64-bit
Processors : 4 × Intel® Core™ i5-3570 CPU @ 3.40GHz
RAM : 15,6 Gio


ADDITIONAL INFORMATION
I use an AMD GPU (RX560).
The session starts normally again when downgrading to frameworks-plasma 5.55.0.
Comment 1 Kai Uwe Broulik 2019-03-11 14:25:36 UTC
Can you please install debug symbols for plasma-framework?

Thread 1 (Thread 0x7f4eb8dac6c0 (LWP 705)):
[KCrash Handler]
#6  0x00007f4ea05758b4 in  () at /usr/lib/qt/qml/org/kde/plasma/core/libcorebindingsplugin.so
#7  0x00007f4ebe28ecff in QAbstractProxyModel::setSourceModel(QAbstractItemModel*) () at /usr/lib/libQt5Core.so.5
#8  0x00007f4ebe2a0ab1 in QSortFilterProxyModel::setSourceModel(QAbstractItemModel*) () at /usr/lib/libQt5Core.so.5
#9  0x00007f4ea057644a in  () at /usr/lib/qt/qml/org/kde/plasma/core/libcorebindingsplugin.so
#10 0x00007f4ea059d256 in  () at /usr/lib/qt/qml/org/kde/plasma/core/libcorebindingsplugin.so
#11 0x00007f4ebfade684 in  () at /usr/lib/libQt5Qml.so.5
#12 0x00007f4ebfadfbe8 in  () at /usr/lib/libQt5Qml.so.5
#13 0x00007f4ebfadc3f3 in QQmlBinding::update(QFlags<QQmlPropertyData::WriteFlag>) () at /usr/lib/libQt5Qml.so.5
#14 0x00007f4ebfae9a44 in QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () at /usr/lib/libQt5Qml.so.5
#15 0x00007f4ebfa7406b in  () at /usr/lib/libQt5Qml.so.5
#16 0x00007f4ebfa74657 in QQmlEnginePrivate::incubate(QQmlIncubator&, QQmlContextData*) () at /usr/lib/libQt5Qml.so.5
#17 0x00007f4ebfa70f77 in QQmlComponent::create(QQmlIncubator&, QQmlContext*, QQmlContext*) () at /usr/lib/libQt5Qml.so.5
#18 0x00007f4ec0158702 in KDeclarative::QmlObject::createObjectFromComponent(QQmlComponent*, QQmlContext*, QHash<QString, QVariant> const&) () at /usr/lib/libKF5Declarative.so.5
Comment 2 Yannick 2019-03-11 15:35:28 UTC
I compiled plasma-framework with debug symbols, but now after 5 attempts I'm unable to open the crash handler window again :(
Comment 3 Antonio Rojas 2019-03-11 16:15:37 UTC
(In reply to Yannick from comment #2)
> I compiled plasma-framework with debug symbols, but now after 5 attempts I'm
> unable to open the crash handler window again :(

Does that mean it doesn't crash, or still crashes but you don't get a drkonqi window
Comment 4 Yannick 2019-03-11 16:19:35 UTC
(In reply to Antonio Rojas from comment #3)
> (In reply to Yannick from comment #2)
> > I compiled plasma-framework with debug symbols, but now after 5 attempts I'm
> > unable to open the crash handler window again :(
> 
> Does that mean it doesn't crash, or still crashes but you don't get a
> drkonqi window

It still crashes, the drkonqi icon appears on the systray but even when I click on it, it won't open the window. Then the taskbar dies anyway, so I can't click on it again.
Comment 5 Antonio Rojas 2019-03-11 16:20:28 UTC
(In reply to Yannick from comment #4)
> (In reply to Antonio Rojas from comment #3)
> > (In reply to Yannick from comment #2)
> > > I compiled plasma-framework with debug symbols, but now after 5 attempts I'm
> > > unable to open the crash handler window again :(
> > 
> > Does that mean it doesn't crash, or still crashes but you don't get a
> > drkonqi window
> 
> It still crashes, the drkonqi icon appears on the systray but even when I
> click on it, it won't open the window. Then the taskbar dies anyway, so I
> can't click on it again.

Then you can still get the backtrace from coredumpctl
Comment 6 Yannick 2019-03-11 16:41:06 UTC
Created attachment 118719 [details]
backtrace

Here is the backtrace that I got with coredumpctl.
Should I also enable debug symbols for the plasma-workspace package?
Comment 7 Antonio Rojas 2019-03-11 16:58:51 UTC
The backtrace points to 9fc663d9f0edf41acd098b7c6c7b090d2c7b5aea. I made a package with that commit reverted, can you please test?

http://pkgbuild.com/~arojas/plasma-framework-5.56.0-2-x86_64.pkg.tar.xz

Signature:
http://pkgbuild.com/~arojas/plasma-framework-5.56.0-2-x86_64.pkg.tar.xz.sig
Comment 8 Yannick 2019-03-11 17:05:49 UTC
It doesn't crash anymore with your package.
Thanks!
Comment 9 David Faure 2019-03-11 21:09:21 UTC
Looks like a missing null check before using sourceModel(), in roleNames().