i3 hangs and stops accepting inputs after a while when run on virtual display

[DanielAW]

Welcome

• Yes, I'm using the latest major release or the current development version. These are the only supported versions.
• Yes, I've searched similar issues and discussions on GitHub and didn't find any.

Current Behavior

i3 does not accept inputs anymore, I also can not restart it (neither key bindings nor i3-msg do work). I'm running it via NoMachine on a virtual desktop when lightdm is stopped.

Expected Behavior

i3 does not stop accepting inputs

Reproduction Instructions

Difficult to reproduce. Seems like some interactions with the UI are causing the hang

i3 version

Binary i3 version:  4.23-31-g60949443 © 2009 Michael Stapelberg and contributors

Running version: < 4.2-200

Config file

# This file has been auto-generated by i3-config-wizard(1).
# It will not be overwritten, so edit it as you like.
#
# Should you change your keyboard layout some time, delete
# this file and re-run i3-config-wizard(1).
#

# i3 config file (v4)
#
# Please see https://i3wm.org/docs/userguide.html for a complete reference!

set $mod Mod4

# Handle Borders
for_window [class="^.*"] border pixel 2
                          # class                 border  backgr. text    indicator child_border
for_window [class="^.*"] client.focused          #77dd77 #285577 #ffffff #2e9ef4   #285577


# Font for window titles. Will also be used by the bar unless a different font
# is used in the bar {} block below.
#font pango:monospace 8

# This font is widely installed, provides lots of unicode glyphs, right-to-left
# text rendering and scalability on retina/hidpi displays (thanks to pango).
font pango:DejaVu Sans Mono 8

# The combination of xss-lock, nm-applet and pactl is a popular choice, so
# they are included here as an example. Modify as you see fit.

# xss-lock grabs a logind suspend inhibit lock and will use i3lock to lock the
# screen before suspend. Use loginctl lock-session to lock your screen.
#exec --no-startup-id xss-lock --transfer-sleep-lock -- i3lock --nofork

# NetworkManager is the most popular way to manage wireless networks on Linux,
# and nm-applet is a desktop environment-independent system tray GUI for it.
#exec --no-startup-id nm-applet

# Use pactl to adjust volume in PulseAudio.
set $refresh_i3status killall -SIGUSR1 i3status
bindsym XF86AudioRaiseVolume exec --no-startup-id pactl set-sink-volume @DEFAULT_SINK@ +10% && $refresh_i3status
bindsym XF86AudioLowerVolume exec --no-startup-id pactl set-sink-volume @DEFAULT_SINK@ -10% && $refresh_i3status
bindsym XF86AudioMute exec --no-startup-id pactl set-sink-mute @DEFAULT_SINK@ toggle && $refresh_i3status
bindsym XF86AudioMicMute exec --no-startup-id pactl set-source-mute @DEFAULT_SOURCE@ toggle && $refresh_i3status

# Use Mouse+$mod to drag floating windows to their wanted position
floating_modifier $mod

# start a terminal
#bindsym $mod+Return exec i3-sensible-terminal
#bindsym $mod+Return exec urxvt
bindsym $mod+Return exec alacritty

# kill focused window
bindsym $mod+Shift+q kill

# start dmenu (a program launcher)
#bindsym $mod+d exec --no-startup-id dmenu_run
bindsym $mod+d exec --no-startup-id rofi -show drun
# A more modern dmenu replacement is rofi:
# bindcode $mod+40 exec "rofi -modi drun,run -show drun"
# There also is i3-dmenu-desktop which only displays applications shipping a
# .desktop file. It is a wrapper around dmenu, so you need that installed.
# bindcode $mod+40 exec --no-startup-id i3-dmenu-desktop

# change focus
#bindsym $mod+j focus left
#bindsym $mod+k focus down
#bindsym $mod+l focus up
#bindsym $mod+semicolon focus right


# alternatively, you can use the cursor keys:
bindsym $mod+Left focus left
bindsym $mod+Down focus down
bindsym $mod+Up focus up
bindsym $mod+Right focus right

# move focused window
bindsym $mod+Shift+j move left
bindsym $mod+Shift+k move down
bindsym $mod+Shift+l move up
bindsym $mod+Shift+semicolon move right

# alternatively, you can use the cursor keys:
bindsym $mod+Shift+Left move left
bindsym $mod+Shift+Down move down
bindsym $mod+Shift+Up move up
bindsym $mod+Shift+Right move right

# split in horizontal orientation
bindsym $mod+h split h

# split in vertical orientation
bindsym $mod+v split v

# enter fullscreen mode for the focused container
bindsym $mod+f fullscreen toggle

# change container layout (stacked, tabbed, toggle split)
bindsym $mod+s layout stacking
bindsym $mod+w layout tabbed
bindsym $mod+e layout toggle split

# toggle tiling / floating
bindsym $mod+Shift+space floating toggle

# change focus between tiling / floating windows
bindsym $mod+space focus mode_toggle

# focus the parent container
bindsym $mod+a focus parent

# focus the child container
#bindsym $mod+d focus child

# Define names for default workspaces for which we configure key bindings later on.
# We use variables to avoid repeating the names in multiple places.
set $ws1 "1"
set $ws2 "2"
set $ws3 "3"
set $ws4 "4"
set $ws5 "5"
set $ws6 "6"
set $ws7 "7"
set $ws8 "8"
set $ws9 "9"
set $ws10 "10"

# switch to workspace
bindsym $mod+1 workspace number $ws1
bindsym $mod+2 workspace number $ws2
bindsym $mod+3 workspace number $ws3
bindsym $mod+4 workspace number $ws4
bindsym $mod+5 workspace number $ws5
bindsym $mod+6 workspace number $ws6
bindsym $mod+7 workspace number $ws7
bindsym $mod+8 workspace number $ws8
bindsym $mod+9 workspace number $ws9
bindsym $mod+0 workspace number $ws10

# move focused container to workspace
bindsym $mod+Shift+1 move container to workspace number $ws1
bindsym $mod+Shift+2 move container to workspace number $ws2
bindsym $mod+Shift+3 move container to workspace number $ws3
bindsym $mod+Shift+4 move container to workspace number $ws4
bindsym $mod+Shift+5 move container to workspace number $ws5
bindsym $mod+Shift+6 move container to workspace number $ws6
bindsym $mod+Shift+7 move container to workspace number $ws7
bindsym $mod+Shift+8 move container to workspace number $ws8
bindsym $mod+Shift+9 move container to workspace number $ws9
bindsym $mod+Shift+0 move container to workspace number $ws10

# reload the configuration file
bindsym $mod+Shift+c reload
# restart i3 inplace (preserves your layout/session, can be used to upgrade i3)
bindsym $mod+Shift+r restart
# exit i3 (logs you out of your X session)
bindsym $mod+Shift+e exec "i3-nagbar -t warning -m 'You pressed the exit shortcut. Do you really want to exit i3? This will end your X session.' -B 'Yes, exit i3' 'i3-msg exit'"

# resize window (you can also use the mouse for that)
mode "resize" {
        # These bindings trigger as soon as you enter the resize mode

        # Pressing left will shrink the window’s width.
        # Pressing right will grow the window’s width.
        # Pressing up will shrink the window’s height.
        # Pressing down will grow the window’s height.
        bindsym j resize shrink width 10 px or 10 ppt
        bindsym k resize grow height 10 px or 10 ppt
        bindsym l resize shrink height 10 px or 10 ppt
        bindsym semicolon resize grow width 10 px or 10 ppt

        # same bindings, but for the arrow keys
        bindsym Left resize shrink width 10 px or 10 ppt
        bindsym Down resize grow height 10 px or 10 ppt
        bindsym Up resize shrink height 10 px or 10 ppt
        bindsym Right resize grow width 10 px or 10 ppt

        # back to normal: Enter or Escape or $mod+r
        bindsym Return mode "default"
        bindsym Escape mode "default"
        bindsym $mod+r mode "default"
}

bindsym $mod+r mode "resize"

set $Locker i3lock && sleep 1

set $mode_system System (l) lock, (e) logout, (s) suspend, (h) hibernate, (r) reboot, (Shift+s) shutdown
mode "$mode_system" {
    bindsym l exec --no-startup-id $Locker, mode "default"
    bindsym e exec --no-startup-id i3-msg exit, mode "default"
    bindsym s exec --no-startup-id $Locker && systemctl suspend, mode "default"
    bindsym h exec --no-startup-id $Locker && systemctl hibernate, mode "default"
    bindsym r exec --no-startup-id systemctl reboot, mode "default"
    bindsym Shift+s exec --no-startup-id systemctl poweroff -i, mode "default"

    # back to normal: Enter or Escape
    bindsym Return mode "default"
    bindsym Escape mode "default"
}

bindsym $mod+l mode "$mode_system"

#bindsym $mod+j exec rofi -show window -kb-accept-entry "!Alt-Tab,!Alt+Alt_L" -kb-row-down "Alt+Tab" -selected-row 1
bindsym $mod+j exec /home/daniel/.config/i3/scripts/i3-alt-tab.py next current
bindsym $mod+k exec /home/daniel/.config/i3/scripts/i3-alt-tab.py prev current

# Start i3bar to display a workspace bar (plus the system information i3status
# finds out, if available)
bar {
        status_command i3status
}

floating_minimum_size 500 x 300
floating_maximum_size 2000 x 1500

exec xinput --set-prop "TPPS/2 Elan TrackPoint" "libinput Accel Speed" 0.4
exec xinput --set-prop "TPPS/2 Elan TrackPoint" "libinput Accel Profile Enabled" 1, 0
exec xinput --set-prop "SynPS/2 Synaptics TouchPad" "libinput Accel Speed" 0.8

# screen brightness controls
bindsym XF86MonBrightnessUp exec xbacklight -inc 10
bindsym XF86MonBrightnessDown exec xbacklight -dec 10

#exec xscreensaver -no-splash
#exec xss-lock -- i3lock -n &
exec vorta --daemonize &

Linux distribution & Version

Arch Linux

Are you using a compositor?

I am sure I don't run any compositor

Logfile

https://logs.i3wm.org/logs/6216700622012416.bz2

[DanielAW]

It seems the UI is still updating but I can not send any commands.

[orestisfl]

Difficult to reproduce. Seems like some interactions with the UI are causing the hang

Need to be more specific than that. What were you doing before the freeze? What is your exact setup? What's a "virtual display"?

[DanielAW]

It seems random to me, I'm just starting a new application (like virt-manager) or even just starting a new terminal in a new workspace. These interactions work for a good long time and then after some minutes the same interaction can cause the hang. A "virtual display" means I'm not running X on $DISPLAY:0. Instead, I stopped my login manager and I'm starting i3 on a "virtual display" (DISPLAY:1001) in order to be able to match the resolution of the system which I'm using to connect to the NoMachine server.

[DanielAW]

One of the last messages I see in the log seems to be:

ERROR: Expected one of these tokens: <end>, '[', 'move', 'exec', 'exit', 'restart', 'reload', 'shmlog', 'debuglog', 'border', 'layout', 'append_layout', 'workspace', 'focus', 'kill', 'open', 'fullscreen', 'sticky', 'split', 'floating', 'mark', 'unmark', 'resize', 'rename', 'nop', 'scratchpad', 'swap', 'title_format', 'title_window_icon', 'mode', 'bar', 'gaps'

[zeaktorres]

@DanielAW @orestisfl, I have been having trouble with a similar issue while just running i3 normally. I play proton games and have firefox on a second monitor. Sometimes while playing the game i3 will stutter, stop accepting inputs and freeze until it flickers a bunch and accepts inputs again. I'm sorry I can't be specific either, please let me know if there are any monitoring commands I can run to show you these errors. I've tried journalctl -xe and didn't seem to get anything of value :/... just

May 12 14:47:26 zeak rtkit-daemon[855]: Supervising 16 threads of 6 processes of 1 users.
May 12 14:47:27 zeak rtkit-daemon[855]: Supervising 16 threads of 6 processes of 1 users.
May 12 14:47:27 zeak rtkit-daemon[855]: Supervising 16 threads of 6 processes of 1 users.
May 12 14:49:06 zeak rtkit-daemon[855]: Supervising 16 threads of 6 processes of 1 users.
May 12 14:49:06 zeak rtkit-daemon[855]: Supervising 16 threads of 6 processes of 1 users.
May 12 14:51:37 zeak rtkit-daemon[855]: Supervising 16 threads of 6 processes of 1 users.
May 12 14:51:37 zeak rtkit-daemon[855]: Supervising 16 threads of 6 processes of 1 users.
May 12 14:51:51 zeak rtkit-daemon[855]: Supervising 16 threads of 6 processes of 1 users.
May 12 14:51:51 zeak rtkit-daemon[855]: Supervising 16 threads of 6 processes of 1 users.
May 12 14:51:52 zeak rtkit-daemon[855]: Supervising 16 threads of 6 processes of 1 users.
May 12 14:51:52 zeak rtkit-daemon[855]: Supervising 16 threads of 6 processes of 1 users.
May 12 14:51:52 zeak rtkit-daemon[855]: Supervising 16 threads of 6 processes of 1 users.
May 12 14:51:52 zeak rtkit-daemon[855]: Supervising 16 threads of 6 processes of 1 users.
May 12 14:53:38 zeak sudo[1066114]:     zeak : TTY=pts/0 ; PWD=/home/zeak ; USER=root ; COMMAND=/usr/bin/pacman -Syu
May 12 14:53:38 zeak sudo[1066114]: pam_unix(sudo:session): session opened for user root(uid=0) by zeak(uid=1000)
May 12 14:56:35 zeak sudo[1066114]: pam_unix(sudo:session): session closed for user root
May 12 15:01:53 zeak rtkit-daemon[855]: Supervising 16 threads of 6 processes of 1 users.
May 12 15:01:53 zeak rtkit-daemon[855]: Supervising 16 threads of 6 processes of 1 users.
May 12 15:08:29 zeak rtkit-daemon[855]: Supervising 16 threads of 6 processes of 1 users.
May 12 15:08:29 zeak rtkit-daemon[855]: Supervising 16 threads of 6 processes of 1 users.