Reply to topic

KWin repeatedly crashing, how to debug?

User avatar Fire-Dragon-DoL
Registered Member
Posts
8
Karma
0
Hello! I'm facing repeatedly this problem:

- KWin randomly crashes (I lose all window titlebars etc) and I can "resurrect it" using
Code: Select all
kwin --replace &
from a Konsole
- This happens repeatedly: 10-20 times during the day
- The software I'm running is Chrome and Sublime Text, as well as Synergy
- I use a lot of desktop switching (very fast) and alt tab (2 windows per desktop)
- I have a system76 laptop which runs on NVIDIA GPU all time (doesn't use the intel one)

I can't really understand what's causing the crash, the only logs I have is from when I run
Code: Select all
kwin --replace
without sending it to the background. But they all crashed for different reasons, here the reports:

The X11 connection broke: No error (code 0)
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
after 248018 requests (248018 known processed) with 0 events remaining.
QObject::~QObject: Timers cannot be stopped from another thread
QtDBus: cannot relay signals from parent QObject(0x55848420e150 "") unless they are emitted in the object's thread QThread(0x558484184db0 ""). Current thread is QSGRenderThread(0x7fd8b0005960 "").


QXcbConnection: XCB error: 3 (BadWindow), sequence: 178, resource id: 127926278, major code: 20 (GetProperty), minor code: 0
kf5.kcoreaddons.desktopparser: Property type "Url" is not a known QVariant type. Found while parsing property definition for "X-KWin-Video-Url" in "/usr/share/kservicetypes5/kwineffect.desktop"
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1806, resource id: 0, major code: 14 (GetGeometry), minor code: 0
trying to show an empty dialog
trying to show an empty dialog
QOpenGLContext::swapBuffers() called with non-exposed window, behavior is undefined
The X11 connection broke: No error (code 0)
XIO: fatal IO error 2 (No such file or directory) on X server ":0"
after 188000 requests (188000 known processed) with 0 events remaining.
QObject::~QObject: Timers cannot be stopped from another thread
QThread::wait: Thread tried to wait on itself
QtDBus: cannot relay signals from parent QObject(0x557acf93f420 "") unless they are emitted in the object's thread QThread(0x557acf8b5db0 ""). Current thread is QSGRenderThread(0x557acff5dac0 "").

[1]+ Exit 1 kwin --replace


The X11 connection broke: No error (code 0)
XIO: fatal IO error 17 (File exists) on X server ":0"
after 173389 requests (173389 known processed) with 0 events remaining.
QObject::~QObject: Timers cannot be stopped from another thread
QtDBus: cannot relay signals from parent QObject(0x555e2833c9b0 "") unless they are emitted in the object's thread QThread(0x555e282b3db0 ""). Current thread is QSGRenderThread(0x555e28725d50 "").


As you can see, the error was different all 3 times. I cannot figure out what's causing it.
I cannot replace chrome, since in any case all software I use is chromium based: Discord, Chrome, Franz (an app to merge multiple chats), all 3 are Electron apps (so Chromium based).

If someone knows the cause, great, but I'm definitely open to debug this more. I need to find a solution, this problem since last update is getting pretty heavy: it was happening once/twice per day before, but now it can potentially happen 4-5 times in a row!
User avatar shadowfire
Registered Member
Posts
5
Karma
0
OS
I'm having the same issue since running my weekly Fedora updates this morning; kwin sometimes crashes after switching to another window on a different virtual desktop:

XIO: fatal IO error 17 (File exists) on X server ":0"
after 6440787 requests (6440787 known processed) with 0 events remaining.
QObject::~QObject: Timers cannot be stopped from another thread
QtDBus: cannot relay signals from parent QObject(0x55fa3ecb76b0 "") unless they are emitted in the object's thread QThread(0x55fa3ec36390 ""). Current thread is QSGRenderThread(0x55fa3eedcd20 "").

kwin-5.12.5-1.fc27.x86_64
kwin-libs-5.12.5-1.fc27.x86_64
xorg-x11-drv-nvidia-libs-390.59-1.fc27.x86_64
User avatar Fire-Dragon-DoL
Registered Member
Posts
8
Karma
0
shadowfire wrote:I'm having the same issue since running my weekly Fedora updates this morning; kwin sometimes crashes after switching to another window on a different virtual desktop:

XIO: fatal IO error 17 (File exists) on X server ":0"
after 6440787 requests (6440787 known processed) with 0 events remaining.
QObject::~QObject: Timers cannot be stopped from another thread
QtDBus: cannot relay signals from parent QObject(0x55fa3ecb76b0 "") unless they are emitted in the object's thread QThread(0x55fa3ec36390 ""). Current thread is QSGRenderThread(0x55fa3eedcd20 "").

kwin-5.12.5-1.fc27.x86_64
kwin-libs-5.12.5-1.fc27.x86_64
xorg-x11-drv-nvidia-libs-390.59-1.fc27.x86_64


Yes, that's exactly what I'm noticing, when I go to a window on another desktop, it crashes (sometimes, not always).
User avatar shadowfire
Registered Member
Posts
5
Karma
0
OS
I think it's related to the Desktop Switch OSD. Turning it off seems to help on my system:

System Settings -> Desktop Behaviour -> Virtual Desktops -> Switching -> uncheck: Desktop Switch On-Screen Display
User avatar Fire-Dragon-DoL
Registered Member
Posts
8
Karma
0
shadowfire wrote:I think it's related to the Desktop Switch OSD. Turning it off seems to help on my system:

System Settings -> Desktop Behaviour -> Virtual Desktops -> Switching -> uncheck: Desktop Switch On-Screen Display


Oh my, thanks man. That made my day.
It literally went from crashing every ~7 minutes to no crashes (yet).

Turned my system back to human...

Is an issue already filed for this?
User avatar shadowfire
Registered Member
Posts
5
Karma
0
OS
Fire-Dragon-DoL wrote:[Is an issue already filed for this?


Haven't looked thoroughly but someone here seems to be having the same issue: https://bugs.kde.org/show_bug.cgi?id=368847#c5

Also I could not reproduce the problem on my other workstation which also runs KDE Plasma on Fedora 27 but has older hardware. (NVIDIA GeForce GT218 versus NVIDIA GeForce GTX 1060 on my 'crashy' workstation; but using NVIDIA's proprietary driver.)
User avatar Fire-Dragon-DoL
Registered Member
Posts
8
Karma
0
shadowfire wrote:
Fire-Dragon-DoL wrote:[Is an issue already filed for this?


Haven't looked thoroughly but someone here seems to be having the same issue: https://bugs.kde.org/show_bug.cgi?id=368847#c5

Also I could not reproduce the problem on my other workstation which also runs KDE Plasma on Fedora 27 but has older hardware. (NVIDIA GeForce GT218 versus NVIDIA GeForce GTX 1060 on my 'crashy' workstation; but using NVIDIA's proprietary driver.)


Interesting, the laptop where this happens uses the proprietary driver and has a gtx 1070, wonder if it's (another) nvidia bug
User avatar shadowfire
Registered Member
Posts
5
Karma
0
OS
shadowfire wrote:Also I could not reproduce the problem on my other workstation which also runs KDE Plasma on Fedora 27 but has older hardware. (NVIDIA GeForce GT218 versus NVIDIA GeForce GTX 1060 on my 'crashy' workstation; but using NVIDIA's proprietary driver.)


Oops I made a typo: I meant both are using NVIDIA's proprietary driver. Although different versions:

fine (legacy driver for < 2010 models):
NVIDIA GeForce GT218
akmod-nvidia-340xx-340.106-1.fc27.x86_64
xorg-x11-drv-nvidia-340xx-340.106-1.fc27.x86_64

crashy DSOSD (newer driver):
NVIDIA GeForce GTX 1060
akmod-nvidia-390.59-1.fc27.x86_64
xorg-x11-drv-nvidia-390.59-1.fc27.x86_64

Fire-Dragon-DoL wrote:
Interesting, the laptop where this happens uses the proprietary driver and has a gtx 1070, wonder if it's (another) nvidia bug


So I guess if it is nvidia it somehow depends on the model...

 
Reply to topic

Bookmarks



Who is online

Registered users: Bing [Bot], claydoh, Google [Bot], kristynspecter, Lachu, Yahoo [Bot]