Created attachment 1937928 [details] Journal showing plasmashell crashes with The Wayland connection experienced a fatal error: Bad file descriptor Description of problem: I was using Plasma 5.26.5 on Wayland with a Fedora Rawhide KDE Plasma live image Fedora-KDE-Live-x86_64-Rawhide-20230111.n.0.iso in a QEMU/KVM VM in GNOME Boxes in a Fedora 37 KDE Plasma installation. I started Konsole from the menu. I ran sudo dnf upgrade in Konsole. I hovered the cursor over the icons in the task manager. plasmashell crashed when hovering over task manager icons plasmashell might've crashed when the Konsole popup was shown. The task manager disappeared and then reappeared automatically several seconds later. The journal at the time of the crash showed plasmashell crashed with the error The Wayland connection experienced a fatal error: Bad file descriptor and lines like plasmashell[1531]: kpipewire_logging: Failed to query DMA-BUF formats. Jan 13 17:50:14 plasmashell[1531]: trying to show an empty dialog Jan 13 17:50:16 plasmashell[1531]: kpipewire_logging: Failed to query DMA-BUF formats. Jan 13 17:50:17 plasmashell[1531]: kpipewire_logging: Failed to query DMA-BUF formats. Jan 13 17:50:25 plasmashell[1531]: kpipewire_logging: Failed to query DMA-BUF formats. Jan 13 17:50:26 plasmashell[1531]: kpipewire_logging: Failed to query DMA-BUF formats. Jan 13 17:50:27 plasmashell[1531]: KCrash: Application 'plasmashell' crashing... Jan 13 17:50:27 plasmashell[1531]: The Wayland connection experienced a fatal error: Bad file descriptor Jan 13 17:50:28 systemd[1344]: plasma-plasmashell.service: Main process exited, code=exited, status=1/FAILURE Jan 13 17:50:28 systemd[1344]: plasma-plasmashell.service: Failed with result 'exit-code'. Jan 13 17:50:28 systemd[1344]: plasma-plasmashell.service: Consumed 43.195s CPU time. Jan 13 17:50:28 systemd[1344]: plasma-plasmashell.service: Scheduled restart job, restart counter is at 1. Jan 13 17:50:28 systemd[1344]: Stopped plasma-plasmashell.service - KDE Plasma Workspace. Jan 13 17:50:28 systemd[1344]: plasma-plasmashell.service: Consumed 43.195s CPU time. Jan 13 17:50:28 systemd[1344]: Starting plasma-plasmashell.service - KDE Plasma Workspace... Jan 13 17:50:29 plasmashell[2722]: libEGL warning: egl: failed to create dri2 screen Jan 13 17:50:29 systemd[1344]: Started plasma-plasmashell.service - KDE Plasma Workspace. drkonqi didn't appear. I'll try to reproduce the problem to get a trace with gdb or valgrind. I'm attaching the journal which shows three plasmashell crashes with The Wayland connection experienced a fatal error: Bad file descriptor in the same Plasma 5.26.5 on Wayland session. The first plasmashell crash was the one I described. The second plasmashell crash happened when I clicked on the Status and Notifications applet button in the system tray at the bottom right of the screen. The third plasmashell crash happened when I was using Firefox. The bottom panel disappeared and reappeared automatically each time. Version-Release number of selected component (if applicable): plasma-workspace-5.26.5-1.fc38 kf5-plasma-5.101.0-1.fc38 qt5-qtbase-5.15.8-2.fc38 konsole5-22.12.1-1.fc38 How reproducible: The crash happened three times in one session. Steps to Reproduce: 1. Boot a Fedora 37 KDE Plasma installation 2. Log in to Plasma on Wayland 3. Download Fedora Rawhide KDE Plasma live image Fedora-KDE-Live-x86_64-Rawhide-20230111.n.0.iso https://koji.fedoraproject.org/koji/buildinfo?buildID=2109618 4. Install GNOME Boxes if it isn't already with sudo dnf install gnome-boxes 5. Start GNOME Boxes 6. Boot the Fedora Rawhide KDE Plasma live image Fedora-KDE-Live-x86_64-Rawhide-20230111.n.0.iso in a QEMU/KVM VM in GNOME Boxes with 3 GB RAM using the llvmpipe mesa driver and virtio_gpu kernel driver 7. start Konsole from the Application launcher menu. 8. hover the cursor back and forth over the icons including Konsole in the task manager and system tray buttons and sometimes clicking them until the crash happens Actual results: plasmashell crashed when hovering over task manager icons with the error The Wayland connection experienced a fatal error: Bad file descriptor Expected results: plasmashell wouldn't crash Additional info: I reported this problem at https://bugs.kde.org/show_bug.cgi?id=464258 The way in which the crash happened was similar those crashes reported at https://bugzilla.redhat.com/show_bug.cgi?id=2140010 and https://bugs.kde.org/show_bug.cgi?id=447717 However, the errors in the journal were different.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 38 development cycle. Changing version to 38.
This message is a reminder that Fedora Linux 38 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 38 on 2024-05-21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '38'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 38 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.