Properly close disabled outputs restored during a restart. (#2337)
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
This commit is contained in:
committed by
Michael Stapelberg
parent
a8757625c3
commit
dbafb3cf23
@ -60,6 +60,12 @@ void init_ws_for_output(Output *output, Con *content);
|
||||
*/
|
||||
void randr_query_outputs(void);
|
||||
|
||||
/**
|
||||
* Disables the output and moves its content.
|
||||
*
|
||||
*/
|
||||
void randr_disable_output(Output *output);
|
||||
|
||||
/**
|
||||
* Returns the first output which is active.
|
||||
*
|
||||
|
Reference in New Issue
Block a user