Bug 443072 - xembedsniproxy and gmenudbusmenuproxy crash whole wayland session
Summary: xembedsniproxy and gmenudbusmenuproxy crash whole wayland session
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-crash (show other bugs)
Version: 5.22.5
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-09-28 13:22 UTC by elman
Modified: 2021-10-29 04:35 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
dump (9.43 KB, text/plain)
2021-09-28 13:22 UTC, elman
Details
dump2 (9.68 KB, text/plain)
2021-09-28 13:22 UTC, elman
Details

Note You need to log in before you can comment on or make changes to this bug.
Description elman 2021-09-28 13:22:43 UTC
Created attachment 141989 [details]
dump

SUMMARY
I was working in Wayland session in PhpStorm (installed via snap) when whole Wayland session crashed and then immediately restarted. However all applications were force closed along with my work. Some applications could not be started again - like Double Commander with error

```
qt.qpa.xcb: could not connect to display :1
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.

fish: Job 1, 'doublecmd' terminated by signal SIGABRT (Abort)
```

I'm attaching dumps.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2 (extra/qt5-base 5.15.2+kde+r227-1)
Comment 1 elman 2021-09-28 13:22:57 UTC
Created attachment 141990 [details]
dump2
Comment 2 Nate Graham 2021-09-28 20:23:08 UTC
This means that KWin crashed. Can you please attach a backtrace of the kwin crash? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl
Comment 3 elman 2021-09-29 08:11:06 UTC
There is no kwin crash around that time, when looking via coredumpctl.
Comment 4 Bug Janitor Service 2021-10-14 04:35:23 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
mark the bug 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 5 Bug Janitor Service 2021-10-29 04:35:14 UTC
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!