[Stable Update] 2021-07-23 - Kernels, Nvidia, Mesa, Wine, Firefox, Thunderbird, Virtualbox

Hello community,

Another stable branch update with some usual updates for you.


Check out our latest Pahvo Preview.

  • Most of our Kernels got updated. Note that 5.12 series is now marked EOL.
  • Wine is now at 6.13
  • VirtualBox got updated to 6.1.24
  • Pipewire got renewed to 0.3.32
  • We ship now Nvidia Driver 470.57.02
  • System is at 248.5
  • Some packages got update like Breath2-Themes, Cinnamon, Kodi
  • Firefox is now at 90.0
  • Mesa 21.1.5 is out now
  • More updates to our Breath2 theme
  • AMDVLK is at 2021.Q3.1
  • Other regular upstream updates

Get our latest daily developer images now from Github: Plasma, Gnome, XFCE. You get the latest stable releases of Manjaro from CDN77.


Our current supported kernels

  • linux44 4.4.276
  • linux49 4.9.276
  • linux414 4.14.240
  • linux419 4.19.198
  • linux54 5.4.134
  • linux510 5.10.52
  • linux512 5.12.19 [EOL]
  • linux513 5.13.4
  • linux510-rt 5.10.47_rt46
  • linux511-rt 5.11.4_rt11

Package Updates (Wed Jul 21 12:57:40 CEST 2021)

  • stable community x86_64: 707 new and 696 removed package(s)
  • stable core x86_64: 36 new and 37 removed package(s)
  • stable extra x86_64: 407 new and 570 removed package(s)
  • stable kde-unstable x86_64: 256 new and 255 removed package(s)
  • stable multilib x86_64: 26 new and 26 removed package(s)

A detailed list of all changes 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:

19 Likes

Known issues and solutions

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


New issues:

  • You might be blocked updating when using pacman due to some libcanberra packages. Simply remove those packages: sudo pacman -Rdd lib32-libcanberra-pulse lib32-libcanberra-gstreamer libcanberra-pulse libcanberra-gstreamer. We recommend to use pamac anyway, which does this automatically: pamac update

  • Compiz packages like compiz-easy-patch got dropped from our repositories. Due to protobuf update you may need to rebuild that package locally on your end. Compiz-easy-patch removed from repos

Nextcloud problem and workaround

Problem:
After upgrading mariadb to 10.6.3-1 and executing

sudo systemctl restart mariadb.service && sudo mariadb-upgrade -u root -p

Nextcloud doesn’t work anymore showing several errors, all of them related to “InnoDB refuses to write tables with ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE.

Workaround:
In /etc/my.cnf.d/server.cnf under section [mariadb] put:

innodb_read_only_compressed=0

Workaround found here: Arch Forum - [SOLVED] Issues on nextcloud 22.0.0 and mariadb 10.6

KDE logo in splash screen instead of Manjaro logo
  • Backup / remove the old ksplashrc file
  • mv ~/.config/ksplashrc ~/.config/ksplashrc.bak
  • Go to System Settings
  • Type in Splash
  • Click on Splash Screen
  • Select and Apply your desired splash screen
Telegram fails to open

Telegram fails with:

(telegram-desktop:6166): Telegram-WARNING **: 15:46:00.533: Application was built without embedded fonts, this may lead to font issues.
(telegram-desktop:6166): GLib-GObject-WARNING **: 15:46:00.619: cannot register existing type 'GtkWidget'
(telegram-desktop:6166): GLib-GObject-CRITICAL **: 15:46:00.619: g_type_add_interface_static: assertion 'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed
(telegram-desktop:6166): GLib-GObject-WARNING **: 15:46:00.619: cannot register existing type 'GtkBuildable'
(telegram-desktop:6166): GLib-GObject-CRITICAL **: 15:46:00.619: g_type_interface_add_prerequisite: assertion 'G_TYPE_IS_INTERFACE (interface_type)' failed
(telegram-desktop:6166): GLib-CRITICAL **: 15:46:00.619: g_once_init_leave: assertion 'result != 0' failed
(telegram-desktop:6166): GLib-GObject-CRITICAL **: 15:46:00.619: g_type_add_interface_static: assertion 'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed
(telegram-desktop:6166): GLib-GObject-CRITICAL **: 15:46:00.619: g_type_register_static: assertion 'parent_type > 0' failed

Upgrade to at least version Version 2.8.11-2.0 as that should fix the bug by executing:

pamac upgrade
KDE krunner and Alt+F1 issues

Symptoms:

  • krunner does not work, no popup when typing on empty desktop and Alt+F2 shows an empty transparent window within a subdued black frame.
  • application launcher doesn’t open with Alt+F1, and when opened with mouse, the entries in the menu don’t work (restart, shutdown etc.).

Solution:

  • Reboot through sudo reboot
  • remove from ~/.config :
    • kglobalshortcutsrc
    • krunnerrc
    • plasma-org.kde.plasma.desktop-appletsrc
  • change global theme and login screen to Breeze and reboot
  • login on tty and rm -rf ~/.cache
  • login on graphical screen
  • change global theme and login screen to Breath2 and reboot

Older Issues

  • OS prober does not run and add other operating systems

    Please click the ► at the beginning of this line to view this solution

    To restore, please execute: echo GRUB_DISABLE_OS_PROBER=false|sudo tee -a /etc/default/grub && sudo update-grub

    For more information, see opening post in [Stable Update] 2021-03-08.

Nvidia card owners

  • We simplified nVidia driver installation. This means we dropped legacy drivers.
    • We recommend to switch over to Nouveau drivers if your card is mentioned here and the feature you need is not in red TO DO here for your particular card.

    • If you however still need proprietary drivers, you may want to execute the following to ensure all parts of the nVidia drivers get installed properly:

      sudo mhwd -a pci nonfree 0300
      
      If proprietary drivers don't fix everything, please click the ► at the beginning of this line to view more info
      1. try installing kernel 5.4 LTS (Long Term Support)
      2. If that doesn’t fix it, take a full system backup, go to a console using Ctrl+Alt+F2 and:
      • Backup /etc/X11/mhwd.d/nvidia.conf if you ever edited that manually

      • remove all nVidia related drivers and applications:

        pacman --remove nvidia*
        
      • Note which applications are being removed and keep them handy in a list

      • Install the driver first:

        mhwd --install video-hybrid-XXX-nvidia-prime
        

        (Where XXX is amd or intel if you have hybrid graphics or the whole thing is video-nvidia if you’re on an nVidia-only system)

      • reboot and see if you at least get a screen.

      • Install all the other applications from your handy list that you still need one by one.

      • Restore /etc/X11/mhwd.d/nvidia.conf if you ever edited that manually

      • If that wouldn’t solve the issue open a new issue here referring to this update and posting at a minimum the full output of:

        inxi --admin --verbosity=7 --filter --no-host --width
        

      If you however still have issues with your Nvidia card, you may open a new thread in our forum: https://forum.manjaro.org/c/support/Graphic-Cards/33 or look at our tutorial on compiling old Nvidia drivers.

For AMD GPU users having a black screen with kernel 5.10

Please click the ► at the beginning of this line to view more info

Due to a bug in the AMD drivers, please try the following first:

For GRUB:

  1. Open a terminal or a TTY
  2. Open /etc/default/grub in your favourite CLI editor (nano vi, emacs`)
  3. Find the line: GRUB_CMDLINE_LINUX_DEFAULT="
  4. Add amdgpu.dc=0
  5. Save
  6. Execute sudo update-grub and reboot

For systemd-boot:

  1. Open a terminal or a TTY
  2. Open /boot/loader/entries/manjarolinux5.10.conf in your favourite CLI editor (nano vi, emacs`)
  3. Add amdgpu.dc=0 to the end of the line options
  4. Save & reboot

For rEFInd:

  1. Open a terminal or a TTY
  2. Open /boot/refind_linux.conf in your favourite CLI editor (nano vi, emacs`)
  3. Find the line: "Boot using default options" "root=
  4. Add amdgpu.dc=0
  5. Save & reboot

Possible 2 Min delay on shutdown with Gnome

Please click the ► at the beginning of this line to view more info
  • If you got the problem with shutdown delay (about 2min) on Gnome, here is a workaround:
    • Edit /usr/lib/systemd/user/gnome-session-restart-dbus.service in your favourite editor as root and add Slice=-.slice as a line all by itself like this:

      [Service]
      Type=notify
      Slice=-.slice
      ExecStart=/usr/lib/gnome-session-ctl --restart-dbus
      
    • Click this link For more information

Touchpad on a ThinkPad stops working

  • Restart again, please.

You get [PKGNAME] warning: directory permissions differ on [Directory name]

followed by:

Filesystem: NNN package MMM

Please click the ► at the beginning of this line to view this solution
  • The solution:

    sudo chmod MMM DirectoryName
    

Where obviously MMM is the second number you see (the correct one)

  • The explanation:
    Your package expects the security permissions to be MMM but your system is set to NNN. This is just a warning (today) but to ensure you remain up-to-date with the latest and greatest security rules it’s advised to execute the above command.

Systemd error message: .slice: Failed to migrate controller cgroups

If you have a similar error message like this:

systemd[1004]: -.slice: Failed to migrate controller cgroups from /user.slice/user-1000.slice/user@1000.service, ignoring: Permission denied

… you may need to add this Grub parameter to your /etc/default/grub file in line GRUB_CMDLINE_LINUX_DEFAULT: systemd.unified_cgroup_hierarchy=true. To update your grub menu, call: sudo update-grub. For more information on that issue, see also Arch Forum.


Python 3.9 Requires Rebuilds

Instructions for quickly and easily rebuilding affected AUR packages:

# Install yay
sudo pacman -S --needed --noconfirm yay

# Rebuild AUR python packages
yay -S --noconfirm $(pacman -Qqo "/usr/lib/python3.8/site-packages")

libtraceevent>=5.9-1 update requires manual intervention

2020-10-23 - Sébastien Luttringer

The libtraceevent package prior to version 5.9-1 was missing a soname link. This has been fixed in 5.9-1, so the upgrade will need to overwrite the untracked files created by ldconfig. If you get any of these errors

libtraceevent: /usr/lib/libtraceevent.so.1 exists in filesystem

when updating, use

pacman -Syu --overwrite /usr/lib/libtraceevent.so.1

to perform the upgrade.

https://www.archlinux.org/news/libtraceevent59-1-update-requires-manual-intervention/

OpenVPN connection times out.

Workaround: donwgrade openvpn (2.5.0-1 => 2.4.9-2).
For a proper solution follow this bug report on Arch Linux: FS#68480 : [openvpn] running unprivileged with iproute no longer working

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”

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 cups.service
systemctl enable cups.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.

GDM does not start (black screen when booting gnome edition)

Log into your system via tty and depending on your use of Plymouth or bootsplash-systemd choose a option from this post

5 Likes

This bug (outdated udev rules that disables features from nvidia cards like audio over hdmi) is still present.

2 Likes

5 posts were split to a new topic: Libusb issue since last update with 5.13

Under Tweaks → Themes → Shell I cant choose anything. Its just empty with an error sign.

2 posts were split to a new topic: Grub-probe: error: cannot find a GRUB drive for Microsoft/Boot/boot

Thanks for pointing this out, commented that lines in mine config. I’ve been trying to do PCI Passthrough of my dGPU and been wondering why I don’t see HDMI and USB-C though they should be. Just wanted to add the exact lines in NVIDIA readme saying about kernel 5.5.

UPD. In addition to /etc/udev/rules.d/90-mhwd-prime-powermanagement.rules I also had to fix /usr/lib/udev/rules.d/80-nvidia-pm.rules file for my shiny new kernel > 5.5 :slightly_smiling_face:

2 Likes

The nice little “enjoy the simplicity” animation (in SDDM ???) at startup is gone. Is there a way to get it back? This is a KDE desktop.

3 Likes

Nextcloud problem and workaround

Problem:
After upgrading mariadb to 10.6.3-1 and executing

sudo systemctl restart mariadb.service && sudo mariadb-upgrade -u root -p

Nextcloud doesn’t work anymore showing several errors, all of them related to “InnoDB refuses to write tables with ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE.

Workaround:
In /etc/my.cnf.d/server.cnf under section [mariadb] put:

innodb_read_only_compressed=0

Workaround found here: Arch Forum - [SOLVED] Issues on nextcloud 22.0.0 and mariadb 10.6

3 Likes

Enable User Theme from Extensions.

1 Like
 (telegram-desktop:6166): Telegram-WARNING **: 15:46:00.533: Application was built without embedded fonts, this may lead to font issues.

(telegram-desktop:6166): GLib-GObject-WARNING **: 15:46:00.619: cannot register existing type 'GtkWidget'

(telegram-desktop:6166): GLib-GObject-CRITICAL **: 15:46:00.619: g_type_add_interface_static: assertion 'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed

(telegram-desktop:6166): GLib-GObject-WARNING **: 15:46:00.619: cannot register existing type 'GtkBuildable'

(telegram-desktop:6166): GLib-GObject-CRITICAL **: 15:46:00.619: g_type_interface_add_prerequisite: assertion 'G_TYPE_IS_INTERFACE (interface_type)' failed

(telegram-desktop:6166): GLib-CRITICAL **: 15:46:00.619: g_once_init_leave: assertion 'result != 0' failed

(telegram-desktop:6166): GLib-GObject-CRITICAL **: 15:46:00.619: g_type_add_interface_static: assertion 'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed

(telegram-desktop:6166): GLib-GObject-CRITICAL **: 15:46:00.619: g_type_register_static: assertion 'parent_type > 0' failed

good morning everyone and thanks for everything …the update went well but telegram fails to open…with that error from the terminal…version 2.8.11.2

1 Like
  • Go to System Settings
  • Type Splas
  • Click Splash Screen
  • Take Breath2
3 Likes

5 posts were split to a new topic: KDE Logo in splash screen instead of Manjaro after update

3 posts were split to a new topic: KDE Meta key doesn’t open menu after update

I have the same problem here. On Arch this is already reported as a bug.

The update went well at first glance, but my computer froze twice since I installed it. I had to shut it down by force each time.

Logs : https://paste.ubuntu.com/p/cgXdms3fth/

2 Likes

seems there is a bug at Arch: FS#71541 : [telegram-desktop] telegram-desktop doesn't work after update to 2.8.11-1

I’m using KDE,cannot reproduce,telegram 2.8.11.2 works fine on my machine :thinking:

Please read this:

Have you tried 5.10 LTS (Long Term Support) already?

telegram-desktop version 2.8.11-2.0 should fix the bug.

3 Likes