- Arch-general - lists.archlinux.org

[arch-general] netcl leaves network down until reenable performed - do we need note?
by David C. Rankin 21 Aug '20

21 Aug '20

Archdevs, I have two computers using netctl, one for a static and one for a dhcp address. After the last update on May, 3, netctl (1.22-1 -> 1.23-1) all remained fine and old profiles generated as subservices in /etc/systemd/system, such as: netctl\(a)rlf_network\\x2dstatic.service continued to bring the network up. However within the past week there was a change, likely to systemd 246, that no longer respects the subservices originally created by netctl. Now attempting at reboot causes the network to fail completely. Not good for remotely adminned boxes. What is required is a "reenable" of the netctl profile. Doing so will remove the old subservice and symlinks and replace then with a directory in /etc/systemd/system of same name as the old subservice, but with a ".d" appended that now contains a "profile.conf", e.g. netctl(a)rlf_network\x2dstatic.service.d/ └── profile.conf However, there is no note or warning during update that any manual intervention will be needed. That will leave anyone adminning a remote arch install with netctl with a box that is unreachable and has no network. Shouldn't there be a warning about this change generated on update? Arch is always pretty good about warning when manual interaction is required -- and this is a biggie. Couldn't there also be a post install that does a reenable for each netctl profile found in /etc/systemd/system as another option to avoid this SNAFU? -- David C. Rankin, J.D.,P.E.

4 5

[arch-general] Gaetan Bisson Resignation
by Amin Vakil 20 Aug '20

20 Aug '20

Hello, I'm not an Arch Linux Developer myself, so I'm not allowed to reply to this email on arch-dev-public. But just out of curiosity and to learn something, would you care to share with us what majority's views is in conflict with your views? Best Regards, Amin Vakil On 8/20/20 3:13 AM, Gaetan Bisson via arch-dev-public wrote: > Dear all, > > I've joined the Arch team in 2010 and spent a decade as a developer; > it's been a great privilege to be a part of such an awesome community > and also a lot of fun. However I felt the ten-year mark was a good > opportunity for me to move on since I recognize the majority's views on > the future of the distro have of late steadily been diverging from mine. > > And thus I hereby resign my position of Arch Linux Developer. > > All the best in your future endeavors! >

2 1

[arch-general] Does PAM 1.4.0 require rebuilding all application / modules using libpam?
by Amish 20 Aug '20

20 Aug '20

Hello, I have few packages (eg. pam_geoip, pam_abl) in custom repo which use libpam. Can someone clarify if PAM upgrade to 1.4.0 would require those packages to be rebuilt? I have few systems using those PAM modules and if those modules break after updating and rebooting then I will lose access to the system. And I do not want to end up in that situation. Since I haven't seen mass-rebuilt of other modules (like pam-krb5, pam_mount etc.), I think rebuild is not required. But would still like if some developer can confirm before I upgrade. Thank you, Amish.

2 1

[arch-general] pam-1.3.1-2 -> 1.4.0-3 breaking change
by Damjan Georgievski 19 Aug '20

19 Aug '20

it seems the 1.4.0-3 removed the tally/tally2 modules and (for some reason) I had `auth required pam_tally2.so` in /etc/pam.d/system-login. Of course that broke the login and I had to rescue the installation from a bootable USB. I wonder if there can be some pam-lint tool that checks your /etc/pam.d/ after upgrades. -- damjan

1 0

Re: [arch-general] HP Laserjet plus 1020 Problem
by das 19 Aug '20

19 Aug '20

Dear friend Karx asked me to try to print something and then give the differences in the three files in /var/log/cups. I tried to print one page from Libreoffice Writer and here is the result of running diff for the old and new versions of the three files for the three files. For access_log the difference is: 186,195d185 < localhost - - [19/Aug/2020:20:10:02 +0530] "POST /printers/HP-LaserJet-1020 HTTP/1.1" 200 215 Create-Job successful-ok < localhost - - [19/Aug/2020:20:10:02 +0530] "POST /printers/HP-LaserJet-1020 HTTP/1.1" 200 29704 Send-Document successful-ok < localhost - - [19/Aug/2020:20:10:24 +0530] "POST /jobs/ HTTP/1.1" 200 151 Cancel-Job client-error-not-found < localhost - - [19/Aug/2020:20:10:24 +0530] "POST /jobs/ HTTP/1.1" 200 151 Cancel-Job client-error-not-found < localhost - - [19/Aug/2020:20:10:24 +0530] "POST /jobs/ HTTP/1.1" 200 151 Cancel-Job client-error-not-found < localhost - - [19/Aug/2020:20:10:24 +0530] "POST /jobs/ HTTP/1.1" 200 151 Cancel-Job client-error-not-found < localhost - - [19/Aug/2020:20:10:24 +0530] "POST /jobs/ HTTP/1.1" 200 151 Cancel-Job client-error-not-found < localhost - - [19/Aug/2020:20:10:24 +0530] "POST /jobs/ HTTP/1.1" 200 151 Cancel-Job client-error-not-found < localhost - - [19/Aug/2020:20:10:24 +0530] "POST /jobs/ HTTP/1.1" 200 151 Cancel-Job client-error-not-found < localhost - - [19/Aug/2020:20:10:24 +0530] "POST /jobs/ HTTP/1.1" 200 151 Cancel-Job client-error-not-found ----------------------------------------------------------------------------------------------- error_log -- no difference ------------------------------------------------------------------------------------------------------ page_log -- no difference

2 1

[arch-general] HP Laserjet plus 1020 Problem
by das 19 Aug '20

19 Aug '20

Dear Friends My new printer HP Laserjet plus 1020 is not working on Arch Linux, while it is working fine on the second boot Debian system. I have tried all the ways that came to my mind or all the suggestions from the Net. It is not working. Can any of you suggest anything? With Regards Dipankar Das -- দাশ das http://ddts.randomink.org/

2 1

[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