i3 consistently fails to accept any user input

nstgc · 2015-01-01 19:54:41

I first installed i3 several months ago, and everytime I start it my system seems to lock up. I cannot move the mouse nor will any keys register such as ctrl+alt+F2 (to get into a TTY). I also tried unplugging and plugging back in my USB keyboard and mouse. To exit I must hit the power button which initiates a shutdown. Jounalctl shows a shutdown was sent and executed, which is a huge relief, but there is nothing before that to indicate any sort of failure. Neither the Arch Wiki nor the i3 manual have anything in them that would help. I tried posting on the upstream faq however that was not the thing to do I was told. Some one did confirm that my issue is not normal, and suggested filing a bug report. Before doing that, however, I wanted to check with the forums to make sure I can't work something out.

Head_on_a_Stick · 2015-01-01 20:09:46

Did you follow the suggestion in the link and try a different Window Manager?

How are you starting i3?

Please post your startup file (presumably ~/.xinintrc) and your ~/.i3/config

Is there anything in the journal?

nstgc · 2015-01-01 21:20:59

Oh, yes. This is the same system that I am using, and have been using since June 6th.

I am starting i3 with xinit i3

#!/bin/sh
#
# ~/.xinitrc
#
# Executed by startx (run your window manager from here)

if [ -d /etc/X11/xinit/xinitrc.d ]; then
  for f in /etc/X11/xinit/xinitrc.d/*; do
    [ -x "$f" ] && . "$f"
  done
  unset f
fi

# exec gnome-session
# exec startkde
# exec startxfce4
#exec enlightenment_start
#~ exec gnome-session
# ...or the Window Manager of your choice

session=${1:-gnome}

case $session in
    awesome           ) exec awesome;;
    bspwm             ) exec bspwm;;
    catwm             ) exec catwm;;
    cinnamon          ) exec cinnamon-session;;
    dwm               ) exec dwm;;
    enlightenment     ) exec enlightenment_start;;
    ede               ) exec startede;;
    fluxbox           ) exec startfluxbox;;
    gnome             ) exec gnome-session;;
    gnome-classic     ) exec gnome-session --session=gnome-classic;;
    i3|i3wm           ) exec i3;;
    icewm             ) exec icewm-session;;
    jwm               ) exec jwm;;
    kde               ) exec startkde;;
    mate              ) exec mate-session;;
    monster|monsterwm ) exec monsterwm;;
    notion            ) exec notion;;
    openbox           ) exec openbox-session;;
    unity             ) exec unity;;
    xfce|xfce4        ) exec startxfce4;;
    xmonad            ) exec xmonad;;
    # No known session, try to run it as command
    *) exec $1;;
esac

~/.i3 exists, but is an empty directory.

As for the journal, nothing of interest as far as I can see.

Jan 01 14:28:52 Lain-Arch login[480]: LOGIN ON tty1 BY nstgc
Jan 01 14:29:02 Lain-Arch systemd-timesyncd[455]: Using NTP server 216.239.32.15:123 (time1.google.com).
Jan 01 14:29:03 Lain-Arch systemd-timesyncd[455]: interval/delta/delay/jitter/drift 64s/+0.011s/0.044s/0.000s/+0ppm
Jan 01 14:30:07 Lain-Arch systemd-timesyncd[455]: interval/delta/delay/jitter/drift 128s/-0.000s/0.043s/0.000s/+0ppm
Jan 01 14:32:15 Lain-Arch systemd-timesyncd[455]: interval/delta/delay/jitter/drift 256s/+0.014s/0.068s/0.005s/+26ppm
Jan 01 14:33:59 Lain-Arch kernel: nvidia 0000:01:00.0: irq 58 for MSI/MSI-X
Jan 01 14:33:59 Lain-Arch kernel: NVRM: Your system is not currently configured to drive a VGA console
Jan 01 14:33:59 Lain-Arch kernel: NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
Jan 01 14:33:59 Lain-Arch kernel: NVRM: requires the use of a text-mode VGA console. Use of other console
Jan 01 14:33:59 Lain-Arch kernel: NVRM: drivers including, but not limited to, vesafb, may result in
Jan 01 14:33:59 Lain-Arch kernel: NVRM: corruption and stability problems, and is not supported.
Jan 01 14:34:00 Lain-Arch systemd-logind[460]: kernel does not support evdev-revocation
Jan 01 14:34:11 Lain-Arch systemd-logind[460]: Power key pressed.
Jan 01 14:34:11 Lain-Arch systemd-logind[460]: Powering Off...
Jan 01 14:34:11 Lain-Arch systemd-logind[460]: System is powering down.
Jan 01 14:34:11 Lain-Arch systemd[563]: Starting Shutdown.
Jan 01 14:34:11 Lain-Arch systemd[563]: Reached target Shutdown.
Jan 01 14:34:11 Lain-Arch systemd[563]: Starting Exit the Session...
Jan 01 14:34:11 Lain-Arch systemd[563]: Stopping Default.
Jan 01 14:34:11 Lain-Arch systemd[563]: Stopped target Default.
Jan 01 14:34:11 Lain-Arch systemd[563]: Stopping Basic System.
Jan 01 14:34:11 Lain-Arch systemd[563]: Stopped target Basic System.
Jan 01 14:34:11 Lain-Arch systemd[563]: Stopping Sockets.
Jan 01 14:34:11 Lain-Arch systemd[563]: Stopped target Sockets.
Jan 01 14:34:11 Lain-Arch systemd[563]: Stopping Paths.
Jan 01 14:34:11 Lain-Arch systemd[563]: Stopped target Paths.
Jan 01 14:34:11 Lain-Arch systemd[563]: Stopping Timers.
Jan 01 14:34:11 Lain-Arch systemd[563]: Stopped target Timers.
Jan 01 14:34:11 Lain-Arch systemd-timesyncd[455]: Network configuration changed, trying to establish connection.
Jan 01 14:34:11 Lain-Arch systemd-timesyncd[455]: Using NTP server 216.239.32.15:123 (time1.google.com).
Jan 01 14:34:11 Lain-Arch systemd[563]: Received SIGRTMIN+24 from PID 611 (kill).
Jan 01 14:34:11 Lain-Arch systemd[1]: Unit haveged.service entered failed state.
Jan 01 14:34:11 Lain-Arch systemd[1]: haveged.service failed.
Jan 01 14:34:11 Lain-Arch systemd[1]: Unit dhcpcd.service entered failed state.
Jan 01 14:34:11 Lain-Arch systemd[1]: dhcpcd.service failed.
Jan 01 14:34:11 Lain-Arch login[480]: pam_unix(login:session): session closed for user briggs5
Jan 01 14:34:11 Lain-Arch haveged[468]: haveged: Stopping due to signal 15
Jan 01 14:34:11 Lain-Arch dhcpcd[612]: sending signal TERM to pid 475
Jan 01 14:34:11 Lain-Arch dhcpcd[612]: waiting for pid 475 to exit
Jan 01 14:34:11 Lain-Arch dhcpcd[475]: received signal TERM from PID 612, stopping
Jan 01 14:34:11 Lain-Arch dhcpcd[475]: enp11s0: removing interface
Jan 01 14:34:11 Lain-Arch dhcpcd[475]: eno1: removing interface
Jan 01 14:34:11 Lain-Arch dhcpcd[475]: exited
Jan 01 14:34:11 Lain-Arch systemd[565]: pam_unix(systemd-user:session): session closed for user briggs5
Jan 01 14:34:11 Lain-Arch dhcpcd[612]: dhcpcd[612]: sending signal TERM to pid 475
Jan 01 14:34:11 Lain-Arch dhcpcd[612]: dhcpcd[612]: waiting for pid 475 to exit
Jan 01 14:34:12 Lain-Arch systemd-timesyncd[455]: interval/delta/delay/jitter/drift 512s/-0.013s/0.045s/0.007s/+26ppm (ignored)
Jan 01 14:34:12 Lain-Arch mkinitcpio[610]: ==> Starting build: none
Jan 01 14:34:12 Lain-Arch mkinitcpio[610]: -> Running build hook: [sd-shutdown]
Jan 01 14:34:12 Lain-Arch mkinitcpio[610]: ==> Build complete.
Jan 01 14:34:13 Lain-Arch systemd[1]: Shutting down.
Jan 01 14:34:13 Lain-Arch systemd-journal[233]: Journal stopped
-- Reboot --

oliver · 2015-01-01 21:36:59

nstgc wrote:

~/.i3 exists, but is an empty directory.

If there's no ~/.i3/config then one should be generated for you based on your answers to a few interactive questions. What are the permissions on ~/.i3 ?

Also, your $session in .xinitrc is defaulting to gnome unless you specify i3 or i3wm

Last edited by oliver (2015-01-01 21:37:53)

Head_on_a_Stick · 2015-01-01 21:38:54

Do all the other Window Managers work?

Have you copied the default config file (/etc/i3/config) to your home directory and modified it?

If so, post the contents here.

Can you actually see the mouse pointer during the lock-up or is the screen blank?

nstgc · 2015-01-01 22:10:57

oliver wrote:

nstgc wrote:
~/.i3 exists, but is an empty directory.
If there's no ~/.i3/config then one should be generated for you based on your answers to a few interactive questions. What are the permissions on ~/.i3 ?
Also, your $session in .xinitrc is defaulting to gnome unless you specify i3 or i3wm

It does that lock up thing on first use. The first, and only thing I would see is that it was asking me to either use the default or go through a setup.

[nstgc@computer ~]$ ls -la |grep .i3
drwxr-xr-x 1 nstgc nstgc         12 Jan  1 16:59 .i3

Head_on_a_Stick wrote:

Do all the other Window Managers work?
Have you copied the default config file (/etc/i3/config) to your home directory and modified it?
If so, post the contents here.
Can you actually see the mouse pointer during the lock-up or is the screen blank?

Of those I've tried -- Gnome 3, Enlightenment, KDE, and Openbox -- all work.

I just finished trying to use the default configuration file and this still happened.

# i3 config file (v4)
#
# Please see http://i3wm.org/docs/userguide.html for a complete reference!
#
# This config file uses keycodes (bindsym) and was written for the QWERTY
# layout.
#
# To get a config file with the same key positions, but for your current
# layout, use the i3-config-wizard
#

# Font for window titles. Will also be used by the bar unless a different font
# is used in the bar {} block below.
# 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
# Before i3 v4.8, we used to recommend this one as the default:
# font -misc-fixed-medium-r-normal--13-120-75-75-C-70-iso10646-1
# The font above is very space-efficient, that is, it looks good, sharp and
# clear in small sizes. However, its unicode glyph coverage is limited, the old
# X core fonts rendering does not support right-to-left and this being a bitmap
# font, it doesn’t scale on retina/hidpi displays.

# use these keys for focus, movement, and resize directions when reaching for
# the arrows is not convenient
set $up l
set $down k
set $left j
set $right semicolon

# use Mouse+Mod1 to drag floating windows to their wanted position
floating_modifier Mod1

# start a terminal
bindsym Mod1+Return exec i3-sensible-terminal

# kill focused window
bindsym Mod1+Shift+q kill

# start dmenu (a program launcher)
bindsym Mod1+d exec dmenu_run
# There also is the (new) i3-dmenu-desktop which only displays applications
# shipping a .desktop file. It is a wrapper around dmenu, so you need that
# installed.
# bindsym Mod1+d exec --no-startup-id i3-dmenu-desktop

# change focus
bindsym Mod1+$left focus left
bindsym Mod1+$down focus down
bindsym Mod1+$up focus up
bindsym Mod1+$right focus right

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

# move focused window
bindsym Mod1+Shift+$left move left
bindsym Mod1+Shift+$down move down
bindsym Mod1+Shift+$up move up
bindsym Mod1+Shift+$right move right

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

# split in horizontal orientation
bindsym Mod1+h split h

# split in vertical orientation
bindsym Mod1+v split v

# enter fullscreen mode for the focused container
bindsym Mod1+f fullscreen

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

# toggle tiling / floating
bindsym Mod1+Shift+space floating toggle

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

# focus the parent container
bindsym Mod1+a focus parent

# focus the child container
#bindsym Mod1+d focus child

# move the currently focused window to the scratchpad
bindsym Mod1+Shift+minus move scratchpad

# Show the next scratchpad window or hide the focused scratchpad window.
# If there are multiple scratchpad windows, this command cycles through them.
bindsym Mod1+minus scratchpad show

# switch to workspace
bindsym Mod1+1 workspace 1
bindsym Mod1+2 workspace 2
bindsym Mod1+3 workspace 3
bindsym Mod1+4 workspace 4
bindsym Mod1+5 workspace 5
bindsym Mod1+6 workspace 6
bindsym Mod1+7 workspace 7
bindsym Mod1+8 workspace 8
bindsym Mod1+9 workspace 9
bindsym Mod1+0 workspace 10

# move focused container to workspace
bindsym Mod1+Shift+1 move container to workspace 1
bindsym Mod1+Shift+2 move container to workspace 2
bindsym Mod1+Shift+3 move container to workspace 3
bindsym Mod1+Shift+4 move container to workspace 4
bindsym Mod1+Shift+5 move container to workspace 5
bindsym Mod1+Shift+6 move container to workspace 6
bindsym Mod1+Shift+7 move container to workspace 7
bindsym Mod1+Shift+8 move container to workspace 8
bindsym Mod1+Shift+9 move container to workspace 9
bindsym Mod1+Shift+0 move container to workspace 10

# reload the configuration file
bindsym Mod1+Shift+c reload
# restart i3 inplace (preserves your layout/session, can be used to upgrade i3)
bindsym Mod1+Shift+r restart
# exit i3 (logs you out of your X session)
bindsym Mod1+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 $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

        # 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
        bindsym Return mode "default"
        bindsym Escape mode "default"
}

bindsym Mod1+r mode "resize"

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

#######################################################################
# automatically start i3-config-wizard to offer the user to create a
# keysym-based config which used his favorite modifier (alt or windows)
#
# i3-config-wizard will not launch if there already is a config file
# in ~/.i3/config.
#
# Please remove the following exec line:
#######################################################################
exec i3-config-wizard

I see everything. My mouse is a spinning wait cursor that doesn't move and the clock in the lower right hand corner changes. before copying over the configuration file I would see the initial setup window, but couldn't get past it.

Head_on_a_Stick · 2015-01-01 22:13:06

Have you installed the i3status package?

nstgc · 2015-01-01 22:37:56

Head_on_a_Stick wrote:

Have you installed the i3status package?

Yes

$ pacman -Q |grep i3                                       
dri3proto 1.0-1
i3-wm 4.8-3
i3lock 2.6-1
i3status 2.8-2

[edit] I just tried re-installing with "#pacman -S i3", allowing it to use the default of all three packages in the group -- i3-wm, i3lock, and i3status -- without any change in behavior.

Last edited by nstgc (2015-01-01 22:45:19)

Arch Linux

#1 2015-01-01 19:54:41

i3 consistently fails to accept any user input

#2 2015-01-01 20:09:46

Re: i3 consistently fails to accept any user input

#3 2015-01-01 21:20:59

Re: i3 consistently fails to accept any user input

#4 2015-01-01 21:36:59

Re: i3 consistently fails to accept any user input

#5 2015-01-01 21:38:54

Re: i3 consistently fails to accept any user input

#6 2015-01-01 22:10:57

Re: i3 consistently fails to accept any user input

#7 2015-01-01 22:13:06

Re: i3 consistently fails to accept any user input

#8 2015-01-01 22:37:56

Re: i3 consistently fails to accept any user input

Board footer