On 8/10/20 10:58 PM, David C. Rankin wrote: > All, > > I was updating an arch install on a platter drive for my laptop that had not > been updated since June 2019. The update was uneventful, only dependency issue > was lib86xxdga a dependency for mplayer that was installed as a dependency of > ogmrip. So, before update I uninstalled ogmrip, mplayer and dependencies that > removed the issue. > > Update of 1568 packages proceeded normally, until the post-install hooks > started to run. A /usr/share/libalpm/hooks path problem occurred. The > following is the output from pacman: > > ... > (1568/1568) upgrading zsh > [########################################] 100% > error: hook /usr/share/libalpm/hooks/30-systemd-tmpfiles.hook line 2: invalid > value Path > error: hook /usr/share/libalpm/hooks/20-systemd-sysusers.hook line 2: invalid > value Path > error: hook /usr/share/libalpm/hooks/70-dkms-install.hook line 4: invalid > value Path > error: hook /usr/share/libalpm/hooks/glib-compile-schemas.hook line 2: invalid > value Path > error: hook /usr/share/libalpm/hooks/gtk-update-icon-cache.hook line 2: > invalid value Path > error: hook /usr/share/libalpm/hooks/update-desktop-database.hook line 2: > invalid value Path > error: hook /usr/share/libalpm/hooks/dconf-update.hook line 2: invalid value Path > error: hook /usr/share/libalpm/hooks/30-systemd-catalog.hook line 2: invalid > value Path > error: hook /usr/share/libalpm/hooks/30-systemd-update.hook line 2: invalid > value Path > error: hook /usr/share/libalpm/hooks/detect-old-perl-modules.hook line 4: > invalid value Path > error: hook /usr/share/libalpm/hooks/texinfo-remove.hook line 2: invalid value > Path > error: hook /usr/share/libalpm/hooks/30-systemd-udev-reload.hook line 2: > invalid value Path > error: hook /usr/share/libalpm/hooks/update-appstream-cache.hook line 2: > invalid value Path > error: hook /usr/share/libalpm/hooks/dbus-reload.hook line 2: invalid value Path > error: hook /usr/share/libalpm/hooks/update-vlc-plugin-cache.hook line 2: > invalid value Path > error: hook /usr/share/libalpm/hooks/30-systemd-sysctl.hook line 2: invalid > value Path > error: hook /usr/share/libalpm/hooks/70-dkms-upgrade.hook line 3: invalid > value Path > error: hook /usr/share/libalpm/hooks/fontconfig.hook line 2: invalid value Path > error: hook /usr/share/libalpm/hooks/30-systemd-binfmt.hook line 2: invalid > value Path > error: hook /usr/share/libalpm/hooks/gio-querymodules.hook line 2: invalid > value Path > error: hook /usr/share/libalpm/hooks/vimdoc.hook line 5: invalid value Path > error: hook /usr/share/libalpm/hooks/xorg-mkfontscale.hook line 2: invalid > value Path > error: hook /usr/share/libalpm/hooks/texinfo-install.hook line 2: invalid > value Path > error: hook /usr/share/libalpm/hooks/30-systemd-daemon-reload.hook line 2: > invalid value Path > error: hook /usr/share/libalpm/hooks/gdk-pixbuf-query-loaders.hook line 2: > invalid value Path > error: hook /usr/share/libalpm/hooks/gtk-query-immodules-2.0.hook line 2: > invalid value Path > error: hook /usr/share/libalpm/hooks/40-update-ca-trust.hook line 5: invalid > value Path > error: hook /usr/share/libalpm/hooks/30-systemd-hwdb.hook line 2: invalid > value Path > error: hook /usr/share/libalpm/hooks/update-mime-database.hook line 2: invalid > value Path > error: hook /usr/share/libalpm/hooks/gtk-query-immodules-3.0.hook line 2: > invalid value Path > error: hook /usr/share/libalpm/hooks/71-dkms-remove.hook line 3: invalid value > Path > :: Running post-transaction hooks... > (1/3) Updating module dependencies... > (2/3) Restarting cronie for libc upgrade... > (3/3) Updating linux initcpios... > > Now when I attempt to boot, After that many errors, why did you try rebooting without fixing things first? The obvious first step is to try rerunning all of those hooks using a modern pacman. (Do not do a year's worth of updates in one go like that, it's not tested and might break. It is preferred instead to do incremental updates via https://wiki.archlinux.org/index.php/Arch_Linux_Archive in e.g. monthly increments, but if you insist on doing the whole thing in one shot then at least use the latest version of pacman via my pacman-static binaries, or the install media + pacman --sysroot /mnt -Syu) > it shows systemd 246.1 and then "root clean ..." > and then tty1 appears to hang, no network is started and for all practical > purposes it just appears to be hung. "Alt + ->" switches to tty2 and the > normal login prompt is displayed and I can login just fine, su to root, and > the system appears to be working (but without any network and attempting to > restart the netctl service for wireless fails) > > The journal shows /boot and /home mounted fine and systemd started and > targets Multi-User and Graphical reached and sddm start and Startup finishes: > > Aug 10 17:11:28 seidr systemd[1]: Reached target Multi-User System. > Aug 10 17:11:28 seidr dbus-daemon[481]: [system] Activating via systemd: service > ... > Aug 10 17:11:28 seidr systemd[1]: Reached target Graphical Interface. > ... > Aug 10 17:11:29 seidr sddm[486]: Initializing... > Aug 10 17:11:29 seidr sddm[486]: Starting... > Aug 10 17:11:29 seidr sddm[486]: Logind interface found > ... > Aug 10 17:11:29 seidr systemd[1]: Startup finished in 6.449s (kernel) + > 13.784s (userspace) = 20.233s. > > There seem to be problems with kde .desktop files, but the system tries to > proceed: > > Aug 10 17:13:20 seidr systemd[500]: /etc/xdg/autostart/org.kde.kgpg.desktop:8: > Unknown key name 'MimeType' in section 'Desktop Entry', ignoring. > Aug 10 17:13:20 seidr systemd[500]: > /etc/xdg/autostart/kmix_autostart.desktop:6: Unknown key name 'MimeType' in > section 'Desktop Entry', ignoring. > Aug 10 17:13:20 seidr systemd[500]: Configuration file > /etc/xdg/autostart/klipper.desktop is marked executable. Please remove > executable permission bits. Proceeding anyway. > Aug 10 17:13:20 seidr systemd[500]: kde-systemd-start-condition not found: No > such file or directory > Aug 10 17:13:20 seidr systemd[500]: kde-systemd-start-condition not found: No > such file or directory > Aug 10 17:13:20 seidr systemd[500]: kde-systemd-start-condition not found: No > such file or directory > Aug 10 17:13:20 seidr systemd[500]: Not generating service for XDG autostart > app-at\x2dspi\x2ddbus\x2dbus-autostart.service, startup phases are not supported. > Aug 10 17:13:20 seidr systemd[500]: kde-systemd-start-condition not found: No > such file or directory > Aug 10 17:13:20 seidr systemd[500]: kde-systemd-start-condition not found: No > such file or directory > Aug 10 17:13:20 seidr systemd[500]: kde-systemd-start-condition not found: No > such file or directory > Aug 10 17:13:20 seidr systemd[500]: Not generating service for XDG autostart > app-kaccess-autostart.service, only Type=Application is supported. > Aug 10 17:13:20 seidr systemd[500]: kde-systemd-start-condition not found: No > such file or directory > Aug 10 17:13:20 seidr systemd[500]: Not generating service for XDG autostart > app-pulseaudio-autostart.service, startup phases are not supported. > Aug 10 17:13:20 seidr systemd[500]: Not generating service for XDG autostart > app-powerdevil-autostart.service, only Type=Application is supported. > Aug 10 17:13:20 seidr systemd[500]: kde-systemd-start-condition not found: No > such file or directory > Aug 10 17:13:20 seidr systemd[495]: Queued start job for default target Main > User Target. > Aug 10 17:13:20 seidr systemd[495]: Reached target Paths. > Aug 10 17:13:20 seidr systemd[495]: Reached target Timers. > > But tty1 is still hung -- no display manager is loaded and I'm stuck on > tty2. I'm not sure what is stuck or what to kill to try and fix it. Before the > update sddm was fine and I loaded fluxbox to do the update rather than doing > it from within KDE. What do I check to try and bring the system back to a > working state? What to check? > -- Eli Schwartz Bug Wrangler and Trusted User
Attachment:
signature.asc
Description: OpenPGP digital signature
