Bug 357403

Summary:	Plasma crashes when quickly switching desktops after a window on another desktop is focused
Product:	[Plasma] plasmashell	Reporter:	Mircea Kitsune <sonichedgehog_hyperblast00>
Component:	general	Assignee:	David Edmundson <kde>
Status:	RESOLVED FIXED
Severity:	crash	CC:	bshah, notmart, plasma-bugs-null, sonichedgehog_hyperblast00
Priority:	NOR
Version First Reported In:	5.5.1
Target Milestone:	1.0
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Mircea Kitsune 2016-01-01 21:10:08 UTC

Plasma crashes when a program on one desktop focuses a window on another desktop, then the user quickly switches back to the initial desktop. You must wait about 10 seconds in order to avoid the crash.

Reproducible: Always

Steps to Reproduce:
1. Make sure the system has at least two desktops. Put your default web browser on one (I use Firefox) and your file manager on the other (I use Dolphin).

2. Create a shortcut file to a website or find one on your drive, then click it. You will automatically be taken to the other desktop as the web browser is focused.

3. Quickly use the pager to scroll back to the initial desktop, on which you have the file manager open. Ideally click on the background or various Plasma menus afterward.

Actual Results:  
plasmashell crashes and the KDE crash reporter pops up.


Several details which might be related to the problem: The crash occurs while I still have the bouncing icon on the cursor, as well as the task manager entry of the web browser showing the spinning cursor. I use the icon-only task manger on the default panel. I use the following KWin and Plasma themes:

http://opendesktop.org/content/show.php?content=168737

http://opendesktop.org/content/show.php?content=168760

Comment 1 Marco Martin 2016-02-11 09:41:24 UTC

to be useful it needs a backtrace: please make sure you have debug packages installed for plasma and Qt

Comment 2 Mircea Kitsune 2016-02-11 11:32:22 UTC

(In reply to Marco Martin from comment #1)

Sounds like I need to mess with my system and packages... since this is my primary desktop, I'd really rather not do that unless I'm extra sure. Is the issue not possible to reproduce locally using the instructions I suggested, on a machine prepared for such tests? I might look into it if not...

Comment 3 Mircea Kitsune 2017-02-01 19:47:50 UTC

Haven't experienced this crash for some time now. I will therefore close this, and reopen or make a new report if it happens again.