All windows are closed after extended periods of screen off time or suspend #1755
Comments
|
That's not the intended behaviour, so feels like a bug. I regularly turn screens off and leave my box for long periods with no clients shutting down. Not sure how to best fault find, but think that capturing a debug log (labwc -d) is worth trying in first instance. |
|
So I started labwc with labwc -d >> ~/output, I then opened a file manager, text editor, and a calculator, I then suspended my PC for 5 minutes, when I awakened it they were all closed, the file in ~/output was empty, so I exited labwc and took a picture of the screen, which I'll upload, I didn't see any errors, only something about /run/seatd.sock
|
You need to redirect stderr to get debug log. |
|
It seems to close all apps when it looses connection with the display, like if I unplug the HDMI cable for about 5 seconds. log output |
|
What version of labwc are you running? Do the clients that die report anything to the console whence they started? I'm a bit surprised that your photograph shows no output from the clients that died. Perhaps you can run one of the clients with "WAYLAND_DEBUG=1" and capture the resulting output for some hints. |
|
Hm.. I dont' see anything obvious in the log. The monitor is disconnected 16 seconds in and then reconnected 8 seconds later. Then, 40 seconds after startup it seems labwc was terminated. Can you confirm this? Or was labwc still running when you extracted the log? |
|
Its version 0.7.1, my process was I started labwc -d, opened a few apps, disconnected the HDMI cable for about 5 seconds or so, reconnected it, saw no apps were open, so I ran labwc -e to exit, I'll try the opening an app with wayland debug. |
|
So here is the log from mousepad run in debug mode when I pulled the HDMI cable log output |
|
And the log from labwc when I had mousepad in debug mode, I did the same process as before log output |
|
With the master branch you can add
|
|
I've long had a problem with some apps dying when turning off monitor and then back on. Don't use steam so can't address anything about that package. I would imagine the root of much of these problems is in wlroots though. |
|
I just tested mousepad 0.6.2 on Void Linux through a cycle which, on my AMD hardware, is sufficient to trigger attached displays to disconnect and reconnect. The application survived. Either it's a race and the disconnect/reconnect cycle is happening quickly enough for me that the application doesn't see anything, or there is something unique about your setup. |
|
For what its worth now that I'm running the master branch I tried adding LABWC_FALLBACK_OUTPUT=fallback to ~/.config/labwc/environment but it didn't make any difference, its apps getting closed on suspend that I have to work around, its not a big deal, I just have to make sure not to suspend if I have something unfinished opened, this is the error log for the master branch when suspended for a few hours, the apps don't seem to get closed if suspended only for half an hour or so. log output |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I don't know if this is a bug or some config option that I've missed, but the other day I needed to download a few large steam games so I left the steam client open so it could download them, then I turned my monitor off while I went out for a few hours, I also had the browser open too, then when I got home I turned my monitor back on and steam and the browser weren't open, so I opened steam and it had barely downloaded anything, I also noticed that if I have my browser open and I suspend my system overnight, when I awaken it from suspend in the morning the browser is no longer open, is there any way to change this behaviour? thanks.
The text was updated successfully, but these errors were encountered: