Bug 428360

Summary:	plasmashell crashes if AV-Receiver is connected via HDMI
Product:	[Plasma] plasmashell	Reporter:	Jens Ramke <jens.ramke>
Component:	general	Assignee:	David Edmundson <kde>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	jens.ramke, plasma-bugs
Priority:	NOR	Keywords:	drkonqi
Version:	5.20.2
Target Milestone:	1.0
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	New crash information added by DrKonqi

Description Jens Ramke 2020-10-27 20:33:30 UTC

Application: plasmashell (5.20.1)

Qt Version: 5.15.1
Frameworks Version: 5.75.0
Operating System: Linux 5.8.16-xanmod1-1 x86_64
Windowing system: X11
Distribution: "Arch Linux"

-- Information about the crash:
- What I was doing when the application crashed:
Logged in via SDDM.
Plasmashell crashes after displaying desktop widgets.
Sometimes it restarts and crashes again. It never starts without crashing.

- Custom settings of the application:
Xorg session.
Connected AV-Receiver (Marantz SR7007) via HDMI and added to screen0.
Crash happens whether receiver is switched on or in standby mode.

Workaround:
Disconnect receiver before starting plasmashell, then reconnect HDMI.

Non-viable workarounds:
Crash does not happen if the receiver is added to a second xorg screen (i.e. screen1). However, HDMI 5.1 and 7.1 audio modes are not available in this configuration, so it is not an alternative.
Receiver "display" needs to be active, since HDMI audio is not working otherwise.

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault

[KCrash Handler]
#4  0x00007f70b8300000 in  ()
#5  0x00007f7158027020 in  () at /usr/lib/qt/qml/org/kde/plasma/calendar/libcalendarplugin.so
#6  0x00007f7187fa87e2 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5
#7  0x00007f7188c14752 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5
#8  0x00007f7187f7bcda in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5
#9  0x00007f7187f7e7d3 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5
#10 0x00007f7187fd5304 in  () at /usr/lib/libQt5Core.so.5
#11 0x00007f71863f3914 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0
#12 0x00007f71864477d1 in  () at /usr/lib/libglib-2.0.so.0
#13 0x00007f71863f2121 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#14 0x00007f7187fd4941 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#15 0x00007f7187f7a65c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#16 0x00007f7187f82af4 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5
#17 0x000055e69ab15f99 in  ()
#18 0x00007f7187948152 in __libc_start_main () at /usr/lib/libc.so.6
#19 0x000055e69ab161de in  ()
[Inferior 1 (process 2087) detached]

Possible duplicates by query: bug 428241, bug 428082, bug 428065, bug 428027, bug 427922.

Reported using DrKonqi

Comment 1 Jens Ramke 2020-10-27 20:56:12 UTC

(In reply to Jens Ramke from comment #0)

Comment 2 David Edmundson 2020-10-27 22:15:58 UTC

>#5  0x00007f7158027020 in  () at /usr/lib/qt/qml/org/kde/plasma/calendar/libcalendarplugin.so

It crashes in the calendar? That seems very unrelated to anything screen related.

Can you install debug symbols for this.

Comment 3 Jens Ramke 2020-10-28 10:52:20 UTC

Created attachment 132831 [details]
New crash information added by DrKonqi

plasmashell (5.20.2) using Qt 5.15.1

I installed plasma-workspace, plasma-framework and plasma-desktop with debug symbols.

-- Backtrace (Reduced):
#4  0x00007f303269b2f2 in DaysModel::update() (this=0x55df5acb6090) at /usr/src/debug/plasma-framework-5.75.0/src/declarativeimports/calendar/daysmodel.cpp:90
#5  DaysModel::update() (this=0x55df5acb6090) at /usr/src/debug/plasma-framework-5.75.0/src/declarativeimports/calendar/daysmodel.cpp:77
#6  0x00007f305c6fb7e2 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5
#7  0x00007f305d367752 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5
#8  0x00007f305c6cecda in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5

Comment 4 Jens Ramke 2020-10-28 11:11:12 UTC

I have two digital clock widgets active on two different monitors, both with all available calender modules active.
The receiver display newly added is the third display.

I decided to try to remove both widgets.
Now, upon adding them again, the issue disappeared.

Comment 5 Christoph Feck 2020-11-09 23:25:03 UTC

Thanks for the update; changing status. If you see this issue again, please reopen the ticket.