[Not solved][Sudo/X] Enter key not released after typing password

n0rv · 2014-08-07 20:11:29

After upgrade to xserver 1.16 I noticed strange thing - any command I try to run with sudo "hangs" keyboard and mouse. It looks like after typing password and pressing <Enter>, this key is not released.
System is still responsive, for example I can watch youtube, listen to music, there is no high cpu usage, but inputs are blocked.
For example:

sudoedit /etc/whateverrc

opens editor and cursor goes down.

This is not a problem with my keyboard
In tty sudo works fine.

Last edited by n0rv (2014-08-09 19:45:28)

jasonwryan · 2014-08-07 20:45:52

How do you start X? What DE/WM? What is in your journal/logs?

Moving to NC...

n0rv · 2014-08-07 21:30:31

jasonwryan wrote:

How do you start X?

startx

What DE/WM?

AwesomeWM, quite old setup.

What is in your journal/logs?

After "hang" X still works, so I need to kill it (alt+sysrq+re) or reboot.

Xorg.log.0.old

[  5770.071] (II) RADEON(0): Modeline "1680x1050"x0.0  119.00  1680 1728 1760 1840  1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
[  5770.071] (II) RADEON(0): Modeline "1920x1080"x60.0  172.80  1920 2040 2248 2576  1080 1081 1084 1118 -hsync +vsync (67.1 kHz e)
[  5770.110] (II) systemd-logind: got resume for 13:68
[  5770.110] (II) systemd-logind: got resume for 13:67
[  5770.126] (II) systemd-logind: got resume for 13:64
[  5770.156] (II) systemd-logind: got resume for 13:65
[  5770.209] (II) systemd-logind: got resume for 13:66
[  5885.135] (II) systemd-logind: got pause for 226:0
[  5885.135] (II) systemd-logind: got pause for 13:68
[  5885.135] (II) systemd-logind: got pause for 13:67
[  5885.135] (II) systemd-logind: got pause for 13:64
[  5885.135] (II) systemd-logind: got pause for 13:65
[  5885.135] (II) systemd-logind: got pause for 13:66
[  5893.481] (II) evdev:   USB Keyboard: Close
[  5893.481] (II) UnloadModule: "evdev"
[  5893.481] (II) systemd-logind: releasing fd for 13:66
[  5893.481] (EE) systemd-logind: failed to release device: Connection is closed
[  5893.481] (II) evdev:   USB Keyboard: Close
[  5893.481] (II) UnloadModule: "evdev"
[  5893.481] (II) systemd-logind: releasing fd for 13:65
[  5893.481] (EE) systemd-logind: failed to release device: Connection is closed
[  5893.481] (II) evdev: A4Tech PS/2+USB Mouse: Close
[  5893.481] (II) UnloadModule: "evdev"
[  5893.481] (II) systemd-logind: releasing fd for 13:64
[  5893.481] (EE) systemd-logind: failed to release device: Connection is closed
[  5893.481] (II) evdev: Power Button: Close
[  5893.481] (II) UnloadModule: "evdev"
[  5893.481] (II) systemd-logind: releasing fd for 13:67
[  5893.481] (EE) systemd-logind: failed to release device: Connection is closed
[  5893.481] (II) evdev: Power Button: Close
[  5893.481] (II) UnloadModule: "evdev"
[  5893.481] (II) systemd-logind: releasing fd for 13:68
[  5893.481] (EE) systemd-logind: failed to release device: Connection is closed
[  5893.560] (WW) xf86CloseConsole: KDSETMODE failed: Input/output error
[  5893.560] (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error
[  5893.560] (EE) 
Fatal server error:
[  5893.560] (EE) xf86CloseConsole: VT_ACTIVATE failed: Input/output error
[  5893.560] (EE) 
[  5893.560] (EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[  5893.560] (EE) Please also check the log file at "/home/n0rv/.local/share/xorg/Xorg.0.log" for additional information.
[  5893.560] (EE) 
[  5893.560] (EE) 
[  5893.560] (EE) Backtrace:
[  5893.613] (EE) 0: /usr/bin/Xorg.bin (xorg_backtrace+0x56) [0x593966]
[  5893.614] (EE) 1: /usr/bin/Xorg.bin (0x400000+0x197b69) [0x597b69]
[  5893.614] (EE) 2: /usr/lib/libc.so.6 (0x7f5912809000+0x33df0) [0x7f591283cdf0]
[  5893.614] (EE) 
[  5893.614] (EE) Segmentation fault at address 0x0
[  5893.614] (EE) 
FatalError re-entered, aborting
[  5893.614] (EE) Caught signal 11 (Segmentation fault). Server aborting
[  5893.614] (EE)

journalctl:

sie 07 23:15:12 Arch sudo[3368]: n0rv : TTY=pts/1 ; PWD=/home/n0rv ; USER=root ; COMMAND=sudoedit /etc/yaourtrc
sie 07 23:15:12 Arch sudoedit[3368]: pam_unix(sudo:session): session opened for user root by (uid=0)
sie 07 23:15:12 Arch systemd[1]: Starting user-0.slice.
sie 07 23:15:12 Arch systemd[1]: Created slice user-0.slice.
sie 07 23:15:12 Arch systemd[1]: Starting User Manager for UID 0...
sie 07 23:15:12 Arch systemd[3372]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
sie 07 23:15:12 Arch systemd-logind[1230]: New session c2 of user root.
sie 07 23:15:12 Arch systemd[1]: Starting Session c2 of user root.
sie 07 23:15:12 Arch systemd[1]: Started Session c2 of user root.
sie 07 23:15:12 Arch systemd[3372]: Starting -.slice.
sie 07 23:15:12 Arch systemd[3372]: Created slice -.slice.
sie 07 23:15:12 Arch systemd[3372]: Starting D-Bus Message Bus Socket.
sie 07 23:15:12 Arch systemd[3372]: Listening on D-Bus Message Bus Socket.
sie 07 23:15:12 Arch systemd[3372]: Starting Paths.
sie 07 23:15:12 Arch systemd[3372]: Reached target Paths.
sie 07 23:15:12 Arch systemd[3372]: Starting Timers.
sie 07 23:15:12 Arch systemd[3372]: Reached target Timers.
sie 07 23:15:12 Arch systemd[3372]: Starting Sockets.
sie 07 23:15:12 Arch systemd[3372]: Reached target Sockets.
sie 07 23:15:12 Arch systemd[3372]: Starting Basic System.
sie 07 23:15:12 Arch systemd[3372]: Reached target Basic System.
sie 07 23:15:12 Arch systemd[3372]: Starting Default.
sie 07 23:15:12 Arch systemd[3372]: Reached target Default.
sie 07 23:15:12 Arch systemd[3372]: Startup finished in 7ms.
sie 07 23:15:12 Arch systemd[1]: Started User Manager for UID 0.
sie 07 23:15:20 Arch kernel: SysRq : Keyboard mode set to system default
sie 07 23:15:20 Arch systemd-journal[1227]: Journal stopped
sie 07 23:15:21 Arch systemd-journal[3399]: Permanent journal is using 131.6M (max allowed 100.0M, trying to leave 2.9G free of 6.0G available → current limit 131.6M).
sie 07 23:15:21 Arch kernel: SysRq : Terminate All Tasks
sie 07 23:15:21 Arch systemd-journald[1227]: Received SIGTERM.
sie 07 23:15:21 Arch systemd[1]: getty@tty2.service has no holdoff time, scheduling restart.

jasonwryan · 2014-08-07 21:40:39

Is your session active? And something is going on there with your journal size: I'd fix that.

n0rv · 2014-08-07 21:49:27

This is how it looks, if you think I'm joking or something...
https://dl.dropboxusercontent.com/u/3837977/output.mkv

After typing password and press <Enter> X still works, but I can't use keyboard or mouse (except alt+sysrq+reisub).

Last edited by n0rv (2014-08-07 21:50:01)

jasonwryan · 2014-08-07 21:54:04

I don't think your joking... But rather than making videos of the problem, shouldn't you be trying to fix it by attending to the other broken stuff and ruling out possible contributing factors?

n0rv · 2014-08-07 22:46:29

And something is going on there with your journal size: I'd fix that.

Fixed.

$ journalctl --disk-usage
Journals take up 81.6M on disk.

Is your session active?

After keyboard "hangs"? I'm not sure how to check that. It looks like active, because X does not freeze or crash.

jasonwryan · 2014-08-07 22:48:29

https://wiki.archlinux.org/index.php/Ge … ermissions

n0rv · 2014-08-08 00:15:55

After "hang" session is not active:

Id=c1
Name=n0rv
Timestamp=pią 2014-08-08 00:59:42 CEST
TimestampMonotonic=1743948149
VTNr=1
TTY=tty1
Remote=no
Service=login
Scope=session-c1.scope
Leader=18498
Audit=0
Type=tty
Class=user
Active=no
State=online
IdleHint=no
IdleSinceHint=1407452384163298
IdleSinceHintMonotonic=1745676057

According to your link: X runs on the same tty where the login occurred, DBus daemon is running, polkit authentication agent looks like running, but I'm not sure it's really needed. Sudo works in tty AND in WM, because I can do that:

$ sudo touch test.txt

now it "hangs", I need to kill X, but file is created:

$ la test.txt
-rw-r--r-- 1 root root 0 08-08 01:39 test.txt

I changed terminal emulator to roxterm and sudo works properly. It works also with urxvt, but not with urxvtc.
Finally, the reason for broken sudo was lack of -f option in my urxvtd.service file. It should look like this: https://wiki.archlinux.org/index.php/rx … gh_systemd

Strange, but it works now. Thanks for help.

Last edited by n0rv (2014-08-08 00:18:05)

jasonwryan · 2014-08-08 00:17:28

Please remember to mark your thread as [Solved] by editing your first post and prepending it to the title.

n0rv · 2014-08-09 18:51:44

Unfortunately, it's not solved.

The problem seems to occur only when I use sudo in urxvtc and when urxvtd daemon is running by systemd (in this way: https://wiki.archlinux.org/index.php/rx … gh_systemd).
If urxvtd will be launched manually, problem seems to not occur.

Journal contains only this:

$ journalctl --unit=urxvtd@n0rv.service -b
-- Logs begin at śro 2014-01-01 22:21:01 CET, end at sob 2014-08-09 20:42:24 CEST. --
sie 09 20:25:52 Arch systemd[1]: Starting RXVT-Unicode Daemon...
sie 09 20:25:52 Arch systemd[1]: Started RXVT-Unicode Daemon.
sie 09 20:26:14 Arch sudo[11365]: n0rv : a password is required ; TTY=pts/1 ; PWD=/home/n0rv ; USER=root ; COMMAND=list /usr/bin/pacman --color auto -Sy
sie 09 20:26:16 Arch sudo[11367]: n0rv : TTY=pts/1 ; PWD=/home/n0rv ; USER=root ; COMMAND=validate
sie 09 20:26:16 Arch sudo[11368]: n0rv : TTY=pts/1 ; PWD=/home/n0rv ; USER=root ; COMMAND=list /usr/bin/pacman --color auto -Sy
sie 09 20:26:16 Arch sudo[11369]: n0rv : TTY=pts/1 ; PWD=/home/n0rv ; USER=root ; COMMAND=/usr/bin/pacman --color auto -Sy
sie 09 20:26:16 Arch sudo[11369]: pam_unix(sudo:session): session opened for user root by (uid=0)

Can anyone reproduce and confirm this?

Last edited by n0rv (2014-08-09 18:53:30)

sinopeus · 2015-02-22 23:25:58

I have had the same problem, only I'm using Gentoo (we only the 1.16 upgrade past week). I'm a bit stumped, just put urxvtd back into xinitrc and on we go.

mkoskar · 2015-02-23 01:36:12

n0rv wrote:

The problem seems to occur only when I use sudo in urxvtc and when urxvtd daemon is running by systemd).

So do you run it as system or user service? Have you tried to run it as user service and include complete .profile for sake of testing?
For completeness you can do something like following (I know it's not systemd, but it works well):

$ cat ~/bin/urxvtc
#!/bin/bash

export RXVT_SOCKET="$HOME/.urxvt/urxvtd-$DISPLAY"

/usr/bin/urxvtc "$@"
if [ $? -eq 2 ]; then
    urxvtd -q -o -f
    /usr/bin/urxvtc "$@"
fi

Also just when on it, I've resignated on "urxvtd" since it would just crash all my terminals with increasingly frequency. I use tmux extensively and really have only 3-4 terminals opened so I use just "urxvt" now.

Arch Linux

#1 2014-08-07 20:11:29

[Not solved][Sudo/X] Enter key not released after typing password

#2 2014-08-07 20:45:52

Re: [Not solved][Sudo/X] Enter key not released after typing password

#3 2014-08-07 21:30:31

Re: [Not solved][Sudo/X] Enter key not released after typing password

#4 2014-08-07 21:40:39

Re: [Not solved][Sudo/X] Enter key not released after typing password

#5 2014-08-07 21:49:27

Re: [Not solved][Sudo/X] Enter key not released after typing password

#6 2014-08-07 21:54:04

Re: [Not solved][Sudo/X] Enter key not released after typing password

#7 2014-08-07 22:46:29

Re: [Not solved][Sudo/X] Enter key not released after typing password

#8 2014-08-07 22:48:29

Re: [Not solved][Sudo/X] Enter key not released after typing password

#9 2014-08-08 00:15:55

Re: [Not solved][Sudo/X] Enter key not released after typing password

#10 2014-08-08 00:17:28

Re: [Not solved][Sudo/X] Enter key not released after typing password

#11 2014-08-09 18:51:44

Re: [Not solved][Sudo/X] Enter key not released after typing password

#12 2015-02-22 23:25:58

Re: [Not solved][Sudo/X] Enter key not released after typing password

#13 2015-02-23 01:36:12

Re: [Not solved][Sudo/X] Enter key not released after typing password

Board footer