You are not logged in.
Hi,
When I leave a window idle for a while, it freezes: its display is not updated any more. This happens for most of my applications (Firefox, slack, thunderbird, …) but interestingly it doesn't seem to happen for gnome-terminal.
The bug appeared recently (in the last couple of days). Unfortunately, I cannot roll-back the installation as I have deleted pacman's cache since then.
Could it be due to a recent update from Linux 4.x to 5.0?
System configuration:
- Laptop: HP 1040G3 with Intel i7-6600U CPU and integrated GPU
- Window manager: i3 (running with compton)
- Kernel: Linux 5.0.0-arch1-1-ARCH #1 SMP PREEMPT Mon Mar 4 14:11:43 UTC 2019 x86_64 GNU/Linux
Additional informations:
- nothing shows up in the console if I launch e.g. firefox and it freezes
- nothing shows up in the journal (journalctl -xn -f doesn't show anything).
Last edited by cphyc (2019-03-18 14:45:22)
Offline
Try downgrading your kernel.
I don't want to work. I want to bang on the drum all day.
Offline
Drop the compositor (compton) from the equation.
Online
Thanks for your replies. I am trying now with the LTS kernel (Linux 4.19.28-1-lts #1 SMP Sun Mar 10 09:37:48 CET 2019 x86_64 GNU/Linux) and it seems to work just fine (with and without the compositor).
Offline
You may want to narrow the issue w/ the 5.0 kernel - at some point the lts kernel will bump…
Online
Might not help but I'm getting this too with anything GPU accelerated, this includes alacritty and Spotify but not Firefox (strangely).
What's weird is that this only happens on my laptop's monitor, if I have the window on my external monitor over USB-C -> HDMI everything's fine. Here's my set up:
* 5.0.0-arch1-1-ARCH #1 SMP PREEMPT Mon Mar 4 14:11:43 UTC 2019 x86_64 GNU/Linux
* Dell XPS 13
* i3
* compton
My colleague on a newer version of this laptop but running Arch, 5.0.0 and xmonad is not experiencing this problem. I don't think he has a compositor though...
It's looking like it could be i3 + (maybe) compton + Linux 5. I only started seeing this after updating.
Last edited by Olical (2019-03-13 10:04:50)
Offline
So after a day or so of usage, I can confirm that running on the LTS version of the kernel + compton + i3 solved the issue (4.19.28-1-lts), but I'm worried that it will break once the LTS bumps into 5.x.
Offline
Take. The. Compositor. Out. Of. The. Equation.
In case it's compton:
1. run compton on the xrender backend and see whether the issue remains
2. post your xorg logs, dmesg & the output of glxinfo
Online
Thanks for the help seth but there's really no need to write such an aggressive message.
I'll try your suggestion and post my xorg log, dmesg and the output of glxinfo if I can reproduce the bug on Linux 5.0.
Offline
I didn't see that as aggressive. Assertive maybe. Direct yes. But it does seem it was needed as you were ignoring the suggestion up until that point.
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
It wasn't meant to be aggressive, just really stressing the point I made before and that apparently escaped general attention.
When I'm aggressive, I'll use a lot of mean words ;-)
Online
Fair enough.
It didn't escape my attention but I first wanted to get a working solution even temporary since my computer is also my work station. This was achieved by downgrading the kernel. I'll post updates about using Linux 5.0 and the messages as soon as I get some spare time.
Offline
When I'm aggressive, I'll use a lot of mean words ;-)
I don't recall ever having seen that with you
OP: Is your machine configured to sleep after some period of time?
When a window freezes, can you unfreeze it?
- try converting to a floating window, then back to titled.
- try moving the window to scratchpad, then restore it
- try changing the layout between split and tabbed.
- try moving the window to another workspace.
- try resize.
Does the window respond to WM messages such as close?
Does freeze mean that the display stops updating, or that it does not respond to keyboard inputs? Pointer inputs?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Looks like killing compton has kept my terminals running this morning. And with regards to ewaller's questions (even though I'm not OP):
There doesn't appear to be a way to unfreeze them, I can move them around to different monitors and workspaces, it doesn't fix it. I _think_ I tried floating and then non-floating to no effect.
I can't close it through i3, I have to use kill from my terminal. No keyboard inputs seem to work at all but Spotify continued to play music (maybe it was in another process though?). I couldn't exit a terminal by sending EOF etc.
I do have it set to lock and turn the screen off after a while of inactivity, I think I've removed most power utils though since it was causing issues with USB mice and keyboards.
So without compton everything seems fine, when it did lock up there was no way to unfreeze it as far as I could tell.
Offline
Try to kill compton after the freeze starts (setup a shortcut or kill it from another VT)
You can then also check whether restarting compton will re-freeze the window immediately (ie. whether the window stops generating damage events or compton simply doesn't react on them)
Other than that see the items on https://bbs.archlinux.org/viewtopic.php … 8#p1836538 (where the logs will mostly be for a pattern detection)
Online
Compton isn't running but I've had a terminal freeze on me after a few hours. Moving, resizing, popping in and out of float does nothing.
Here's how it looks when you resize: https://imgur.com/9OG2KQJ.png - so it's painting but not clearing. So the issue still persists with compton out of the mix. Only one terminal out of three has done this so far today though.
I tried starting then killing compton out of interest, no difference. And now for some logs, even though I don't see anything suspect in them: https://gist.github.com/Olical/3978c159 … 951e6a8a9d
Hopefully this information helps to cross reference with others and get to the bottom of this.
Offline
Drop xf86-video-intel and restart X11 - still reproducable?
Online
I couldn't startx or lightdm without xf86-video-intel and I need my laptop today, I'll report in when I get time to get my laptop working without it and leave a terminal open for a while.
Offline
left-over intel.conf in /etc/X11/xorg.conf.d/ or /usr/share/X11/xorg.conf.d/ ?
Online
OP: Is your machine configured to sleep after some period of time?
When a window freezes, can you unfreeze it?
- try converting to a floating window, then back to titled.
- try moving the window to scratchpad, then restore it
- try changing the layout between split and tabbed.
- try moving the window to another workspace.
- try resize.Does the window respond to WM messages such as close?
Does freeze mean that the display stops updating, or that it does not respond to keyboard inputs? Pointer inputs?
The machine is not configured to sleep after some period of time and I cannot unfreeze any frozen window.
When a window freezes, I can still convert from and to floating and I can push it to the scratchpad, as well as split it, etc. However, it does not react to keyboard inputs (e.g. I cannot close it using i3's kill command). I can only close it using xkill or by killing the process.
Output of glxinfo: https://pastebin.com/Z58RiXnU
Output of dmesg: https://pastebin.com/cXdgJwtR
Output of /var/log/Xorg.0.log
Offline
left-over intel.conf in /etc/X11/xorg.conf.d/ or /usr/share/X11/xorg.conf.d/ ?
In /etc/X11/xorg.conf.d/ I have a file named `20-intel.conf` containing
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
EndSection
Offline
Well, if you want to avoid the intel driver, the config must not explicitly ask for it - so remove that file along xf86-vide-intel…
Online
I am now trying with mesa instead of xf86-video-intel on Linux 5.0.2-arch1-1-ARCH, thanks for the help! I'll close the topic if I can confirm that it works.
Offline
Hi,
Try to put
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "DRI" "2"
EndSection
here /etc/X11/xorg.conf.d/20-intel.conf
It works for me. I'm using "xf86-video-intel" and I have the same problem before. After this "fix" - no problem so far
Offline
I can confirm that deactivating xf86-video-intel (removing the package + commenting out /etc/X11/xorg.conf.d/20-intel.conf) fixes the issue.
I haven't tried lulo.lupov's solution though.
Offline