Bug 478233

Summary: Crash after putting widgets on a panel
Product: [Plasma] plasmashell Reporter: rafal.dardzinski
Component: generalAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: kde, nate
Priority: NOR Keywords: drkonqi
Version: 5.27.5   
Target Milestone: 1.0   
Platform: Debian stable   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: New crash information added by DrKonqi

Description rafal.dardzinski 2023-12-07 22:26:16 UTC
Application: plasmashell (5.27.5)

Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.1.0-13-amd64 x86_64
Windowing System: X11
Distribution: Debian GNU/Linux 12 (bookworm)
DrKonqi: 5.27.5 [CoredumpBackend]

-- Information about the crash:
I have two monitors in the following configuration: 1st one is  2560x1440 with 90deg clockwise orientation. Second is 3840x2160, no rotation. Crash occured when I was trying to add widget to a full width, non floating panel attached to the bottom of the screen.

The crash can be reproduced sometimes.

-- Backtrace (Reduced):
#5  0x00007f958e277c86 in QtQml::qmlExecuteDeferred(QObject*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
#6  0x00007f958e749059 in QQuickTransition::prepare(QList<QQuickStateAction>&, QList<QQmlProperty>&, QQuickTransitionManager*, QObject*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#7  0x00007f958e73e997 in QQuickTransitionManager::transition(QList<QQuickStateAction> const&, QQuickTransition*, QObject*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#8  0x00007f958cadd50d in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x00007f958d962fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5


Reported using DrKonqi
Comment 1 rafal.dardzinski 2023-12-07 22:26:16 UTC
Created attachment 163992 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Nate Graham 2023-12-08 16:25:10 UTC

*** This bug has been marked as a duplicate of bug 468180 ***