[Stable Update] 2020-08-28 - Kernels, Systemd, PAM, PAMBASE, KDE-git, Deepin, Pamac, Nvidia 450.66, LibreOffice 7.0

All went fine on my main machine via TYY update, GNOME, 5.4 Kernel

Keep up the good work!

Did you try with replacing it with pamac-tray-icon-plasma package?

that is strange. does xrdp still uses tally by any chance? @RBX


Hmm, this is strange. Can you use a Manjaro install media and chroot into it? Then you may downgrade pam and pambase:

sudo pacman -U https://archive.archlinux.org/packages/p/pam/pam-1.3.1-2-x86_64.pkg.tar.xz https://archive.archlinux.org/packages/p/pambase/pambase-20190105.1-2-any.pkg.tar.xz

4 Likes

In my case, akonadi stopped working - unable to start mysql properly. Got it running with

sudo apparmor_parser -R /etc/apparmor.d/usr.bin.akonadiserver

For some reason mariadb wasn’t able to read my (user side) mysql.conf file under ~/.local/share/akonadi after the update…

Updated on Manjaro KDE. Nvidia 450 is still unusable: black screen after prolonged suspend and window artifacts in system settings. I’ve tried turning off the D3 powersaving options for the nvidia module, but it seems to make no difference.

I am returning to 440.

Before I reboot, my update is frozen on updating grub:
(15/27) Updating Grub-Bootmenu Generating grub configuration file ... Found background: /usr/share/grub/background.png Found linux image: /boot/vmlinuz-5.4-x86_64 Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.4-x86_64.img Found initrd fallback image: /boot/initramfs-5.4-x86_64-fallback.img Found linux image: /boot/vmlinuz-4.19-x86_64 Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.19-x86_64.img Found initrd fallback image: /boot/initramfs-4.19-x86_64-fallback.img Found linux image: /boot/vmlinuz-4.14-x86_64 Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.14-x86_64.img Found initrd fallback image: /boot/initramfs-4.14-x86_64-fallback.img Found linux image: /boot/vmlinuz-4.9-x86_64 Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.9-x86_64.img Found initrd fallback image: /boot/initramfs-4.9-x86_64-fallback.img

Now, the ethernet keeps dis/reconnecting; no disks are mounting; Timeshift not launching.

EDIT:
I interrupted the upgrade, checked grub for errors (no errors) and then rebooted. Everything seems okay, but I’ll go back to yesterday’s system backup and try again.

EDIT 2: After applying yesterday’s backup, the upgrade is frozen in the grub section again (over 30 minutes).

I’m a bit confused about the order to proceed in order to keep the system usable after this update. Edited for our own good
Do pacnew in /etc.pam.d/ have to be proceed before reboot? :confused:
I’m the kind of guy to put chances on my side before updating my machine, better than chrooting it after it breaks.
Then, just after TTY updating, ones should look for pacnews files, and apply changes right away. Am I right ?
For now it looks like I would have 3 pacnew files after update:

 [philippe@Probook-450 ~]$ grep -E "pam_tally|pam_cracklib" /etc/pam.d/*
 /etc/pam.d/gdm-fingerprint:auth     required  pam_tally.so onerr=succeed file=/var/log/faillog
 /etc/pam.d/gdm-smartcard:auth     required  pam_tally.so onerr=succeed file=/var/log/faillog
 /etc/pam.d/passwd:#password	required	pam_cracklib.so difok=2 minlen=8 dcredit=2 ocredit=2 retry=3
 /etc/pam.d/system-login:auth       required   pam_tally2.so        onerr=succeed file=/var/log/tallylog
 /etc/pam.d/system-login:account    required   pam_tally2.so 
 [philippe@Probook-450 ~]$

Until here I was used to proceed pacnew with two terminal windows, but in TTY I will have only one :worried:
I’ve read severals workaround here and here, but what is the best method?
Any help would be appreciate

Hi, I have problem with libreoffice - it keeps crashing when I’m trying open some document (writer, calc).

OK, solutions is “libreoffice --safe-mode” and restore settings to default (which is little pissy for me).

My post was before update only ;
After is a classic merge, .pacnew gdm/sddm/… pambase are safe, we can copy .pacnew in old file
only if we want pam_tally function, we replace pam_tally2 by pam_faillock
and if you have other customization, keep them

Update went fine. PAM didn’t need intervention. Rebooted just fine… however…

8 hours later today morning I was unable to wake the computer from “sleep” (or it was in some weird sleep state never seen before… also it seems to have turned off USB maybe?? Moving mouse and pressing keys didn’t do anything. Keyboard rgb lights were even turned off, which has never happened before unless computer fails to POST… so thought it had done some hard crash or something… but later log didn’t show anything even remotely crashy and background tasks seemed to run just fine until I had to power button restart the system…

also there is this new thing with kernel 5.8.3:

aug   29 13:30:02 Zen kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
aug   29 13:30:02 Zen kernel: pcieport 0000:00:01.3: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
aug   29 13:30:02 Zen kernel: pcieport 0000:00:01.3: AER:   device [1022:1453] error status/mask=00000040/00006000
aug   29 13:30:02 Zen kernel: pcieport 0000:00:01.3: AER:    [ 6] BadTLP                
aug   29 13:31:23 Zen kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
aug   29 13:31:23 Zen kernel: pcieport 0000:00:01.3: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
aug   29 13:31:23 Zen kernel: pcieport 0000:00:01.3: AER:   device [1022:1453] error status/mask=00001000/00006000
aug   29 13:31:23 Zen kernel: pcieport 0000:00:01.3: AER:    [12] Timeout               
aug   29 13:56:44 Zen kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
aug   29 13:56:44 Zen kernel: pcieport 0000:00:01.3: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
aug   29 13:56:44 Zen kernel: pcieport 0000:00:01.3: AER:   device [1022:1453] error status/mask=00000080/00006000
aug   29 13:56:44 Zen kernel: pcieport 0000:00:01.3: AER:    [ 7] BadDLLP               
aug   29 13:59:07 Zen kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
aug   29 13:59:07 Zen kernel: pcieport 0000:00:01.3: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
aug   29 13:59:07 Zen kernel: pcieport 0000:00:01.3: AER:   device [1022:1453] error status/mask=00001000/00006000
aug   29 13:59:07 Zen kernel: pcieport 0000:00:01.3: AER:    [12] Timeout               

Firefox 80 is not included in this update - it’s still in testing afaik…

Smooth update, KDE, Kernel Latest, Amd APU, Radeon driver, no problems at all, no intervention needed from my side, thanks Manjaro Team, good work

then you can add to boot kernel ( and so /etc/default/grub & update-grub )
PCI=NOAER

A small hiccup with Kvantum not applying the selected theme at the first login after update. The theme is correctly applied on subsequent logins.

:man_shrugging:

After updating, I noticed the fans in my laptop (ThinkPad X1 Extreme Gen 2) reach 0 RPM frequently. This was not the case before. Not sure which plays a bigger part, Kernel 5.8.3, Nvidia 450.66, or the new BIOS.

After this update on Manjaro KDE, the option to switch user is missing on SDDM lock screen.

This seems to be caused by SystemD in connection with SDDM. Found a bug report under FS#67623 on Arch forums but cannot post a link here.

Suggested fix is currently to downgrade systemd, systemd-libs and systemd-sysvcompat to pre-246.

4 Likes

I only removed the files form ~/.local/share/akonadi and ~/.config/akonadi and everything else went fine. No need to downgrade.

Nice update…btw guys, which browser are you using ? I need fast one, with sync for Android and Linux.

I was unable to log in after the upgrade and didn’t read @philm’s post above.

However I was able to fix the issue by booting with a Live USB then cd into /etc/pam.d and merge system-login.pacnew into system-login.

My AMD based Toshiba netbook will still not boot with the 5.8 Kernel, same problem as I have posted about previously. It works fine otherwise with earlier kernels.

I managed to pinpoint the issue to a single line in /etc/pam.d/system-auth.
After upgrading pam and pambase to the newest version, I just need to comment out following line from /etc/pam.d/system-auth to make xrdp work again:
-account [success=1 default=ignore] pam_systemd_home.so