Bug | Unstopping Logging file when sleeping/locking screen #167
Comments
|
That is very concerning! I'm not sure how the process could run and writing could happen whilst the laptop is asleep. We will deal with this.
It would be great if you could post your cfg.yaml as well as the .log up until it starts thrashing. |
|
Hi, Thank you for your quick response. I just did a few test, it seems it is because that I use the command As for your second question, the repeated logs have different timestamps. If you could help me fix it, I will really appreciate it. |
Ah I see. I think I've seen something like this before: https://gitlab.freedesktop.org/wlroots/wlroots/-/issues/2325 Take a look at your sway logs. There may be a constant stream of pageflip/commit fail messages. They indicate that the monitor is in an undefined state. Try setting wiki: Unusable Displays Following MODE For me to help you further I'm going to need:
|
|
Hi, Attached is the log detail, I removed the repeated records from 48s-59s As for the second question, I think it is just turn the screen off. |
That's good news - makes our diagnosis easier.
That's a bad sign. It looks like (cut off) it might be trying all modes and failing them all. I've seen that on a laptop with an nvidia GPU failing to pass through to intel, with some nonstandard nvidia module options set. Sway/wlroots logs confirmed it with DRM setting failures. What is your laptop make/model? Options, easiest first: In all cases, please observe and collect your sway logs. They'll indicate problems that won't be reported to way-displays.
MODE:
- NAME_DESC: XV340CK
WIDTH: 1920
HEIGHT: 1080
HZ: 60
|
|
Hi, thank you! my make/model is Huawei/Matebook14. I believe I'm in the pure cpu mode, the Nvidia GPU is deactivated. I will try the options you mentioned.
|
|
The results of step 2 |
|
3, sway.log file |
|
By the way, just a work around, remove the log file seems eliminate the issue. |
|
Thanks for all the digging. Unfortunately there's nothing unusual in the sway logs. What were the results of 1, 2 and 3? Did the display work correctly?
That is very strange! Do you mean that the display failures are eliminated? Is it an issue with Alternatively, for testing, you could run |
|
For the option 1,2,3, all of them display correctly, but they still created really large log file (about 1GB). The display works, but it creates infinite log file which consumes all the /tmp space. I will try to store it into another location and update it later. |
|
I tried to log to /home/leeliu/wd.log, the logging file goes to 1GB too when monitor has been off. |
|
This is very puzzling; I'm not able to replicate anything with sway 1.9 wlroots 0.17.2. Deprecated Let's confirm so that we can come up with a full test case:
Based on the above, I'm going to ask for a complete single test case. We have a lot of information above however they are for different scenarios and it's not clear what the conditions are. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, thank you for your excellent work! I really like it. I noticed there is a bug during sleeping, as it keeps writing the log files when my laptop is sleeping, which consumes all my /tmp file space. I checked the .log file, as shown in the figure, it keeps writing the lines in the image.
The text was updated successfully, but these errors were encountered: