Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 588770

Summary: Plasma: crashes if text file is opened in a different screen
Product: Gentoo Linux Reporter: Plüss Roland <roland>
Component: Current packagesAssignee: Gentoo KDE team <kde>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: Crash Report

Description Plüss Roland 2016-07-13 17:35:02 UTC
Created attachment 440604 [details]
Crash Report

Situation is like this: There is a Kate instance running on one screen (let's say screen 1). Now on another screen (let's say screen 2) you click on a text file that KDE opens in Kate. KDE window manager switches to Kate (screen 1) to open the file. After switching Plasma crashes with the bug report below and has to be restarted.

I can not post this on KDE bug-list due to technical issues on their end.
Comment 1 Michael Palimaka (kensington) gentoo-dev 2016-07-13 17:40:55 UTC
Which Plasma version?
Comment 2 Plüss Roland 2016-07-13 19:09:48 UTC
(In reply to Michael Palimaka (kensington) from comment #1)
> Which Plasma version?

kde-plasma/plasma-meta-5.5.5:5::gentoo  USE="bluetooth display-manager gtk pam sddm wallpapers -mediacenter -networkmanager -pulseaudio -sdk"
Comment 3 Michael Palimaka (kensington) gentoo-dev 2016-08-05 17:46:42 UTC
There's many fixes for multiple screens with Plasma 5.6.5 which is now stable, does the issue persist with that?
Comment 4 Plüss Roland 2016-08-08 23:29:23 UTC
(In reply to Michael Palimaka (kensington) from comment #3)
> There's many fixes for multiple screens with Plasma 5.6.5 which is now
> stable, does the issue persist with that?

I see no difference in 5.6.5 . In contrary. Now the entire plasma desktop sometimes randomly crashes while doing nothing restarting itself right away. Stable looks different.
Comment 5 Johannes Huber (RETIRED) gentoo-dev 2016-11-02 10:27:23 UTC

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