Bug 2232207 - plasmashell sometimes crashes when clicking on Notifications
Summary: plasmashell sometimes crashes when clicking on Notifications
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: plasma-desktop
Version: 39
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: KDE SIG
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-15 18:23 UTC by Adam Williamson
Modified: 2023-11-14 23:46 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
KDE Software Compilation 468180 0 VHI ASSIGNED Plasmashell crashed in QQuickTransition::prepare() after closing a notification 2023-09-13 06:53:36 UTC

Description Adam Williamson 2023-08-15 18:23:16 UTC
openQA is showing that plasmashell sometimes crashes when we open the "Status and Notifications" pane and click "Notifications", e.g. here:

https://openqa.fedoraproject.org/tests/2073354

if you watch the video - https://openqa.fedoraproject.org/tests/2073354/video?filename=video.ogv&t=51.08,51.12 carefully, around the 11:30:36 mark, you can see the test clicks Notifications, and the entire desktop briefly goes black while the shell reloads. In the system logs we see this:

Aug 15 08:30:34 localhost-live plasmashell[1795]: trying to show an empty dialog
Aug 15 08:30:34 localhost-live plasmashell[1795]: trying to show an empty dialog
Aug 15 08:30:34 localhost-live plasmashell[1795]: trying to show an empty dialog
Aug 15 08:30:35 localhost-live plasmashell[1795]: Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations.
Aug 15 08:30:35 localhost-live plasmashell[1795]: Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations.
Aug 15 08:30:35 localhost-live plasmashell[1795]: Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations.
Aug 15 08:30:35 localhost-live plasmashell[1795]: Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations.
Aug 15 08:30:37 localhost-live plasmashell[1795]: KCrash: Application 'plasmashell' crashing...
Aug 15 08:30:37 localhost-live plasmashell[1795]: The Wayland connection experienced a fatal error: Bad file descriptor
Aug 15 08:30:37 localhost-live systemd[1448]: plasma-plasmashell.service: Main process exited, code=exited, status=1/FAILURE
Aug 15 08:30:37 localhost-live systemd[1448]: plasma-plasmashell.service: Failed with result 'exit-code'.
Aug 15 08:30:37 localhost-live systemd[1448]: plasma-plasmashell.service: Consumed 15.842s CPU time.
Aug 15 08:30:37 localhost-live systemd[1448]: plasma-plasmashell.service: Scheduled restart job, restart counter is at 1.
Aug 15 08:30:37 localhost-live systemd[1448]: Starting plasma-plasmashell.service - KDE Plasma Workspace...

(the timestamp difference is just a timezone thing). Not sure how to get better details on the crash, please advise.

Reproducible: Sometimes

Steps to Reproduce:
1. Boot a Fedora 39 or Rawhide KDE live image
2. Wait ten minutes (probably not necessary, but openQA does this)
3. Click the up-arrow thingy in the bottom right pane to open the "Status and Notifications" pane
4. Click "Notifications"
Actual Results:  
Desktop briefly goes black then reloads, you never actually get where clicking "Notifications" should have taken you

Expected Results:  
Clicking "Notifications" should work as expected

Comment 1 Fedora Release Engineering 2023-08-16 08:08:14 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.

Comment 2 Adam Williamson 2023-09-13 06:22:08 UTC
Ping? This is still happening, and it's quite a bad bug.

Comment 3 Adam Williamson 2023-09-13 06:23:05 UTC
Note: I think this only happens when booted live, not after install.

Comment 4 Adam Williamson 2023-11-14 23:46:32 UTC
hmm, well, https://openqa.fedoraproject.org/tests/2260970 seems like it happening post-install...


Note You need to log in before you can comment on or make changes to this bug.