pacman crashes session silently following some installs

vibeisveryo · 2023-04-21 06:23:52

http://ix.io/4tTW <- journal from executing

sudo pacman -S steam

http://ix.io/4tTY <- pacman log

info:
- running lightdm as display manager
- i3wm
- alacritty terminal emulator
- let me know if you need anything else, not too terribly familiar with what could be useful info here

With several different pacman installs (reproduced several times with steam), during or after the post-installation hooks (when I try to install it afterward, it shows as already installed) the session crashes and i'm returned (all of my other windows closing as well) to lightdm.

This happens even on command-line only TTY2 - it returns me to lightdm, but does not log me out of the session there unlike the graphical reproduction.

This is a new Arch install from today, and this problem has never happened to me before - even with this same hardware. Any info I can provide, how could I fix this?

seth · 2023-04-21 07:20:42

It's probably '30-systemd-udev-reload.hook' and possibly related to https://bugs.archlinux.org/task/77789

sudo /usr/share/libalpm/scripts/systemd-hook udev-reload

kicks you out of the session as well?

vibeisveryo · 2023-04-21 13:27:40

seth wrote:

sudo /usr/share/libalpm/scripts/systemd-hook udev-reload
kicks you out of the session as well?

Doesn't seem to, no.

seth · 2023-04-21 14:25:17

Seems like the only hook triggered everytime, though.

Kick yourself out of the session w/ pacman and post the (old) lightdm and Xorg logs (in /var/log/*) you get in return.

Edit: steam installs /usr/lib/udev/rules.d/70-steam-input.rules and /usr/lib/udev/rules.d/70-steam-vr.rules (what triggers the hook)
You could also try to touch those (to update their timestamps) and then run the hook command that so far failed to kick you.

Last edited by seth (2023-04-21 14:27:03)

vibeisveryo · 2023-04-27 03:29:52

Actually, tried doing the hook command again and it did kick me out this time. Weird.

http://ix.io/4umP old Xorg log

http://ix.io/4umQ lightdm.log

http://ix.io/4umS lightdm.log.old

seth · 2023-04-27 06:49:29

[  8907.311] (II) Server terminated successfully (0). Closing log file.

That server exited deliberately, so the session process died.

[+4.94s] DEBUG: Session pid=19653: Running command /etc/lightdm/Xsession i3-with-shmlog
…
[+181.09s] DEBUG: Session pid=19653: Exited with return value 129

seems to be the troublemaker.

Is i3-with-shmlog already to invedtigate?
How's the behavior for i3-withoutanythingshm?
What do the i3 logs say after the incident (and before re-starting i3)?

Naught · 2023-04-29 15:06:21

I am also getting this. Reinstalling the steam package crashes my Xorg server.

Here is the output:

[   115.736] (EE) Backtrace:
 17 [   115.738] (EE) 0: /usr/lib/Xorg (dri3_send_open_reply+0xdd) [0x5608eaefd9dd]
 18 [   115.739] (EE) 1: /usr/lib/libc.so.6 (__sigaction+0x50) [0x7f34c6826f50]
 19 [   115.739] (EE) unw_get_proc_name failed: no unwind info found [-10]
 20 [   115.739] (EE) 2: /usr/lib/xorg/modules/input/libinput_drv.so (?+0x0) [0x7f34c5e1ce8c]
 21 [   115.739] (EE) 3: /usr/lib/Xorg (DisableDevice+0xb88) [0x5608eae121d8]
 22 [   115.739] (EE) 4: /usr/lib/Xorg (RemoveDevice+0x211) [0x5608eae125e1]
 23 [   115.739] (EE) 5: /usr/lib/Xorg (DeleteInputDeviceRequest+0x49) [0x5608eaf237e9]
 24 [   115.740] (EE) 6: /usr/lib/Xorg (config_init+0x207) [0x5608eaf78467]
 25 [   115.740] (EE) 7: /usr/lib/Xorg (config_init+0x478) [0x5608eaf786d8]
 26 [   115.740] (EE) 8: /usr/lib/Xorg (UnlockServer+0x282) [0x5608eaef58c2]
 27 [   115.740] (EE) 9: /usr/lib/Xorg (WaitForSomething+0x1c9) [0x5608eaef0ec9]
 28 [   115.740] (EE) 10: /usr/lib/Xorg (SProcXkbDispatch+0x1c93) [0x5608eade036f]
 29 [   115.741] (EE) 11: /usr/lib/libc.so.6 (__libc_init_first+0x90) [0x7f34c6811790]
 30 [   115.741] (EE) 12: /usr/lib/libc.so.6 (__libc_start_main+0x8a) [0x7f34c681184a]
 31 [   115.741] (EE) 13: /usr/lib/Xorg (_start+0x25) [0x5608eade12b5]
 32 [   115.741] (EE)
 33 [   115.741] (EE) Segmentation fault at address 0x80
 34 [   115.741] (EE)
 35 Fatal server error:
 36 [   115.741] (EE) Caught signal 11 (Segmentation fault). Server aborting
 37 [   115.741] (EE)
 38 [   115.741] (EE)
 39 Please consult the The X.Org Foundation support
 40          at http://wiki.x.org
 41  for help.

seth · 2023-04-29 15:08:28

Very likely hook and bug in #2 - what's your systemd version?

Naught · 2023-04-29 15:11:43

seth wrote:

Very likely hook and bug in #2 - what's your systemd version?

systemd 253 (253.3-3-arch)

seth · 2023-04-29 15:30:08

There're supposed to have been fixes around that, but apparently not.

You can try to comment /usr/share/libalpm/scripts/systemd-hook

     47     /usr/bin/systemctl daemon-reload
     48     ;;
     49   udev-reload)
     50     udevd_live
     51     /usr/bin/udevadm control --reload
     52     # /usr/bin/udevadm trigger
     53     # /usr/bin/udevadm settle
     54     ;;
     55   binfmt)
     56     systemd_live

as workaround.

V1del · 2023-04-29 22:47:02

Likely same cause as https://bbs.archlinux.org/viewtopic.php?id=285369 and a bogus evdev referencing conf file flying about

seth · 2023-04-30 06:05:18

At least the OP has no evdev in their xorg log (but a bogus nvidia-xconfig generated xorg.conf)

V1del · 2023-04-30 15:47:07

Stack trace looks similar enough though and also complaining about deleting some input device

seth · 2023-04-30 16:01:03

"Naught" isn't the OP, we lack a trace from "vibeisveryo" and it seems more the i3 session than X11

Naught · 2023-04-30 20:14:16

seth wrote:

"Naught" isn't the OP, we lack a trace from "vibeisveryo" and it seems more the i3 session than X11

Is there something wrong with my Xorg config? Should I change it?

Here is the full Xorg log with the 'pacman -S' steam crash.

https://termbin.com/p2kr

Last edited by Naught (2023-04-30 20:15:03)

seth · 2023-04-30 20:15:59

[    10.302] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[    10.302] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[    10.302] (**) Power Button: Applying InputClass "system-keyboard"
[    10.302] (II) LoadModule: "evdev"
[    10.302] (WW) Warning, couldn't open module evdev
[    10.302] (EE) Failed to load module "evdev" (module does not exist, 0)
[    10.302] (EE) No input driver matching `evdev'

See the link in #11

Naught · 2023-04-30 20:25:54

That worked. Thanks.

I had an old evdev config lying around but don't have the package installed.

seth · 2023-04-30 20:27:47

Posts #7 and following should probably be split off, the OP must have a different problem.

2shrestha22 · 2023-06-20 17:09:27

Installing `xf86-input-evdev` solved my issue. Source: https://www.reddit.com/r/archlinux/comm … ion_kicks/

V1del · 2023-06-20 19:00:53

You generally want to remove that and remove the config files that are still referencing it erroneously.

Arch Linux

#1 2023-04-21 06:23:52

pacman crashes session silently following some installs

#2 2023-04-21 07:20:42

Re: pacman crashes session silently following some installs

#3 2023-04-21 13:27:40

Re: pacman crashes session silently following some installs

#4 2023-04-21 14:25:17

Re: pacman crashes session silently following some installs

#5 2023-04-27 03:29:52

Re: pacman crashes session silently following some installs

#6 2023-04-27 06:49:29

Re: pacman crashes session silently following some installs

#7 2023-04-29 15:06:21

Re: pacman crashes session silently following some installs

#8 2023-04-29 15:08:28

Re: pacman crashes session silently following some installs

#9 2023-04-29 15:11:43

Re: pacman crashes session silently following some installs

#10 2023-04-29 15:30:08

Re: pacman crashes session silently following some installs

#11 2023-04-29 22:47:02

Re: pacman crashes session silently following some installs

#12 2023-04-30 06:05:18

Re: pacman crashes session silently following some installs

#13 2023-04-30 15:47:07

Re: pacman crashes session silently following some installs

#14 2023-04-30 16:01:03

Re: pacman crashes session silently following some installs

#15 2023-04-30 20:14:16

Re: pacman crashes session silently following some installs

#16 2023-04-30 20:15:59

Re: pacman crashes session silently following some installs

#17 2023-04-30 20:25:54

Re: pacman crashes session silently following some installs

#18 2023-04-30 20:27:47

Re: pacman crashes session silently following some installs

#19 2023-06-20 17:09:27

Re: pacman crashes session silently following some installs

#20 2023-06-20 19:00:53

Re: pacman crashes session silently following some installs

Board footer