https://bugs.kde.org/show_bug.cgi?id=471248

            Bug ID: 471248
           Summary: plasmashell on Wayland crashed occasionally when
                    playing Instagram story videos in Firefox
    Classification: Plasma
           Product: plasmashell
           Version: 5.27.5
          Platform: Fedora RPMs
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: generic-crash
          Assignee: plasma-b...@kde.org
          Reporter: matt.fagn...@bell.net
  Target Milestone: 1.0

SUMMARY

plasmashell crashed occasionally when playing Instagram story videos in Firefox
Nightly on Wayland 116.0a1 and earlier in Plasma 5.27.5 on Wayland in Fedora
38. plasmashell crashed several times over the last few weeks when Firefox was
finished showing one Instagram story and then started playing the next story
which was a video. The panel disappeared from the bottom of the screen, and
then it reappeared automatically. The last crash was with Firefox Nightly
116.0a1 (2023-06-19) on Wayland in Plasma 5.27.5. KCrash appeared to try to
start drkonqi when the crashes happened according to the journal, but drkonqi
never appeared.

Jun 19 18:16:05 plasmashell[1456]:
file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/items/PlasmoidItem.qml:125:
TypeError: Cannot read property 'compactRepresentationItem' of null
Jun 19 18:16:05 plasmashell[1456]: KCrash: Application 'plasmashell'
crashing...
Jun 19 18:16:05 plasmashell[1456]: KCrash: Attempting to start
/usr/libexec/drkonqi
Jun 19 18:16:05 drkonqi[4122]: kf5idletime_wayland: This plugin does not
support polling idle time
Jun 19 18:16:06 systemd[1251]: plasma-plasmashell.service: Main process exited,
code=exited, status=253/n/a
Jun 19 18:16:06 systemd[1251]: plasma-plasmashell.service: Failed with result
'exit-code'.
Jun 19 18:16:06 systemd[1251]: plasma-plasmashell.service: Consumed 16.190s CPU
time.
Jun 19 18:16:07 systemd[1251]: plasma-plasmashell.service: Scheduled restart
job, restart counter is at 1.
Jun 19 18:16:07 systemd[1251]: Stopped plasma-plasmashell.service - KDE Plasma
Workspace.
Jun 19 18:16:07 systemd[1251]: plasma-plasmashell.service: Consumed 16.190s CPU
time.
Jun 19 18:16:07 systemd[1251]: Starting plasma-plasmashell.service - KDE Plasma
Workspace...
Jun 19 18:16:07 systemd[1251]: Started plasma-plasmashell.service - KDE Plasma
Workspace.
Jun 19 18:16:07 plasmashell[4140]: kf.plasma.quick: Applet preload policy set
to 1

The error messages of the crashes weren't really informative, but they were the
same each time. Such crashes probably happened about 1% or less of the
Instagram story videos I've played in this way in the last few weeks. 

These crashes happened with mesa-va-drivers-23.1.2-1.fc38.x86_64 installed
which doesn't have h264 video hardware decoding support and with
mesa-va-drivers-freeworld from RPM Fusion which has h264 hardware decoding
support for AMD GPUs. When mesa-va-drivers-freeworld was installed, the journal
showed the radeonsi video decoding library being loaded right before the
crashes.

STEPS TO REPRODUCE
1. Boot a Fedora 38 KDE Plasma installation updated to 2023-6-19 with
updates-testing repo enabled
2. Log in to Plasma 5.27.5 on Wayland
3. Download Firefox Nightly from
https://www.mozilla.org/en-US/firefox/channel/desktop/#nightly
4. Decompress the FIrefox Nightly download
5. Run Firefox Nightly on Wayland
6. Log in to your Instagram account
7. Play stories from the top of the main feed of your Instagram account page
until the crash happens. Playing hundreds of videos in stories might be needed
to reproduce the crash.

OBSERVED RESULT
plasmashell on Wayland crashed occasionally when playing Instagram story videos
in Firefox

EXPECTED RESULT
plasmashell wouldn't have crashed.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 38
(available in About System)
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.107.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION
I could try to attach gdb to plasmashell and then try to reproduce the crash. I
haven't tried that yet.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to