dbafb3cf23
If an output is disabled during a restart, for example because a binding such as bindsym $mod+Shift+r exec "xrandr --auto", restart is used, it can happen that we first write the layout to disk and only then receive the RandR change events. This leads to a situation where the restored tree will contain these outputs, but the restarted i3 process will not receive the RandR events, thus the internal output in i3 is marked disabled. This patch finds these cases after a restart and force-disables the affected outputs. fixes #2326 |
||
---|---|---|
.github | ||
contrib | ||
debian | ||
docs | ||
i3-config-wizard | ||
i3-dump-log | ||
i3-input | ||
i3-msg | ||
i3-nagbar | ||
i3bar | ||
include | ||
libi3 | ||
man | ||
parser-specs | ||
src | ||
testcases | ||
travis | ||
.clang-format | ||
.gitignore | ||
.travis.yml | ||
DEPENDS | ||
I3_VERSION | ||
LICENSE | ||
Makefile | ||
PACKAGE-MAINTAINER | ||
RELEASE-NOTES-4.12 | ||
VERSION | ||
common.mk | ||
generate-command-parser.pl | ||
i3-dmenu-desktop | ||
i3-migrate-config-to-v4 | ||
i3-save-tree | ||
i3-sensible-editor | ||
i3-sensible-pager | ||
i3-sensible-terminal | ||
i3-with-shmlog.xsession.desktop | ||
i3.applications.desktop | ||
i3.config | ||
i3.config.keycodes | ||
i3.xsession.desktop | ||
logo.svg | ||
pseudo-doc.doxygen | ||
release.sh |