i3: Windows become empty and can't be restored!
I’m submitting a…
[x] Bug [ ] Feature Request [ ] Documentation Request [ ] Other (Please describe in detail)
Current Behavior
Seemingly randomly the content of some windows vanishes e.g. Firefox on workspace 1 works, switching workspaces and everything else works for some time, I switch back to workspace 1 from another workspace and what I see then is the content of the window from the workspace I just was on. Only the title of the window is correct and show firefox, but not the content. Reloading i3 leads to workspace 1 being a frame with the correct title, filled with black. Other windows on other workspaces still work. The same happened not only to a window with Firefox but also with my terminal emulator gnome-terminal
.
Expected Behavior
Content of windows should stay visible at all times.
Reproduction Instructions
None, there is no visible logic to this.
Environment
Output of i3 --moreversion 2>&-
:
Binary i3 version: 4.19.1 (2021-02-01) ? 2009 Michael Stapelberg and contributors Running i3 version: 4.19.1 (2021-02-01) (pid 19510) Loaded i3 config: /home/sapiens//.config/i3/config (Last modified: Sun 25 Jul 2021 06:40:22 PM CEST, 614425 seconds ago) The i3 binary you just called: /usr/bin/i3 The i3 binary you are running: i3
Config URL: https://github.com/s-a-p-i-e-n-s/upload/blob/main/i3_config
Logfile URL: https://raw.githubusercontent.com/s-a-p-i-e-n-s/upload/main/i3_debug_log
- Linux Distribution & Version: Arch Linux - Are you using a compositor (e.g., xcompmgr or compton): picom
If you need more (specific) information, please let me know! Thanks to all in advance!
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 26 (9 by maintainers)
No idea if this comment helps, but: Once upon a time, there was DRI2. Then came the new and fancy DRI3 and with it came lots of new code. That option that you use disables that new code and makes everything use the old DRI2 code instead (I think it makes Xorg just not announce that it supports DRI3, but I am not sure). Thus, the bug is somewhere in that “lots of new code”. Random guess would be: Somewhere in xf86-video-intel (the video driver), Xorg (the X11 server - but I actually doubt this), or in mesa (this is the “other end” that should talk DRI3 with the X11 server - but… mesa is OpenGL or Vulkan; does steam use that?!?)