[Testing Update] 2019-02-14 - Kernels, Systemd, Browsers, Calamares, Firmware, Plasma5, KDE Framework

update
testing

#81

Link?


#82

…versus my VM:

25/11/17: Created today from “manjaro-kde-17.0.6-stable-x86_64.iso”.
NB This VM has LUKS-encrypted Swap & Home partitions, hence CANNOT be successfully Cloned.


#83

All my VMs are encrypted and I clone them all the time, easier than installing from scratch when I’m doing certain types of testing.


#84

Ta muchly - over dinner i was thinking of trying exactly that, but i got paralysed with indecision about all the other packages i might then also need to remember to include in my downgrade…?


#85

I did the only downgrade of systemd to the 240.95-2 version without doing the downgrade of any dependency and I was lucky :slight_smile:


#86

I replied to my first posting which shows the link:


#87

…and… she’s ba-ack!

Summary

Thanks so much! :champagne:

Done in the chroot before rebooting VM:

Summary
[root@manjaro /]# 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-1-x86_64.pkg.tar.xz (remote)                                                    
   5) systemd-240.93-3-x86_64.pkg.tar.xz (remote)                                                    
   6) systemd-240.93-2-x86_64.pkg.tar.xz (remote)                                                    
   7) systemd-240.93-1-x86_64.pkg.tar.xz (remote)                                                    
   8) systemd-240.34-3-x86_64.pkg.tar.xz (remote)                                                    
   9) systemd-240.34-2-x86_64.pkg.tar.xz (remote)                                                    
  10) systemd-240.34-1-x86_64.pkg.tar.xz (remote)                                                    
  11) systemd-240.0-3-x86_64.pkg.tar.xz (remote)                                                                                                                                                                 
  12) systemd-240.0-2-x86_64.pkg.tar.xz (remote)                                                                                                                                                                 
  13) systemd-240.0-1-x86_64.pkg.tar.xz (remote)                                                                                                                                                                 
* 14) systemd-239.370-2-x86_64.pkg.tar.xz (local)                                                                                                                                                                                          
  15) systemd-239.370-1-x86_64.pkg.tar.xz (remote)                                                                                                                                                                                         
* 16) systemd-239.303+really+239.6-1-x86_64.pkg.tar.xz (local)
* 17) systemd-239.303-1-x86_64.pkg.tar.xz (remote)
* 18) systemd-239.301-1-x86_64.pkg.tar.xz (remote)
  19) systemd-239.300-2-x86_64.pkg.tar.xz (remote)
* 20) systemd-239.300-1-x86_64.pkg.tar.xz (remote)
  21) systemd-239.6-1-x86_64.pkg.tar.xz (remote)
* 22) systemd-239.2-1-x86_64.pkg.tar.xz (remote)
  23) systemd-239.0-2-x86_64.pkg.tar.xz (remote)
  24) systemd-238.133-4-x86_64.pkg.tar.xz (remote)
  25) systemd-238.133-3-x86_64.pkg.tar.xz (remote)
  26) systemd-238.133-2-x86_64.pkg.tar.xz (remote)
* 27) systemd-238.133-1-x86_64.pkg.tar.xz (remote)
* 28) systemd-238.76-1-x86_64.pkg.tar.xz (remote)
  29) systemd-238.51-1-x86_64.pkg.tar.xz (remote)
  30) systemd-238.0-3-x86_64.pkg.tar.xz (remote)

select a package by number: 3
 systemd-240.95-2-x86_64                 4.5 MiB  1248K/s 00:04 [###################################] 100%
 systemd-240.95-2-x86_64.sig           325.0   B  0.00B/s 00:00 [###################################] 100%
loading packages...
warning: downgrading package systemd (241.0-1.1 => 240.95-2)
resolving dependencies...
looking for conflicting packages...

Packages (1) systemd-240.95-2

Total Installed Size:  20.17 MiB
Net Upgrade Size:      -0.57 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%
Running in chroot, ignoring request: daemon-reexec
:: 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...
Running in chroot, ignoring request: daemon-reload
( 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...
add systemd to IgnorePkg? [y/n] y
[root@manjaro /]# 

#88

I am having an issue when connectiong to vpn using openconnect.

Got CONNECT response: HTTP/1.1 200 OK
CSTP connected. DPD 30, Keepalive 20
Connected as 10.175.41.62, using SSL, with DTLS in progress
Established DTLS connection (using GnuTLS). Ciphersuite (DTLS0.9)-(DHE-CUSTOM)-(AES-256-CBC)-(SHA1).
Unit dbus-org.freedesktop.resolve1.service not found.
Unit dbus-org.freedesktop.resolve1.service not found.

And all the resolving of targets behind the vpn fail.

It actually seems like one an older issue https://bugs.archlinux.org/task/54796 as any action with systemd-resolve fails, see below.
$ sudo systemd-resolve status
status: resolve call failed: Unit dbus-org.freedesktop.resolve1.service not found.

I will try to fix it the same way as is suggested in the issue above.


#89

This file is supposed to be linked by systemctl when systemd-resolved.service is enabled which for some reason has disappeared after the update?

So the solution is to sudo systemctl enable systemd-resolved.


#90

Ok, gotta eat my word - not everythings great for me. Luks (full disk) on the T450s worked… but will hardly suspend to ram, and wont wake up to more than a frozen Lockscreen (gnome) not even the mouse is moving, nor any input is registered -.-


#91

I reported now upstream in regard of systemd-cryptsetup changes made since v241-rc2:


#92

I don’t think it’s only KDE. As I wrote I’m with i3/xfce and think it’s the same problem I have.


#93

The reason why philm mentioned KDE is that he built a KDE ISO just for this update.


#94

libsystemd renamed to systemd-lib? Also I’m on unstable but there’s no announcement over there. But it seems like testing and unstable got the same stuff… Should I hit Y and go ahead?


#95

O.K. Sorry. I don’t want to stress anyone. I only thought that someone could narrow the troubleshooting too much on the KDE-branch and missing the point that way.


#96

Ok it looks like they confirmed the bug! They added it to the v242 milestone. https://github.com/systemd/systemd/issues/11723


#97

Yes, accept the replacement.

We failed, or upstream failed? That’s the question.
(Well, they marked it as a bug, so they acknowledge something went wrong on their side.)

But, yeah, it looks Manjaro will have to stick with 239 for a while. With all the new stuff that we got, is a rebuild necessary for Stable?


#98

Unstable will keep getting systemd RC???

I like unstable cause it feels very “archy”, small updates you know . I thought the repo would be like arch stable, but not even arch is on systemd 241.

Update to 241 was fine for me, system running smooth as always.

PS: i think the forum should have a unstable report section, maybe someone with encrypted /home could have spotted the bug while was still on RC. Just a suggestion, maybe testing is enough.


#99

Applied this update yesterday before the ones from today. Only issue I ran into with this update was a conflicting file:

conflicting files:
python-pyqt5: /usr/lib/python3.7/site-packages/PyQt5/__pycache__/__init__.cpython-37.pyc already exists in filesystem

No other issues. Updated via Pamac GUI on kernel 4.19.

System specs Thinkpad W540
DE: Xfce4
WM: Compiz
CPU: Intel Core i7-4900MQ @ 8x 3.8GHz
GPU: Quadro K1100M
RAM: 3265MiB / 31796MiB

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

Yup, many people reported it a few days ago.