-
Notifications
You must be signed in to change notification settings - Fork 10
Compositor crashes when "abruptly and normally" closing VLC #118
Comments
Upon crash there should be a sad face in the notification area. If you click on it you'll open a "sorry" dialog. |
Yeah I remember that sad face icon notification back when I was using Kubuntu. However I do not get any notification at all right now. Not sure if it's disabled by Garuda team or the crash does not log anything. I enabled all pop-up notification, marking to systray and logging to a specific file in the Notifications settings page in System Settings but nothing shows anywhere. So what I did is I was hitting
Quite possible all this has nothing to do with the crash itself, I cannot tell. I googled around but could not find where kwin stores its backtrace log files. I'm kinda stuck. Maybe I should post on the Garuda forums, that's another option, someone or the team could tell me what I need to do to acces such trace... or maybe I could use I hate when I cannot provide clean data. :( |
Let's try to acquire a better backtrace. Open an SSH connection to the machine (yes) and type:
This engages a debugger. After that type:
This will start a debugging session of KWin. Crash it and then the display will freeze and the debugger will say something about SIGSEGV or SIGABRT. Type:
then
This will output a backtrace which should come in handy. |
Adding to this, I see an error when redirecting subwindows.... Hmmmm.... |
Wow I didn't know it was possible to ssh a machine to itself. But gdb failed. Here's what I did:
Entered PW of course and I was in
Then
That replaced kwin I saw it restarting. I then opened a video and when I hit close button, the entire computer locked up with absolutely nothing showing on the screen other than how the screen was at the exact moment it froze. Only the mouse was still moving but no button. It disappeared as soon as I hit ALT key. Something there doesn't want me to debug. :) |
It is intended to freeze. It means it crashed. Try again, but when it freezes immediately check the debugger in your SSH session. It should say something (if it doesn't you can hit Ctrl-C and you will jump back to the debugger). Also, there should be some "FOR CRASH" messages that might come in handy. One more footnote: You have to run the debugger on a separate computer (or a phone with an SSH app installed), or at least a different TTY... |
That's probably why. I am on my localhost connected to localhost on the same TTY. It freezes before showing any debug info and CTRL-C, X, Q, BREAK, etc. don't do a thing. I'll see what other device I can use, I wonder if Chromebook would work, I've got 4 options, 2nd TTY on same machine, Chromebook, Windows 11 and Android phone (version 12). One of these will certainly work. I can test TTY right now, if it fails it'll take me a bit longer to move on another device, but I will. |
...yyyyyup. If you don't have another device you can use a TTY instead. |
It seems I have issues with TTYs. Even when TTY1 is working cleanly, when I start TTY2 only Conky launches. Back to TTY1 and compositor acts strangely, lost functions and no window border. So I'll move on another device to ssh. |
That doesn't seem normal, but I'll wait. |
Could be also a problem from the upstream KDE since it haves many bugs right now. https://www.phoronix.com/scan.php?page=news_item&px=KDE-Starts-December-2021 |
@ptr1337 It's definitely not. This is an issue with unredirection, so it is not a bug in vanilla KWin. |
Nope it's not. lol There seems to be conflicting PIDs when second TTY starts in X, maybe it's a Garuda thing, but I got a bigger dog to chase before I look into that one. :) I will be able to perform more SSH stuff tonight, in the meantime I realized I don't understand well enough how that principle works. I googled a few things but it was difficult to find something related to what I'm trying to do here and what I'm trying to understand. Maybe someone can help me understand a bit more? Here's where I'm confused:
All that being said, I was able to log into machine#1 from my Chromebook through SSH. So I could debug there, as long I use the proper gdb commands, should they be different then those from a few posts above. And I believe I don't need to startx. Thank you very much! |
First of all, you do not need to start another X session in order to debug KWin.
Got it... Basically SSH is a thing that allows you to remotely connect to your machine.
Yes, you can. But please do not type
It appears you didn't understand my last sentence, so let me phrase it clearly. SSH does not hook to TTY1 or something. It creates a virtual terminal (when you type
Because you set the DISPLAY environment variable.
Yep, correct. Again, do not ever type |
In a summary, here is what you need to do in order to acquire a backtrace:
|
Yes! Got it! I understand better now what I was doing. :) Here ya go:
|
Hmmm... that looks odd. Can you try disabling unredirection (System Settings > Display and Monitor > Compositor > Enable full-screen unredirection (X11)) and see if it still reproduces? |
You are good.
It does reproduce with that cool feature disabled.
WORKS! Not an option for me to disable it, though, as Garuda's theme is heavily based on blur and translucency, but maybe for some people it is an acceptable workaround. |
Hi, I see this has been tagged as a BUG, maybe it was there last month I didn't pay attention. Either way lemme know if you need more data to troubleshoot. :) Thanks! |
I do confirm having the exact same bug, on Arch, with an Nvidia GTX 1660 TI. |
Hello and thanks for this improved kwin, I can play smoothly 4k@60hz with your unredirection setting on full screen videos.
I recently upgraded to 5.23.4. When I play a VLC video (the mode with just one window opened and the controls showing right under the video in that same window) and I do what everyone does since 1000 years which is hit the close button while playing, it then crashes kwin. Thanks to your option to restart the compositor without disabling it.
Now if I uninstall kwin-lowlatency and install same version (5.23.4) of kwin, it does not crash at all.
I am not sure what trace log to provide, but I did come across some info here https://forum.videolan.org/viewtopic.php?f=13&t=149762&start=25
I have a Nvidia GTX1650 with 495 drivers, of course I can test this with a different driver version if need be or a different video player/video mode, however my question is not who is responsible but rather why. Why is it that with kwin-lowlatency is crashes and not the standard kwin, what's different between the 2 so it does that?
What is mentioned on the above URL is true, if I stop the video and then hit the close button, kwin-lowlatency does not crash, but it's also not intuitive to stop the video before closing, so many times I forget and it crashes.
Thanks
The text was updated successfully, but these errors were encountered: