Bug 431786

Summary: When Firefox tab is dragged to panel, kwin crashes
Product: [Plasma] plasmashell Reporter: Grayson Penland <gpenland06>
Component: generic-crashAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: nate, ngompa13
Priority: NOR    
Version: 5.20.5   
Target Milestone: 1.0   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:

Description Grayson Penland 2021-01-18 15:57:28 UTC
SUMMARY
When I click and drag a firefox tab down to the plasma panel, kwin appears to crash, but will recover 90% of the time and keep going

STEPS TO REPRODUCE
1. In KDE plasma wayland, open a firefox windows
2. Click and drag any firefox tab, and release it over the panel

OBSERVED RESULT
The background goes black and the panel disappears, but any open windows remain, and the cursor is repsonsive. After a second the background usually comes back along with the panel.


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Grayson Penland 2021-01-18 16:01:50 UTC
(In reply to Grayson Penland from comment #0)
> SUMMARY
> When I click and drag a firefox tab down to the plasma panel, kwin appears
> to crash, but will recover 90% of the time and keep going
> 
> STEPS TO REPRODUCE
> 1. In KDE plasma wayland, open a firefox windows
> 2. Click and drag any firefox tab, and release it over the panel
> 
> OBSERVED RESULT
> The background goes black and the panel disappears, but any open windows
> remain, and the cursor is repsonsive. After a second the background usually
> comes back along with the panel.
> 
> 

 
 
 SOFTWARE/OS VERSIONS
 Linux/KDE Plasma: 
 (available in About System)
 KDE Plasma Version: 5.20.5
 KDE Frameworks Version: 5.78.0
 Qt Version: 5.15.2
 
Fedora 33
Comment 2 Vlad Zahorodnii 2021-01-21 09:09:53 UTC
From the given description, it sounds like plasmashell crashed.
Comment 3 Nate Graham 2021-01-26 19:19:23 UTC

*** This bug has been marked as a duplicate of bug 398440 ***