- Arch-general - lists.archlinux.org

[arch-general] AUR - Best Practices when Package no longer Supported for Linux upstream but LTS fine?
by David C. Rankin 18 Aug '20

18 Aug '20

Arch devs, Quick AUR question. The virtualbox 5.2 branch is unsupported as of July 2020. Oracle continues to put out testbuilds for 5.2, but currently it does not build with 5.8 (LTS is fine). I am still awaiting answers on the vbox-end-users list as to whether anything compatible will be released either as a testbuild case or as a release (Oracle seems a bit undecided) If 5.2.44 was the last release and there will be no update to support Linux 5.8 -- what do I do with the package? Do I mark it LTS only in some way, or just have it removed? -- David C. Rankin, J.D.,P.E.

2 1

[arch-general] pacman -Syu ~ 1 yr. of packages, tty1 hangs after root clean, tty2 console login OK - how to fix?
by David C. Rankin 15 Aug '20

15 Aug '20

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.

4 9

[arch-general] R: openvpn-client@ takes long time to start
by Riccardo Paolo Bestetti 14 Aug '20

14 Aug '20

Da: Giancarlo Razzolini Inviato: Venerdì, 14 Agosto, 2020 13:29 A: General Discussion about Arch Linux Cc: Riccardo Paolo Bestetti Oggetto: Re: [arch-general] openvpn-client@ takes long time to start Em agosto 14, 2020 3:58 Riccardo Paolo Bestetti via arch-general escreveu: >> After a reboot, the first openvpn-client@ instance I try to start takes almost exactly two minutes to start. The instances before that one start just fine in a few seconds. >> > Guess you meant: "The instances *after* ..." Yes I did. :) >> When that happens, I can see from journalctl that the client actually starts in the first few seconds after the systemctl command. But then, the command doesn't terminate for two more minutes (with no further journal entries). >> > Openvpn has quite good logging capabilities that you can put to use here. The output from OpenVPN indicates that the client is started within the first few seconds from when I give the `systemctl start openvpn-client@whatever` command (see previous email). The tun interface is created, opened, the routes are received and added to the routing table. All the usual stuff. Of course, I can also reach remote hosts through the VPN after that. The exact same thing (& output) happens if I try to start OpenVPN manually from the command line. Minus, of course, the two-minutes wait before the command returns. >> Has anyone seen this before? What could it be? >> > Without knowing more, my first guess is that you still don't have connectivity when that first openvpn client starts. > 2 minutes matches exactly the 120 seconds default ping-restart parameter. So, > what happens is, the client starts, you have > no connectivity then, after two minutes, ping-restart kicks in, and your connection gets through. > So, get a network manager that can properly trigger network-online.target. Or, if your network manager is triggering it, then > it means your network is not quite ready when it does. See above. I also forgot to specify it also happens when the system has been up for hours. It really can't be that the network is not ready. I don't think there's anything much that could be disturbing it. I'm using systemd-networkd for everything + iwd for wireless. Riccardo > Regards, > Giancarlo Razzolini

2 1

[arch-general] openvpn-client@ takes long time to start
by Riccardo Paolo Bestetti 14 Aug '20

14 Aug '20

After a reboot, the first openvpn-client@ instance I try to start takes almost exactly two minutes to start. The instances before that one start just fine in a few seconds. When that happens, I can see from journalctl that the client actually starts in the first few seconds after the systemctl command. But then, the command doesn't terminate for two more minutes (with no further journal entries). Has anyone seen this before? What could it be? Riccardo

2 1

[arch-general] old archlinux instance repositories progress
by Jude DaShiell 13 Aug '20

13 Aug '20

I found and downloaded a current mirrorslist file and selected servers to use. pacman cannot update though and I suspect this is because the necessary ssh keys have to be imported. How is this done using pacman facilities in such a situation? --

4 6

[arch-general] Pros/Cons of Python zipapp packaging
by Daan De Meyer 11 Aug '20

11 Aug '20

Hi, We've been discussing the distribution mechanism for mkosi ( https://github.com/systemd/mkosi) and one of the ideas is using Python zipapp (https://docs.python.org/3/library/zipapp.html) to allow us to split mkosi up into multiple files for easier development without complicating the packaging process. zipapp takes all source files in a directory and bundles them up into a single executable python zip archive so after building the zip you can simply call ./mkosi to run mkosi and can put it anywhere in the PATH to simply run mkosi wherever you want. Are there any issues with this approach from a distro packaging perspective? Zipapp doesn't bundle a specific python version (uses system python and system python stdlib) and we don't intend on bundling any dependencies in the zipapp. I don't think I've ever seen a python application packaged this way which is why I'm asking. Cheers, Daan

4 4

[arch-general] old archlinux cannot now update
by Jude DaShiell 11 Aug '20

11 Aug '20

Is a link in the archwiki on the process to point archlinux at all of the new repositories and import all of the ssh keys? I hadn't been able to access my computers while this move happened so wasn't able to do the necessary steps to change where archlinux finds all of its updates. --

3 3

[arch-general] Estimate on when 5.8 will hit core? - (Virtualbox Still Won't Build)
by David C. Rankin 08 Aug '20

08 Aug '20

Devs, Just a quick check on when 5,8 is going from testing to core? I ask because Virtualbox still is not ready for 5.8: https://www.virtualbox.org/ticket/19644 -- David C. Rankin, J.D.,P.E.

1 0

[arch-general] systemd package: include additional Arch-based boot splash (.bmp) image?
by Anderyos Zaya 31 Jul '20

31 Jul '20

It seems that we have splash-arch.bmp included with Arch Linux systemd package. The included .bmp image is the two-color standard version (arch word in black text). It would be useful to also include the two-color inverted version (for dark backgrounds, also Arch main logo). The .bmp images are useful, for example for setting up boot splash image for people booting with dracut initramfs. Who is the best person to report/talk to regarding this request?

1 0

[arch-general] Anyone having problems refreshing PGP keys lately?
by matthew dyer 23 Jul '20

23 Jul '20

Good morning all, I am wondering if anyone is having problems refreshing PGP keys from the default server? I can force it to use the ipv4 server, but using mate-terminal with orca I am unable to edit the /etc/pacman.d/gnu/pgp.conf file to change the server. Orca will not read it and plume will not open it with sudo rites. Any ideas on this one? This is an older arch vm which will not update till the PGP keys have been updated and imported. I do not have speech in a conc so that would not work. Thanks. Matthew

3 3