[arch-general] pacman -Syu ~ 1 yr. of packages, tty1 hangs after root clean, tty2 console login OK - how to fix?
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, 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? -- David C. Rankin, J.D.,P.E.
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
On 8/10/20 10:10 PM, Eli Schwartz via arch-general wrote:
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)
Thank you Eli, Well, to be honest, I knew pacman had been updated and I thought rebooting would fix it :) -- Oh well, maybe not.... pacman is fully updated now, right? So if I take that list and go back and try re-running the hooks -- that may be one way to fix it? Worse come to worse, I'll just wipe /root and reinstall... So for my edification -- what happened was after update, the new pacman was installed along with the new hooks, but since the pacman I ran the update from was too old, it croaked trying to run the new hooks from the updated pacman? Will we give it a go. -- David C. Rankin, J.D.,P.E.
On 8/10/20 11:25 PM, David C. Rankin wrote:
On 8/10/20 10:10 PM, Eli Schwartz via arch-general wrote:
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)
Thank you Eli,
Well, to be honest, I knew pacman had been updated and I thought rebooting would fix it :) -- Oh well, maybe not....
pacman is fully updated now, right? So if I take that list and go back and try re-running the hooks -- that may be one way to fix it? Worse come to worse, I'll just wipe /root and reinstall...
Depends on the hook. Some of them use NeedsTargets, so the Exec command needs to receive the list of triggering files on stdin. Reinstalling all currently installed packages would have the same effect, no need to wipe anything. If you have the list of packages which were updated at that time, you could just update them alone. Otherwise it might take a bit of fiddling to ensure every hook runs correctly.
So for my edification -- what happened was after update, the new pacman was installed along with the new hooks, but since the pacman I ran the update from was too old, it croaked trying to run the new hooks from the updated pacman?
Will we give it a go.
Correct. Again, using https://aur.archlinux.org/packages/pacman-static#pinned-666894 renders this concern irrelevant since you'd end up running the most recent pacman in order to perform the update and run hooks. -- Eli Schwartz Bug Wrangler and Trusted User
On 8/10/20 11:00 PM, Eli Schwartz via arch-general wrote:
pacman is fully updated now, right? So if I take that list and go back and try re-running the hooks -- that may be one way to fix it? Worse come to worse, I'll just wipe /root and reinstall... Depends on the hook. Some of them use NeedsTargets, so the Exec command needs to receive the list of triggering files on stdin.
Reinstalling all currently installed packages would have the same effect, no need to wipe anything. If you have the list of packages which were updated at that time, you could just update them alone.
Otherwise it might take a bit of fiddling to ensure every hook runs correctly.
So for my edification -- what happened was after update, the new pacman was installed along with the new hooks, but since the pacman I ran the update from was too old, it croaked trying to run the new hooks from the updated pacman?
Will we give it a go. Correct.
Again, using https://aur.archlinux.org/packages/pacman-static#pinned-666894 renders this concern irrelevant since you'd end up running the most recent pacman in order to perform the update and run hooks.
Well... I booted, and reinstalled all 1568 files and all 28 hooks ran successfully: # cd /var/cache/pacman/pkg # pacman -U $(find . -type f -newermt 20190627 -printf " %f) Everything completed successfully, all dkms drivers rebuilt for 5.7.12, all appears to be working fine -- except the network and the boot hangs at the exact same place on tty1, but login is fine on tty2, sddm is started, but there is no graphical display. I wonder if the network is causing the hang with boot on tty1. When I manually try and restart the wireless card, I get: Aug 14 00:38:46 seidr systemd[1]: /etc/systemd/system/netctl@wlo1_wireless_skyline.service:1: Assignment outside of section. Ignoring. Aug 14 00:41:34 seidr systemd[1]: Starting (Re)store the netctl profile state... Aug 14 00:41:35 seidr netctl[553]: Could not read state file '/var/lib/netctl/netctl.state' Aug 14 00:41:35 seidr systemd[1]: Finished (Re)store the netctl profile state. The service file is the same as it has been: # cat /etc/systemd/system/netctl@wlo1_wireless_skyline.service .include /usr/lib/systemd/system/netctl@.service [Unit] Description=A wpa_supplicant configuration file based wireless connection BindsTo=sys-subsystem-net-devices-wlo1.device After=sys-subsystem-net-devices-wlo1.device I have no clue what this assignment outside of section is telling me. I haven't changed the wireless config at all. Any idea on this or the boot hang issue? What to check? -- David C. Rankin, J.D.,P.E.
On 8/14/20 1:04 AM, David C. Rankin wrote:
I have no clue what this assignment outside of section is telling me. I haven't changed the wireless config at all. Any idea on this or the boot hang issue? What to check?
I fixed the netctl issue. It seems the netctl interface with systemd changed and the normal subsystem service file has been turned into a service.d directory containing 'profile' files. A reenable of the profile removed the old symlinks and service file and replaced them with the service.d directory using # netctl reenable the_profile Network is up and happy again. Additionally, I've done a completely additional reinstall: # pacman -Qqn | pacman -S - All goes well, no errors, but the boot still hangs on tty1 and no GUI or X is every started though sddm says it is running. I think it is time to wipe the slate clean and reinstall unless anyone has a better idea? The original install was from 2016 so it was a bit old, but still working well before the ill-fated update. -- David C. Rankin, J.D.,P.E.
On 8/14/20 3:18 AM, David C. Rankin wrote:
Additionally, I've done a completely additional reinstall:
# pacman -Qqn | pacman -S -
All goes well, no errors, but the boot still hangs on tty1 and no GUI or X is every started though sddm says it is running.
I think it is time to wipe the slate clean and reinstall unless anyone has a better idea?
GAH!!!! The original reinstall would have solved everything -- but for Arch removing the nvidia-390xx packages, WTF?? There were no new ones there so the 390.116 packages installed on my Laptop were never updated causing boot to hang. That is a shame. You just can't pull a videocard out of your i7 laptop to update for fun, and you sure can't run desktop effects in KDE without it. I'm not sure I understand the logic in Arch dropping the 390xx drivers relegating a host of laptops Quadro cards to trying to build the nvidia-390xx, the utils and settings package. Even following the list, I don't recall a discussion about the discontinuation and there was no warning on update or error on reinstall. But, it is done, and aside from the netctl SNAFU and the nvidia surprise, the update from 6/19 to 8/20 worked just fine -- which is pretty amazing. -- David C. Rankin, J.D.,P.E.
Am 15.08.20 um 09:57 schrieb David C. Rankin:
... That is a shame. You just can't pull a videocard out of your i7 laptop to update for fun, and you sure can't run desktop effects in KDE without it. I'm not sure I understand the logic in Arch dropping the 390xx drivers relegating a host of laptops Quadro cards to trying to build the nvidia-390xx, the utils and settings package. Even following the list, I don't recall a discussion about the discontinuation and there was no warning on update or error on reinstall.
It was mentioned on arch-dev-public: https://lists.archlinux.org/pipermail/arch-dev-public/2020-March/029895.html There were no maintainers that were able to test the legacy nvidia packages anymore, so they had to be dropped. Unofficial binary packages are available in the disastrousaur[1] and jlk[2] repositories. The AUR package is mostly repackaging the upstream binaries anyways, only the kernel module is built from source. So I don't think it would be too bad to install it from the AUR. [1]: https://wiki.archlinux.org/index.php/Unofficial_user_repositories#disastrous... [2]: https://wiki.archlinux.org/index.php/Unofficial_user_repositories#jlk -- ProgAndy
On 8/15/20 3:07 AM, ProgAndy wrote:
It was mentioned on arch-dev-public:
https://lists.archlinux.org/pipermail/arch-dev-public/2020-March/029895.html
There were no maintainers that were able to test the legacy nvidia packages anymore, so they had to be dropped.
Unofficial binary packages are available in the disastrousaur[1] and jlk[2] repositories. The AUR package is mostly repackaging the upstream binaries anyways, only the kernel module is built from source. So I don't think it would be too bad to install it from the AUR.
[1]: https://wiki.archlinux.org/index.php/Unofficial_user_repositories#disastrous...
[2]: https://wiki.archlinux.org/index.php/Unofficial_user_repositories#jlk
Thank you, Yes, when you build the nvidia-390xx from AUR you have the option of installing nvidia-390xx or nvidia-390xx-dkms which is as you explain handles the rebuild of the kernel modules. My only concern there, as with the 5.2 branch of VirtualBox I package for AUR, builds break on kernel update. The vbox 5.2.45 (testbuild 139677) still fails to build the kernel modules for 5.8. If something like that were to happen with the nvidia driver, then you would simply break X on all affected laptops until the AUR maintainer could update the package. AUR is good, but it certainly is no where near as reliable as having a maintained package for critical drivers. Moreover, with vbox, your guest may be offline until an update is provided, but your computer still works. With graphics driver -- you are not as lucky. I'm sure the testing could have been arranged to preserve the 390xx driver -- I would have been more than happy to do it. We will see how it goes, but I'm not going to update to 5.8 and roll the dice yet. -- David C. Rankin, J.D.,P.E.
On 11.08.2020 05:25, David C. Rankin wrote:
On 8/10/20 10:10 PM, Eli Schwartz via arch-general wrote:
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)
Thank you Eli,
Well, to be honest, I knew pacman had been updated and I thought rebooting would fix it :) -- Oh well, maybe not....
pacman is fully updated now, right? So if I take that list and go back and try re-running the hooks -- that may be one way to fix it? Worse come to worse, I'll just wipe /root and reinstall...
I had the same problem too (but I did not reboot). I just reinstalled all packages using this: https://wiki.archlinux.org/index.php/Pacman/Tips_and_tricks#Reinstalling_all... I did it on all my servers without problems. Regards, Łukasz
participants (4)
-
David C. Rankin
-
Eli Schwartz
-
ProgAndy
-
Łukasz Michalski