I have been experiencing an issue whilst running eos-update that seems to have started 2/3 months ago, in that I suddenly get logged out before the updates complete. Twice now this has resulted in a failure to complete a kernel update, causing the system to not boot.
Although I have so far been able to fix this using arch-chroot, I would like to find out what is causing this as there doesn’t seem to be any mention of errors in the pacman log, nor have I noticed any messages or warnings despite watching the update carefully. Everything appears to be proceeding normally and then suddenly I’m back at the login screen.
Good suggestion but it’s turned off along with similar timeouts. I also forgot to mention that the logouts are random, it doesn’t happen every time, and I have done many updates successfully, including kernel updates.
I was wondering if it was a resource issue, but though I have plenty of free disk space and ram, I guess it could be something that’s causing a sudden demand at times, though I’ve only been logged out whilst running eos-update?
I don’t use eos-update so I have no idea. I just know many desktops have a time out for the screen unless you disable it. However sounds like that is not the issue so good luck. Maybe @manuel can be of much better assistance
Thanks, I thought I had checked the logs, but must have been asleep to miss the big reg coredump! Here is the part of the log from the start of eos-update to the dump:
`Jul 17 21:06:26 Acer-Nitro systemd[2074]: Started [systemd-run] /usr/bin/bash -c "echo '==> eos-update --aur'; eos-update --aur; eos-sleep-counter 60".`
`Jul 17 21:06:31 Acer-Nitro systemd[2074]: app-gnome-firefox-5359.scope: Consumed 1h 34min 22.311s CPU time over 12h 37min 40.393s wall clock time, 3.7G memory peak.`
`Jul 17 21:06:33 Acer-Nitro sudo[51456]: remoulder : TTY=pts/0 ; PWD=/home/remoulder ; USER=root ; COMMAND=/usr/bin/rm -f /var/lib/pacman/db.lck`
`Jul 17 21:06:33 Acer-Nitro sudo[51456]: pam_unix(sudo:session): session opened for user root(uid=0) by remoulder(uid=1000)`
`Jul 17 21:06:33 Acer-Nitro sudo[51456]: pam_unix(sudo:session): session closed for user root`
`Jul 17 21:06:33 Acer-Nitro sudo[51471]: remoulder : TTY=pts/0 ; PWD=/home/remoulder ; USER=root ; COMMAND=/usr/bin/pacman -Sy`
`Jul 17 21:06:33 Acer-Nitro sudo[51471]: pam_unix(sudo:session): session opened for user root(uid=0) by remoulder(uid=1000)`
`Jul 17 21:06:34 Acer-Nitro sudo[51471]: pam_unix(sudo:session): session closed for user root`
`Jul 17 21:06:34 Acer-Nitro sudo[51492]: remoulder : TTY=pts/0 ; PWD=/home/remoulder ; USER=root ; COMMAND=/usr/bin/pacman -Su`
`Jul 17 21:06:34 Acer-Nitro sudo[51492]: pam_unix(sudo:session): session opened for user root(uid=0) by remoulder(uid=1000)`
`Jul 17 21:06:51 Acer-Nitro systemd[1]: systemd-timedated.service: Deactivated successfully.`
`Jul 17 21:07:09 Acer-Nitro dbus-broker-launch[619]: Noticed file-system modification, trigger reload.`
`Jul 17 21:07:09 Acer-Nitro gnome-shell[2234]: Error checking authorization for action id org.freedesktop.NetworkManager.network-control: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.freedesktop.NetworkManager.network-control is not registered`
`Jul 17 21:07:09 Acer-Nitro dbus-broker-launch[619]: Noticed file-system modification, trigger reload.`
`Jul 17 21:07:18 Acer-Nitro systemd[1]: Reload requested from client PID 51661 ('systemctl') (unit user@1000.service)...`
`Jul 17 21:07:18 Acer-Nitro systemd[1]: Reloading...`
`Jul 17 21:07:18 Acer-Nitro systemd[1]: Reloading finished in 431 ms.`
`a0=5 a1=7ffc9e4b61f0 a2=a8 a3=0 items=0 ppid=0 pid=1 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="systemd" exe="/usr/lib/systemd/systemd" key=(null)`
`a0=f4 a1=0 a2=0 a3=0 items=0 ppid=0 pid=1 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="systemd" exe="/usr/lib/systemd/systemd" key=(null)`
`Jul 17 21:07:19 Acer-Nitro systemd[1]: Queuing reload/restart jobs for marked units…`
`Jul 17 21:07:19 Acer-Nitro systemd-logind[629]: Watching system buttons on /dev/input/event2 (Lid Switch)`
`Jul 17 21:07:19 Acer-Nitro systemd[2074]: Reached target Bluetooth.`
`Jul 17 21:07:19 Acer-Nitro systemd-logind[629]: Watching system buttons on /dev/input/event0 (Power Button)`
`Jul 17 21:07:19 Acer-Nitro systemd-logind[629]: Watching system buttons on /dev/input/event3 (Power Button)`
`Jul 17 21:07:19 Acer-Nitro systemd-logind[629]: Watching system buttons on /dev/input/event1 (Sleep Button)`
`Jul 17 21:07:19 Acer-Nitro systemd-logind[629]: Watching system buttons on /dev/input/event4 (AT Translated Set 2 keyboard)`
`Jul 17 21:07:19 Acer-Nitro systemd-logind[629]: Watching system buttons on /dev/input/event11 (Acer WMI hotkeys)`
`Jul 17 21:07:20 Acer-Nitro kernel: amdgpu 0000:01:00.0: [drm] PCIE GART of 256M enabled (table at 0x000000F400000000).`
`Jul 17 21:07:20 Acer-Nitro kernel: rtsx_pci 0000:02:00.0: VPD access failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update`
`Jul 17 21:07:20 Acer-Nitro kernel: amdgpu 0000:01:00.0: [drm] UVD and UVD ENC initialized successfully.`
`Jul 17 21:07:20 Acer-Nitro kernel: amdgpu 0000:01:00.0: [drm] VCE initialized successfully.`
`Jul 17 21:07:20 Acer-Nitro gnome-shell[2234]: Failed to reopen '/dev/dri/card1': GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Permission denied`
`Jul 17 21:07:20 Acer-Nitro gnome-shell[2234]: g_hash_table_iter_init: assertion 'hash_table != NULL' failed`
`Jul 17 21:07:20 Acer-Nitro systemd-coredump[51873]: Process 2234 (gnome-shell) of user 1000 terminated abnormally with signal 11/SEGV, processing...`
`Jul 17 21:07:20 Acer-Nitro systemd[1]: Created slice Slice /system/systemd-coredump.`
`Jul 17 21:07:20 Acer-Nitro systemd[1]: Started Process Core Dump (PID 51873/UID 0).`
Thanks, there are some entries elsewhere in the log relating to gnome shell, so I’ll look at those in more detail but likely a problem extension? I find it strange that this only happens during the eos-update though as my laptop is usually on all day and it hasn’t happened at any other time?
I don’t think it’s a password, but maybe something corrupted somewhere? Seems not to be caused by the update anyway, though for some reason that does seem to be the trigger? Guess I’ll have to investigate more deeply and close this thread.