[Testing Update] 2019-02-15 - Kernels, Grub, Systemd, Haskell, Python

Linux kernel 4.20.9 is not a good one. You have to jump to 4.20.10!

https://lkml.org/lkml/2019/2/15/162

Neither 4.19.22. You have to jump 4.19.23!

https://lkml.org/lkml/2019/2/15/156

7 Likes

https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.20.10
https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.19.23
https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.101

( revert for all version about shebang string )

Apart from the known systemd-issue (I downgraded to 239.370-1 with live-dvd and chroot) all got well when updating from stable to this. Until you say that next systemd version is working with encrypted /home again, I will hold back the package.

1 Like

can you check this ?

sudo journalctl -b0 | grep -i gvfs-daemon.service

févr. 15 23:41:43 mjro dbus-daemon[715]: [session uid=620 pid=715] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.4' (uid=620 pid=713 comm="/usr/bin/lightdm-gtk-greeter ")
févr. 15 23:41:50 mjro dbus-daemon[785]: [session uid=1000 pid=785] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.9' (uid=1000 pid=811 comm="Thunar --daemon ")
févr. 15 23:42:00 mjro systemd[706]: gvfs-daemon.service: Main process exited, code=killed, status=15/TERM
févr. 15 23:42:00 mjro systemd[706]: gvfs-daemon.service: Succeeded.

On my end updated KDE and systemd (.241) and no problem. Got a warning with grub (stupidly haven’t write it down) but after reboot all well and regenerating grub doesn’t throws any more warnings. Kernel 4.19.xx.

Just tried systemd 241.71-1 on a new VM with an encrypted /home (and only that, the rest is not encrypted), updated from current Stable to current Testing and it didn’t went really good. The upgrade in itself went OK, but at next boot, it fails to mount my /home like others had with 241.0-1.1.

Screenshot

I would suggest to just downgrade to 239.6 again for now (rebuild it if needed) and try again later with more commits.


Potential file conflict(s) related to python-pyqt5 still relevant.

2 Likes

These are just info messages. You can add -p <x> (where <x> is a log level) (see man journalctl) . For me, they don’t appear until -p 5:

[merell@Jammin1 ~]$ journalctl -p 5 -b0 | grep -i gvfs-daemon.service
Feb 15 18:20:17 Jammin1 systemd[1025]: gvfs-daemon.service: Main process exited, code=killed, status=15/TERM

And,

[merell@Jammin1 ~]$ journalctl -p 6 -b0 | grep -i gvfs-daemon.service
Feb 15 18:20:03 Jammin1 dbus-daemon[1049]: [session uid=620 pid=1049] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.5' (uid=620 pid=1032 comm="/usr/bin/lightdm-gtk-greeter ")
Feb 15 18:20:06 Jammin1 dbus-daemon[1197]: [session uid=1000 pid=1197] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.2' (uid=1000 pid=1289 comm="xfce4-session ")
Feb 15 18:20:17 Jammin1 systemd[1025]: gvfs-daemon.service: Main process exited, code=killed, status=15/TERM
Feb 15 18:20:17 Jammin1 systemd[1025]: gvfs-daemon.service: Succeeded.

And, let’s see what we got here:

[merell@Jammin1 ~]$ ps ax|grep gvfs
 1308 ?        Ssl    0:00 /usr/lib/gvfsd
 1313 ?        Sl     0:00 /usr/lib/gvfsd-fuse /run/user/1000/gvfs -f -o big_writes
 1470 ?        Ssl    0:00 /usr/lib/gvfs-udisks2-volume-monitor
 1539 ?        Ssl    0:00 /usr/lib/gvfs-afc-volume-monitor
 1544 ?        Ssl    0:00 /usr/lib/gvfs-gphoto2-volume-monitor
 1548 ?        Ssl    0:00 /usr/lib/gvfs-mtp-volume-monitor
 1561 ?        Sl     0:00 /usr/lib/gvfsd-trash --spawner :1.3 /org/gtk/gvfs/exec_spaw/0
 1569 ?        Ssl    0:00 /usr/lib/gvfsd-metadata
23676 pts/0    S+     0:00 grep --colour=auto gvfs

Successful update on my cinnamon laptop!

I confirm that this update identically breaks my system [LUKS-encrypted /home partition] at the next boot, as did yesterday’s update. Also identically to last night’s rescue, today i recovered my VM by chrooting from LiveISO then downgrading systemd 241.71-1 back to 240.95-2. Tis an exciting ride here, recently :grinning:

This is Arch built (ie remote) not Manjaro built.

The previous Manjaro built testing systemd release was

* 16) systemd-239.303+really+239.6-1-x86_64.pkg.tar.xz (local)

Howeve, if it works for you and no issues then all good.

1 Like

Oh? Golly! It was not my intention to jump from a Manjaro to Arch kernel build WTF? I meant systemd, geez kadee, get a grip. . I picked that one coz in the downgrade options list it showed as “local”, which i interpreted to imply it had previously existed on my system, which in turn a presumed implied it was Manjaro… given i’ve never manually installed any kernel version external to the Manjaro kernel manager tool. So, i really dunno how this happened. *

I’m now going to try another downgrade to “your #16”, & see what happens. Ta.


*Sigh, yes i know how it happened – idiotic inattention on my part. I just rechecked my transcripts from the DG [both yesterday’s & today’s], which CLEARLY say Remote NOT Local. I now have no idea at all how i utterly misread that. Sheesh. :woman_facepalming: Ta again :blush:



Update: It seems to have gone very badly. I’ve not rebooted the VM yet, coz based on the plethora of errors i expect it’s now broken again.

Summary

 ██████████████████  ████████     kdemeoz@ManjaroTestingKDEVM
 ██████████████████  ████████     OS: Manjaro 18.0.2 Illyria
 ██████████████████  ████████     Kernel: x86_64 Linux 4.20.8-1-MANJARO
 ██████████████████  ████████     Uptime: 3h 26m
 ████████            ████████     Packages: 1731
 ████████  ████████  ████████     Shell: bash 5.0.0
 ████████  ████████  ████████     Resolution: 1920x1023
 ████████  ████████  ████████     DE: KDE 5.55.0 / Plasma 5.15.0
 ████████  ████████  ████████     WM: KWin
 ████████  ████████  ████████     GTK Theme: QtCurve [GTK2], Breath-Dark [GTK3]
 ████████  ████████  ████████     Icon Theme: hicolor
 ████████  ████████  ████████     Font: Ubuntu Condensed Regular
 ████████  ████████  ████████     CPU: Intel Core i7-4790 @ 2x 3.6GHz
 ████████  ████████  ████████     GPU: llvmpipe (LLVM 7.0, 256 bits)
                                  RAM: 1418MiB / 12008MiB
[kdemeoz@ManjaroTestingKDEVM ~]$ downgrade systemd
Available packages:

*  1) systemd-241.0-1.1-x86_64.pkg.tar.xz (local)
   2) systemd-241.0-1-x86_64.pkg.tar.xz (remote)
   3) systemd-240.95-2-x86_64.pkg.tar.xz (remote)
   4) systemd-240.95-2-x86_64.pkg.tar.xz (local)
   5) systemd-240.95-1-x86_64.pkg.tar.xz (remote)
   6) systemd-240.93-3-x86_64.pkg.tar.xz (remote)
   7) systemd-240.93-2-x86_64.pkg.tar.xz (remote)
   8) systemd-240.93-1-x86_64.pkg.tar.xz (remote)
   9) systemd-240.34-3-x86_64.pkg.tar.xz (remote)
  10) systemd-240.34-2-x86_64.pkg.tar.xz (remote)
  11) systemd-240.34-1-x86_64.pkg.tar.xz (remote)
  12) systemd-240.0-3-x86_64.pkg.tar.xz (remote)
  13) systemd-240.0-2-x86_64.pkg.tar.xz (remote)
  14) systemd-240.0-1-x86_64.pkg.tar.xz (remote)
* 15) systemd-239.370-2-x86_64.pkg.tar.xz (local)
  16) systemd-239.370-1-x86_64.pkg.tar.xz (remote)
* 17) systemd-239.303+really+239.6-1-x86_64.pkg.tar.xz (local)
* 18) systemd-239.303-1-x86_64.pkg.tar.xz (remote)
* 19) systemd-239.301-1-x86_64.pkg.tar.xz (remote)
  20) systemd-239.300-2-x86_64.pkg.tar.xz (remote)
* 21) systemd-239.300-1-x86_64.pkg.tar.xz (remote)
  22) systemd-239.6-1-x86_64.pkg.tar.xz (remote)
* 23) systemd-239.2-1-x86_64.pkg.tar.xz (remote)
  24) systemd-239.0-2-x86_64.pkg.tar.xz (remote)
  25) systemd-238.133-4-x86_64.pkg.tar.xz (remote)
  26) systemd-238.133-3-x86_64.pkg.tar.xz (remote)
  27) systemd-238.133-2-x86_64.pkg.tar.xz (remote)
* 28) systemd-238.133-1-x86_64.pkg.tar.xz (remote)
* 29) systemd-238.76-1-x86_64.pkg.tar.xz (remote)
  30) systemd-238.51-1-x86_64.pkg.tar.xz (remote)

select a package by number: 17
[sudo] password for kdemeoz: 
loading packages...
warning: downgrading package systemd (240.95-2 => 239.303+really+239.6-1)
resolving dependencies...
looking for conflicting packages...

Packages (1) systemd-239.303+really+239.6-1

Total Installed Size:  19.82 MiB
Net Upgrade Size:      -0.36 MiB

:: Proceed with installation? [Y/n] 
(1/1) checking keys in keyring                                        [#######################################] 100%
(1/1) checking package integrity                                      [#######################################] 100%
(1/1) loading package files                                           [#######################################] 100%
(1/1) checking for file conflicts                                     [#######################################] 100%
(1/1) checking available disk space                                   [#######################################] 100%
:: Processing package changes...
(1/1) downgrading systemd                                             [#######################################] 100%
warning: /etc/systemd/journald.conf installed as /etc/systemd/journald.conf.pacnew
systemd-sysusers: error while loading shared libraries: libidn2.so.4: cannot open shared object file: No such file or directory
journalctl: error while loading shared libraries: libidn2.so.4: cannot open shared object file: No such file or directory
systemctl: error while loading shared libraries: libidn2.so.4: cannot open shared object file: No such file or directory
:: Running post-transaction hooks...
( 1/10) Updating linux414 initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux414.preset: 'default'
  -> -k /boot/vmlinuz-4.14-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.14-x86_64.img
==> Starting build: 4.14.99-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
==> ERROR: binary dependency `libidn2.so.4' not found for `/usr/lib/systemd/systemd-udevd'
==> ERROR: binary dependency `libidn2.so.4' not found for `/usr/bin/udevadm'
==> ERROR: binary dependency `libidn2.so.4' not found for `/usr/bin/systemd-tmpfiles'
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
cannot open file au
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-4.14-x86_64.img
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: /etc/mkinitcpio.d/linux414.preset: 'fallback'
  -> -k /boot/vmlinuz-4.14-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.14-x86_64-fallback.img -S autodetect
==> Starting build: 4.14.99-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
==> ERROR: binary dependency `libidn2.so.4' not found for `/usr/lib/systemd/systemd-udevd'
==> ERROR: binary dependency `libidn2.so.4' not found for `/usr/bin/udevadm'
==> ERROR: binary dependency `libidn2.so.4' not found for `/usr/bin/systemd-tmpfiles'
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
cannot open file au
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-4.14-x86_64-fallback.img
==> WARNING: errors were encountered during the build. The image may not be complete.
error: command failed to execute correctly
( 2/10) Updating linux420 initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux420.preset: 'default'
  -> -k /boot/vmlinuz-4.20-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.20-x86_64.img
==> Starting build: 4.20.8-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
==> ERROR: binary dependency `libidn2.so.4' not found for `/usr/lib/systemd/systemd-udevd'
==> ERROR: binary dependency `libidn2.so.4' not found for `/usr/bin/udevadm'
==> ERROR: binary dependency `libidn2.so.4' not found for `/usr/bin/systemd-tmpfiles'
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
cannot open file au
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-4.20-x86_64.img
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: /etc/mkinitcpio.d/linux420.preset: 'fallback'
  -> -k /boot/vmlinuz-4.20-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.20-x86_64-fallback.img -S autodetect
==> Starting build: 4.20.8-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
==> ERROR: binary dependency `libidn2.so.4' not found for `/usr/lib/systemd/systemd-udevd'
==> ERROR: binary dependency `libidn2.so.4' not found for `/usr/bin/udevadm'
==> ERROR: binary dependency `libidn2.so.4' not found for `/usr/bin/systemd-tmpfiles'
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
cannot open file au
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-4.20-x86_64-fallback.img
==> WARNING: errors were encountered during the build. The image may not be complete.
error: command failed to execute correctly
( 3/10) Updating journal message catalog...
/usr/bin/journalctl: error while loading shared libraries: libidn2.so.4: cannot open shared object file: No such file or directory
error: command failed to execute correctly
( 4/10) Reloading system manager configuration...
/usr/bin/systemctl: error while loading shared libraries: libidn2.so.4: cannot open shared object file: No such file or directory
error: command failed to execute correctly
( 5/10) Updating udev hardware database...
/usr/bin/systemd-hwdb: error while loading shared libraries: libidn2.so.4: cannot open shared object file: No such file or directory
error: command failed to execute correctly
( 6/10) Applying kernel sysctl settings...
/usr/lib/systemd/systemd-sysctl: error while loading shared libraries: libidn2.so.4: cannot open shared object file: No such file or directory
error: command failed to execute correctly
( 7/10) Creating system user accounts...
/usr/bin/systemd-sysusers: error while loading shared libraries: libidn2.so.4: cannot open shared object file: No such file or directory
error: command failed to execute correctly
( 8/10) Creating temporary files...
/usr/bin/systemd-tmpfiles: error while loading shared libraries: libidn2.so.4: cannot open shared object file: No such file or directory
error: command failed to execute correctly
( 9/10) Reloading device manager configuration...
/usr/bin/udevadm: error while loading shared libraries: libidn2.so.4: cannot open shared object file: No such file or directory
error: command failed to execute correctly
(10/10) Arming ConditionNeedsUpdate...
[kdemeoz@ManjaroTestingKDEVM ~]$ 

Indeed, it made the situation even worse.

Somehow, libidn2 went back in the past in term of SOname. Wtf?

[awesome@i56400 ~]$ pacman -Ql libidn2
libidn2 /usr/
libidn2 /usr/bin/
libidn2 /usr/bin/idn2
libidn2 /usr/include/
libidn2 /usr/include/idn2.h
libidn2 /usr/lib/
libidn2 /usr/lib/libidn2.so
libidn2 /usr/lib/libidn2.so.0
libidn2 /usr/lib/libidn2.so.0.3.5
libidn2 /usr/lib/pkgconfig/
libidn2 /usr/lib/pkgconfig/libidn2.pc
libidn2 /usr/share/
[...]

So yeah, it confirms that if @philm wants to downgrade systemd, he’ll have to do a rebuild and not just put the old packages back in repo.

1 Like

Everything went smoothly…in a TTY session, since I got burned the last couple times updating during the x session. Do I vote for the first option or not at all?:thinking: Btw, I have system encryption enabled per Calamares encryption defaults – which includes / and swap but an unencrypted /boot/efi partition.

Again my suggestion of piping all terminal output to a log when updating would probably be helpful in your situation, and also during a TTY session in general. Sometimes we just need more than what’s provided in the pacman.log.

1 Like

Feeling like i’m caught between the proverbial rock & hard place, i’ve now re-run DG & gone back up [slightly] to that Arch version. No errors… so i’m about to timidly reboot it to see if virtual smoke billows outta it.

Summary
[kdemeoz@ManjaroTestingKDEVM ~]$ downgrade systemd
Available packages:

*  1) systemd-241.0-1.1-x86_64.pkg.tar.xz (local)
   2) systemd-241.0-1-x86_64.pkg.tar.xz (remote)
   3) systemd-240.95-2-x86_64.pkg.tar.xz (remote)
   4) systemd-240.95-2-x86_64.pkg.tar.xz (local)
   5) systemd-240.95-1-x86_64.pkg.tar.xz (remote)
   6) systemd-240.93-3-x86_64.pkg.tar.xz (remote)
   7) systemd-240.93-2-x86_64.pkg.tar.xz (remote)
   8) systemd-240.93-1-x86_64.pkg.tar.xz (remote)
   9) systemd-240.34-3-x86_64.pkg.tar.xz (remote)
  10) systemd-240.34-2-x86_64.pkg.tar.xz (remote)
  11) systemd-240.34-1-x86_64.pkg.tar.xz (remote)
  12) systemd-240.0-3-x86_64.pkg.tar.xz (remote)
  13) systemd-240.0-2-x86_64.pkg.tar.xz (remote)
  14) systemd-240.0-1-x86_64.pkg.tar.xz (remote)
* 15) systemd-239.370-2-x86_64.pkg.tar.xz (local)
  16) systemd-239.370-1-x86_64.pkg.tar.xz (remote)
* 17) systemd-239.303+really+239.6-1-x86_64.pkg.tar.xz (local)
* 18) systemd-239.303-1-x86_64.pkg.tar.xz (remote)
* 19) systemd-239.301-1-x86_64.pkg.tar.xz (remote)
  20) systemd-239.300-2-x86_64.pkg.tar.xz (remote)
* 21) systemd-239.300-1-x86_64.pkg.tar.xz (remote)
  22) systemd-239.6-1-x86_64.pkg.tar.xz (remote)
* 23) systemd-239.2-1-x86_64.pkg.tar.xz (remote)
  24) systemd-239.0-2-x86_64.pkg.tar.xz (remote)
  25) systemd-238.133-4-x86_64.pkg.tar.xz (remote)
  26) systemd-238.133-3-x86_64.pkg.tar.xz (remote)
  27) systemd-238.133-2-x86_64.pkg.tar.xz (remote)
* 28) systemd-238.133-1-x86_64.pkg.tar.xz (remote)
* 29) systemd-238.76-1-x86_64.pkg.tar.xz (remote)
  30) systemd-238.51-1-x86_64.pkg.tar.xz (remote)

select a package by number: 4
[sudo] password for kdemeoz: 
loading packages...
resolving dependencies...
looking for conflicting packages...

Packages (1) systemd-240.95-2

Total Installed Size:  20.17 MiB
Net Upgrade Size:       0.36 MiB

:: Proceed with installation? [Y/n] 
(1/1) checking keys in keyring                                        [#######################################] 100%
(1/1) checking package integrity                                      [#######################################] 100%
(1/1) loading package files                                           [#######################################] 100%
(1/1) checking for file conflicts                                     [#######################################] 100%
(1/1) checking available disk space                                   [#######################################] 100%
:: Processing package changes...
(1/1) upgrading systemd                                               [#######################################] 100%
warning: /etc/systemd/journald.conf installed as /etc/systemd/journald.conf.pacnew
:: Running post-transaction hooks...
( 1/10) Updating linux414 initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux414.preset: 'default'
  -> -k /boot/vmlinuz-4.14-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.14-x86_64.img
==> Starting build: 4.14.99-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
cannot open file au
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-4.14-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux414.preset: 'fallback'
  -> -k /boot/vmlinuz-4.14-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.14-x86_64-fallback.img -S autodetect
==> Starting build: 4.14.99-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
cannot open file au
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-4.14-x86_64-fallback.img
==> Image generation successful
( 2/10) Updating linux420 initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux420.preset: 'default'
  -> -k /boot/vmlinuz-4.20-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.20-x86_64.img
==> Starting build: 4.20.8-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
cannot open file au
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-4.20-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux420.preset: 'fallback'
  -> -k /boot/vmlinuz-4.20-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.20-x86_64-fallback.img -S autodetect
==> Starting build: 4.20.8-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
cannot open file au
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-4.20-x86_64-fallback.img
==> Image generation successful
( 3/10) Updating journal message catalog...
( 4/10) Reloading system manager configuration...
( 5/10) Updating udev hardware database...
( 6/10) Applying kernel sysctl settings...
( 7/10) Creating system user accounts...
( 8/10) Creating temporary files...
( 9/10) Reloading device manager configuration...
(10/10) Arming ConditionNeedsUpdate...
[kdemeoz@ManjaroTestingKDEVM ~]$ 


Edit: No billowing smoke; it rebooted ok. Dodged the asteroid this time, but given i’m now inadvertently running an Arch not Manjaro systemd, i wonder what imminent booby-trap lies in wait…

LOL, deja vu … you just recreated the same issue that borked others last aborted systemd update.

** TWILIGHT ZONE MUSIC **

If it works use it, regardless of who built it.

Systemd in Manjaro is currently a mess, if an Arch build works just stick with it until an upstream 241 cryptsetup patch eventuates. Even then may be better to stick with Arch systemd builds going forward as Manjaro’s seem perpetually buggy.

2 Likes

You took the wrong systemd version when downgrading. The only one that works is:
systemd-239.303+really+239.6-1-x86_64.pkg.tar.xz

On my system, everything is still ok with systemd241.71:

 ██████████████████  ████████     bs86@BS86-PC
 ██████████████████  ████████     OS: Manjaro 18.0.2 Illyria
 ██████████████████  ████████     Kernel: x86_64 Linux 4.20.10-1-ck1-MANJARO
 ██████████████████  ████████     Uptime: 8m
 ████████            ████████     Packages: 1534
 ████████  ████████  ████████     Shell: bash 5.0.0
 ████████  ████████  ████████     Resolution: 5120x1440
 ████████  ████████  ████████     DE: KDE 5.55.0 / Plasma 5.15.0
 ████████  ████████  ████████     WM: KWin
 ████████  ████████  ████████     GTK Theme: Adapta-Breath [GTK2/3]
 ████████  ████████  ████████     Icon Theme: Papirus-Adapta-Maia
 ████████  ████████  ████████     Font: Noto Sans Regular
 ████████  ████████  ████████     CPU: AMD Ryzen 7 2700X Eight-Core @ 16x 3.7GHz
 ████████  ████████  ████████     GPU: Radeon RX Vega (VEGA10, DRM 3.27.0, 4.20.10-1-ck1-MANJARO, LLVM 7.0.1)
                                  RAM: 3148MiB / 32163MiB

Indeed, this is the one I referenced too … that explains the issues, however if they Arch build works just stick with it in the short term.

Full encrypted installation with systemd241.71-1 Kernel: x86_64 Linux 4.20.9-1-MANJARO
update went just fine.

The systemd log issue with plenty of messages like

Feb 15 07:16:38 manjaro systemd-udevd[217]: /usr/lib/udev/rules.d/50-udev-default.rules:20: Invalid GROUP operation

is fixed in systemd:master:

Closed #11720 via #11726.

3 Likes

A note/remark:
Whatever was introduced/modified in the linux420 and linux419 kernels, makes the wacom tablet not only to connect/disconnect (as before), but once is again manually disconnected and connected, the mapping goes off with an internal error, rendering the tablet unusable. I didn’t had much time to play around, it works in linux414 with no issue.
Later i will post more findings about it.

UPDATE:
Issue solved by

:hugs::smiling_face_with_three_hearts: