| Summary: | [Wayland] Systemsettings crashes with "The Wayland connection broke. Did the Wayland compositor die?" | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | Tony <jodr666> |
| Component: | generic-crash | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | jodr666, kde, matt.fagnani, nate |
| Priority: | NOR | Keywords: | drkonqi, wayland |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
terminal log for systemsettings5
New crash information added by DrKonqi Systemsettings5 terminal log New crash information added by DrKonqi |
||
|
Description
Tony
2020-06-12 21:49:49 UTC
We were killed by kwin for making a protocol violation. Can you run from a terminal and reproduce and paste the contents Created attachment 129656 [details]
terminal log for systemsettings5
Sadly i can't reproduced the crash anymore, may be it was related to some other issue i had over the past weekend, i end up deleting ~/.cache and those as well as this one don't happen anymore.
The attatchement it may not be of any help now although I do find wierd this line keeps repeating in it :
dri_create_context: requested glthread but driver is missing backgroundCallable V2 extension
Ok, well please do keep us informed if it comes up again. Typically a protocol error would be some code in Qt, systemsettings won't be doing anything natively itself. So it might get fixed with different Qt releases Created attachment 129725 [details]
New crash information added by DrKonqi
systemsettings5 (5.19.80) using Qt 5.15.0
- What I was doing when the application crashed:
Mostly the same steps, switched from x session to wayland.
The main difference this time being :
I updated the system from a different tty.
After the installation finished, ran systemctl daemon-reload && systemctl daemon-reexec.
Deleted ~/.cache
Switch bacl to sdd and log in.
-- Backtrace (Reduced):
#4 0x00007f4360a244b1 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#5 0x00007f4360a0d539 in __GI_abort () at abort.c:79
#6 0x00007f4360e26c27 in qt_message_fatal (message=<synthetic pointer>..., context=...) at global/qlogging.cpp:1914
#7 0x00007f4360e26c27 in QMessageLogger::fatal(char const*, ...) const (this=this@entry=0x7fff64646fa0, msg=msg@entry=0x7f435c2150b8 "The Wayland connection broke. Did the Wayland compositor die?") at global/qlogging.cpp:893
#8 0x00007f435c15bf25 in QtWaylandClient::QWaylandDisplay::checkError() const (this=<optimized out>) at /usr/include/qt5/QtCore/qlogging.h:90
Created attachment 129726 [details]
Systemsettings5 terminal log
Also this time i did run systemsettings from a terminal when it happen.
New information was added with recent comments; changing status for inspection. Created attachment 130038 [details]
New crash information added by DrKonqi
systemsettings5 (5.19.80) using Qt 5.15.0
- What I was doing when the application crashed:
This time it happen but instead of clicking on "start up and shutdown" it happen with display and monitor.
-- Backtrace (Reduced):
#4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#5 0x00007f9b1fce5539 in __GI_abort () at abort.c:79
#6 0x00007f9b200fec27 in qt_message_fatal (message=<synthetic pointer>..., context=...) at global/qlogging.cpp:1914
#7 QMessageLogger::fatal (this=this@entry=0x7ffef33bd990, msg=msg@entry=0x7f9b1b4ed0b8 "The Wayland connection broke. Did the Wayland compositor die?") at global/qlogging.cpp:893
#8 0x00007f9b1b433f25 in QtWaylandClient::QWaylandDisplay::checkError (this=<optimized out>) at /usr/include/qt5/QtCore/qlogging.h:90
*** Bug 424729 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of bug 423179 *** |