[Stable-Staging Update] 2020-09-06 - Kernels, Mesa, Browsers, KDE Apps 20.08.1, Systemd, LibreOffice 7.0.1, Deepin

Hello community,

Another stable-staging branch update with some interesting updates for you!


Get the latest Phosh image for your PinePhone #stayhome, #staysafe, #stayhealthy

  • Some more KDE-git and Deepin package updates
  • LibreOffice is now at 7.0.1
  • KDE Apps are now at 20.08.1
  • Palemoon browser got renewed to 28.13.0
  • Systemd got another point-release
  • Most of our Kernels got renewed
  • File conflict with dunstify got fixed
  • Firefox got updated to 80.0.1 and 81-beta4
  • Gambas 3.15 saw it’s first point-release
  • Most of our Kernels got updated
  • Wine is now at 5.16
  • We added CoreCTRL so you can tweak your grahics cards better
  • AMD managed to get another AMDVLK release out
  • Usual Python and Haskell package updates and rebuilds

If you like following latest Plasma development you may also like to check out our current version of manjaro-kde-dev, which we build on a regular basis against kde-git master packages. Also check out our latest RC of Manjaro Mikah 20.1! XFCE, KDE and Gnome


Our current supported kernels

  • linux44 4.4.235
  • linux49 4.9.235
  • linux414 4.14.196
  • linux419 4.19.143
  • linux54 5.4.62
  • linux57 5.7.19 [EOL]
  • linux58 5.8.6
  • linux59 5.9-rc3
  • linux54-rt 5.4.61_rt37
  • linux56-rt 5.6.19_rt12

Package Changes (Sun Sep 6 10:52:26 CEST 2020)

  • stable-staging community x86_64: 1748 new and 1717 removed package(s)
  • stable-staging core x86_64: 64 new and 61 removed package(s)
  • stable-staging extra x86_64: 937 new and 947 removed package(s)
  • stable-staging multilib x86_64: 28 new and 27 removed package(s)

A list of all package changes made in this update can be found here.

  • No issue, everything went smoothly
  • Yes there was an issue. I was able to resolve it myself.(Please post your solution)
  • Yes i am currently experiencing an issue due to the update. (Please post about it)

0 voters

Check if your mirror has already synced:

8 Likes

Known issues and solutions

This is a wiki post; please edit as necessary.
Please, consider subscribing to the Stable-Staging Updates Announcements RSS feed


PAM and PAMBASE got updated, which might prevent you from login

Due to updates from pambase and pam you might take care about any .pacnew files in /etc/pam.d as for example pam_tally, pam_tally2 and pam_cracklib got deprecated. Read in the ArchWiki about managing those files.

Typical issue:

For recovery, it is enough to boot with kernel option “systemd.unit=rescue.target”, then proceed into /etc/pam.d and merge “system-auth” and “system-auth.pacnew”

Older Issues

System takes a long time to boot

If you’ve got errors like Failed to start Network Manager Wait Online. you can try removing systemd from passwd and group in /etc/nsswitch.conf as described here
Update: If you can see the line
dbus-daemon[1453]: [system] Connection has not authenticated soon enough, closing it (auth_timeout=30000ms, elapsed: 45146ms)
in in your dbus log ( journalctl -b -u dbus ), the new/better workaround is to switch cups from service to socket as described here:
systemctl disable org.cups.cupsd.service
systemctl enable org.cups.cupsd.socket

I think I’ve some font problems

With the update of fontconfig some major rules how fonts get applied changed. Make sure that your system has ttf-dejavu installed. A more in depth explanation can be found here.

Gnome-shell-extension-pop-shell is currently incompatible with wayland

… and causes the system to freeze when the first window is tiled and can render it unbootable. Solution is a hard reset and disabling either pop shell or wayland. If the system becomes unbootable, use a live USB to edit /etc/gdm/custom.conf to disable wayland and reboot.

A post was split to a new topic: New installs hanging when installing proprietary drivers

Smooth update and everything seems to work fine :slight_smile:
Don’t know is this is important but I had this warning (kernel 5.8.6-1):
==> WARNING: Possibly missing firmware for module: xhci_pci

more details
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.8-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux58.preset: 'fallback'
  -> -k /boot/vmlinuz-5.8-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.8-x86_64-fallback.img -S autodetect
==> Starting build: 5.8.6-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: xhci_pci
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
inxi
System:
  Kernel: 5.8.6-1-MANJARO x86_64 bits: 64 compiler: N/A 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.8-x86_64 
  root=UUID=f058c567-0081-4771-b20a-fef880c45251 rw quiet udev.log_priority=3 
  resume=UUID=f8fdb6be-1bb9-4206-9df2-97f0a223dceb 
  Desktop: Xfce info: tint2 wm: Openbox 3.6.1 dm: LightDM 1.30.0 
  Distro: Manjaro Linux 
Machine:
  Type: Laptop System: LENOVO product: 20ASS11T00 v: ThinkPad L440 
  serial: <filter> Chassis: type: 10 serial: <filter> 
  Mobo: LENOVO model: 20ASS11T00 serial: <filter> UEFI [Legacy]: LENOVO 
  v: J4ET65WW(1.65) date: 06/24/2014 
Battery:
  ID-1: BAT0 charge: 16.7 Wh condition: 38.6/47.5 Wh (81%) volts: 11.0/10.8 
  model: SANYO 45N1159 type: Li-ion serial: <filter> status: Unknown 
CPU:
  Topology: Dual Core model: Intel Core i5-4200M bits: 64 type: MT MCP 
  arch: Haswell family: 6 model-id: 3C (60) stepping: 3 microcode: 28 
  L2 cache: 3072 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 19961 
  Speed: 1844 MHz min/max: 800/3100 MHz Core speeds (MHz): 1: 2494 2: 2495 
  3: 2494 4: 2495 
  Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
  Type: l1tf 
  mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
  Type: meltdown mitigation: PTI 
  Type: spec_store_bypass 
  mitigation: Speculative Store Bypass disabled via prctl and seccomp 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, 
  IBRS_FW, STIBP: conditional, RSB filling 
  Type: srbds mitigation: Microcode 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: Intel 4th Gen Core Processor Integrated Graphics vendor: Lenovo 
  driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0416 
  Device-2: Chicony Integrated Camera type: USB driver: uvcvideo 
  bus ID: 2-12:3 chip ID: 04f2:b398 
  Display: x11 server: X.Org 1.20.8 compositor: picom v: git-e553e 
  driver: intel display ID: :0 screens: 1 
  Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.2x8.0") 
  s-diag: 414mm (16.3") 
  Monitor-1: eDP1 res: 1366x768 hz: 60 dpi: 112 size: 310x170mm (12.2x6.7") 
  diag: 354mm (13.9") 
  OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2) 
  v: 4.5 Mesa 20.1.7 compat-v: 3.0 direct render: Yes 
Audio:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio 
  vendor: Lenovo driver: snd_hda_intel v: kernel bus ID: 00:03.0 
  chip ID: 8086:0c0c 
  Device-2: Intel 8 Series/C220 Series High Definition Audio vendor: Lenovo 
  driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:8c20 
  Sound Server: ALSA v: k5.8.6-1-MANJARO 
Network:
  Device-1: Intel Ethernet I217-V vendor: Lenovo driver: e1000e v: 3.2.6-k 
  port: 5080 bus ID: 00:19.0 chip ID: 8086:153b 
  IF: enp0s25 state: up speed: 100 Mbps duplex: full mac: <filter> 
  Device-2: Intel Wireless 7260 driver: iwlwifi v: kernel port: efa0 
  bus ID: 02:00.0 chip ID: 8086:08b2 
  IF: wlp2s0 state: down mac: <filter> 
Drives:
  Local Storage: total: 298.09 GiB used: 96.15 GiB (32.3%) 
  SMART Message: Unable to run smartctl. Root privileges required. 
  ID-1: /dev/sda vendor: Western Digital model: WD3200BEKX-75B7WT0 
  size: 298.09 GiB block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s 
  rotation: 7200 rpm serial: <filter> rev: 1A01 scheme: MBR 
Partition:
  ID-1: / raw size: 209.67 GiB size: 205.37 GiB (97.95%) 
  used: 96.15 GiB (46.8%) fs: ext4 dev: /dev/sda2 
Swap:
  Kernel: swappiness: 10 (default 60) cache pressure: 50 (default 100) 
  ID-1: swap-1 type: partition size: 4.00 GiB used: 0 KiB (0.0%) priority: -2 
  dev: /dev/sda4 
Sensors:
  System Temperatures: cpu: 50.0 C mobo: 43.0 C 
  Fan Speeds (RPM): cpu: 0 
Info:
  Processes: 159 Uptime: 10m Memory: 7.51 GiB used: 1.14 GiB (15.2%) 
  Init: systemd v: 246 Compilers: gcc: 10.2.0 clang: 10.0.1 Packages: 
  pacman: 1282 lib: 296 Shell: Zsh v: 5.8 running in: termite inxi: 3.1.05 
1 Like

In my case I had to install Renesas uPD72020x USB 3.0 chipsets firmware (upd72020x-fw)

2 Likes

when will Thunderbird 78 be avaliable (not thunderbird-bin)

Due to the issues with encrypted emails we have to stay on 68 series for a while. When Mozilla fixed their new way to do encrypted emails we might switch.

7 Likes

I updated but for some reason LibreOffice is still version 6.4.6.2

you are probably using libreoffice still. If you want the latest use libreoffice fresh

1 Like

haha thanks I should’ve done some more googling switching now. Thanks

1 Like

https://bbs.archlinux.org/viewtopic.php?id=257937

3 Likes

There is still a problem with Load/Save/Restore of the backlight xfce+gnome+5.7+5.8 on AMD Ryzen9+nvidia
It was OK with Stable and 5.7 until a stable update last month.
With 20.1-RC5 I have this problem, too.

Log:
Sep 07 17:31:48 rogg14 systemd[1]: systemd-backlight@backlight:amdgpu_bl1.service: Main process exited, code=exited, status=1/FAILURE
Sep 07 17:31:48 rogg14 systemd[1]: systemd-backlight@backlight:amdgpu_bl1.service: Failed with result ‘exit-code’.
Sep 07 17:31:48 rogg14 systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:amdgpu_bl1.
Sep 07 17:31:48 rogg14 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg=‘unit=systemd-backlight@backlight:amdgpu_bl1 comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed’
Sep 07 17:31:57 rogg14 pkexec[1687]: wapel: Executing command [USER=root] [TTY=unknown] [CWD=/] [COMMAND=/usr/bin/xfpm-power-backlight-helper --set-brightness-switch 0]

inxi -G
Graphics: Device-1: NVIDIA TU116M [GeForce GTX 1660 Ti Mobile] driver: nvidia v: 450.66
Device-2: Advanced Micro Devices [AMD/ATI] Renoir driver: amdgpu v: kernel
Display: x11 server: X.Org1.20.8 driver: amdgpu,ati,nvidia unloaded: modesetting,nouveau
resolution: 1920x1080~120Hz
OpenGL: renderer: AMD RENOIR (DRM 3.38.0 5.8.6-1-MANJARO LLVM 10.0.1) v: 4.6 Mesa 20.1.7

mhwd -li

Installed PCI configs:


              NAME               VERSION          FREEDRIVER           TYPE

video-hybrid-amd-nvidia-450xx-prime 2019.10.25 false PCI
video-linux 2018.05.04 true PCI

Libreoffice Writer is constantly crashing. As soon as I open it, it instantly crashes and restarts in the Writer document recovery window.

This happened to me. It was happening due to the tabbed interface I think. I wiped the writer config in .config to recover it. At this time, I cannot use the ribbon interface or the problem starts again.

@itsKia2 @SweetestRug After update LibreOffice to 7.0 I’ve removed libreoffice directory and don’t have issues now. Hope it will work for you as well.
Maybe just in case rename folder instead of removing:
mv ~/.config/libreoffice ~/.config/libreoffice.bak

What is your subdirectory in ~/.config/libreoffice/ before and after renaming config folder? I’m curious it has something to do with update to 7.0

I ended up just removing the specific configs for writer and that fixed the issue. I had no problems with the other components.

I believe the configs being used were in a 4.x subfolder.

Oh, I misunderstood your reply. Sorry :sweat_smile:

My is 4 (after removing configs), a bit weird decision for naming directory :slight_smile:

i just got a bunch of packages shown as available to update, but im on stable branch, there is no post here saying there is a new stable update, was this pushed to stable on accident?

i have the same problem so i am using the eol tagged 5.7 kernel…

That’s not an accident, sometimes the update is available before the announcement.