Bug 384490 - [Wayland] Plasma crashes when clicking Kmail launcher if already open
Summary: [Wayland] Plasma crashes when clicking Kmail launcher if already open
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: Task Manager and Icons-Only Task Manager (show other bugs)
Version: 5.10.5
Platform: Arch Linux Linux
: NOR crash
Target Milestone: 1.0
Assignee: Eike Hein
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2017-09-08 12:31 UTC by tromzy
Modified: 2018-10-28 03:32 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description tromzy 2017-09-08 12:31:45 UTC
On Wayland, I have a Kmail launcher icon in my Plasma panel. If I click it once, it opens Kmail fine. If I click the "Close" button in Kmail titlebar, Kmail gets minimized in systray (that is the expected behavior). On X11 I can click the kmail icon in the Plasma panel again to restore the Kmail main window. But On Wayland, doing so results in Plasma crashing and kicking me back to SDDM.

I use Intel Modesettings driver, Plasma 5.10 with KDE Applications 17.08.1 and Frameworks 5.37.
Comment 1 tromzy 2017-09-08 17:49:41 UTC
The crash also happens if I click "Kmail" in the application launcher, not just with the pinned launcher in panel.
Comment 2 tromzy 2017-09-15 11:21:54 UTC
Also happens in Plasma 5.11 beta.
Comment 3 Christoph Feck 2017-09-27 20:17:45 UTC
If the complete session is terminated, this is probably a Wayland bug.

Either way, we need the backtrace of the crash, either of the plasmashell process, or from the Wayland server.
Comment 4 tromzy 2017-09-28 07:39:39 UTC
The thing is, I cannot provide a backtrace because I use Arch Linux...
Comment 5 Antonio Rojas 2017-09-28 07:58:51 UTC
(In reply to tromzy from comment #4)
> The thing is, I cannot provide a backtrace because I use Arch Linux...

https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces
Comment 6 Christoph Feck 2017-10-12 20:14:08 UTC
Did comment #5 help? In either case, even an incomplete backtrace could already give a hint.
Comment 7 Andrew Crouthamel 2018-09-28 02:42:07 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Andrew Crouthamel 2018-10-28 03:32:21 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!