FS#73875 - firefox plasmashell on xorg nvidia proprietary crashed as volume changing too fast

Attached to Project: Arch Linux
Opened by Vasja (pridoorok) - Saturday, 19 February 2022, 04:40 GMT
Last edited by Andreas Radke (AndyRTR) - Saturday, 19 February 2022, 16:22 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Andreas Radke (AndyRTR)
Jan Alexander Steffens (heftig)
Laurent Carlier (lordheavy)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
i've assigned changing volume +- on f7 f8 keys, when firefox playing media and im trying to change volume too fast(i mean by holding key) plasmashell is crashed to sddm login screen, im using plasmashell on xorg with nvidia proprietary drivers. chromium doesn't have such behavior. i've also trying to use pipewire-pulse instead of pulseaudio - same no difference

Additional info:
kwin - 5.24.1-1
xorg - 21.1.3-2
plasma-desktop - 5.24.1-1
firefox - 97.0.1
pulseaudio - 15.0-1
pipewire - 1:0.3.46-1
nvidia-lts - 1:510.54-2
linux-lts - 5.15.24-1



crash dumps attached

Steps to reproduce:
open any media using firefox
try to change volume too fast by holding on the key
session crash to the login screen
   kwin-x11Crash (32.3 KiB)
   xorgCrash (16.3 KiB)
   plasmashellCrash (52.1 KiB)
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Saturday, 19 February 2022, 16:22 GMT
Reason for closing:  Fixed
Comment by Vasja (pridoorok) - Saturday, 19 February 2022, 05:39 GMT
dmn it's actually happens no matter where no firefox to blame here, it crashed once then it's fine till next reboot
Comment by agapito fernandez (agapito) - Saturday, 19 February 2022, 08:04 GMT
Probably this: https://bbs.archlinux.org/viewtopic.php?id=271450
Comment by agapito fernandez (agapito) - Saturday, 19 February 2022, 08:57 GMT
Comment by Antonio Rojas (arojas) - Saturday, 19 February 2022, 11:02 GMT
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1261
Comment by Andreas Radke (AndyRTR) - Saturday, 19 February 2022, 11:33 GMT
Please check if 21.1.3-5 solves this.
Comment by Frederik “Freso” S. Olesen (Freso) - Saturday, 19 February 2022, 13:37 GMT
FWIW, 21.1.3-3 broke X for me entirely, with 21.1.3-5 it works again.

Loading...