[Stable Update] 2021-01-19 - Kernels, XFCE, Plasma, PulseAudio, Pipewire, Mesa, Firefox, Thunderbird, KDE Apps

Hello community,

Another stable update. It is also our first of 2021! So happy New Years everyone !!!


Take a look at the latest KDE development! #stayhome, #staysafe, #stayhealthy

  • Most of our Kernels got an update
  • XFCE got its major 4.16 release
  • Plasma got updated to 5.20.5
  • KDE Apps is at 20.12.1
  • Mesa got updated to 20.3.3
  • More updates to Gnome, KODI-Addons, Gstreamer and KDE-dev
  • KDE Frameworks 5.78 got released
  • Thunderbird is now at 78.6.1
  • Nvidia started a new long-term series with 460xx
  • A new Quarterly Release of AMDVLK
  • Pamac got another point-release
  • Some of our Themes got updated
  • Deepin got further updated packages
  • Firefox got updated to 84.0.2
  • Mass-Rebuild against ICU
  • Qt4 got removed
  • A lot of Haskell and Python rebuilds
  • Other regular upstream updates

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 Manjaro Ornara 21.0 preview release! KDE, XFCE and Gnome


Our current supported kernels

  • linux44 4.4.251
  • linux49 4.9.251
  • linux414 4.14.215
  • linux419 4.19.167
  • linux54 5.4.89
  • linux59 5.9.16 [EOL]
  • linux510 5.10.7
  • linux511 5.11-rc3
  • linux54-rt 5.4.84_rt47
  • linux59-rt 5.9.1_rt19

Packages Changes (Sun Jan 17 10:45:58 CET 2021)

  • stable community x86_64: 2349 new and 2275 removed package(s)
  • stable core x86_64: 56 new and 54 removed package(s)
  • stable extra x86_64: 1044 new and 1190 removed package(s)
  • stable multilib x86_64: 43 new and 44 removed package(s)

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

34 Likes

Known issues and solutions

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

New issues:

  • I’m still running on nvidia-450 and I want to recompile the 450 driver (Kernel 5.4 LTS):

    Please click the ► at the beginning of this line to view this solution
    1. Add the line IgnorePkg = lib32-nvidia-utils lib32-opencl-nvidia mhwd-nvidia opencl-nvidia in file /etc/pacman.conf

    2. Upgrade your packages (using the pamac GUI) or:

      pamac upgrade
      
    3. Reboot on kernel 5.4 (see Note 1 below on how to do this)

    4. Boot will be stuck because no driver has been found, just open a console with Ctrl+Alt+F2

    5. First read Note 2 below, then get the sources for your driver (in my case, 450xx):

      git clone https://gitlab.manjaro.org/packages/extra/nvidia-450xx-utils.git
      git clone https://gitlab.manjaro.org/packages/multilib/lib32-nvidia-450xx-utils.git
      git clone https://gitlab.manjaro.org/packages/extra/linux54-extramodules/nvidia-450xx.git
      
    6. Compile the driver (if you get an error, see Note 3):

      cd nvidia-450xx-utils && makepkg -si
      cd ../lib32-nvidia-450xx-utils && makepkg -si
      cd ../nvidia-450xx && makepkg -sif
      
    7. Reboot on kernel 5.4 (see Note 1 below on how to do this)

    Now, everything is working again! To check if you’re indeed running kernel Linux 5.4, you can run uname --kernel-release in a console, and to check if you’re running the driver you just compiled, you can run inxi --graphics --display OR nvidia-smi

    Note 1: to choose which kernel to boot on, you need to edit those two lines in /etc/default/grub to match those (5 as in 5 seconds to make your choice on the menu, you can put whatever):

      GRUB_TIMEOUT=5
      GRUB_TIMEOUT_STYLE=menu
    

    Then, run sudo update-grub. When booting, you’ll now see a menu with all installed kernels so you can choose which one to use for this session.

    Then finally execute the reboot command:

      sudo reboot 
    

    Note 2: During step 5 and 6: If you already have compiled the nvidia driver during last update, you can skip cloning nvidia-450xx-utils and lib32-nvidia-450xx-utils (you already have the sources, you just need to compile them again), but I suggest you remove your older nvidia-450xx folder (rm -rf nvidia-450xx) and clone it again before compiling this one, otherwise you will get an error like “folder already exists” when trying to compile.

    Note 3: When trying to compile the driver, you might get an error with two nvidia packages creating conflicts (I think lib32-nvidia-utils was one of them, I don’t remember the other one). To fix that, just uninstall those packages with pamac remove <package>.

  • I’m still running on nvidia-450 and I want to upgrade to 460 (Kernel 5.10):

    Please click the ► at the beginning of this line to view this solution
    • Print this page so you have it as a reference while in TTY2

    • Log off

    • Switch to TTY2 by pressing Ctrl+Alt+F2

    • Log in there

    • Execute:

      pamac remove nvidia-450xx-utils
      #you will get some warnings about optional components needing this: 
      #  no worries, you'll install 460 in the next line
      sudo mhwd --install pci video-nvidia
      sudo reboot
      

Older Issues

Please click the ► at the beginning of this line to view the older issues

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.


CUPS update need manual intervention

After you update your system, update your systemd services like this:

sudo systemctl disable --now org.cups.cupsd.socket
sudo systemctl disable --now org.cups.cupsd.service
sudo systemctl disable --now org.cups.cupsd.path
sudo systemctl enable --now cups.service
sudo systemctl enable --now cups.socket
sudo systemctl enable --now cups.path

[Edit according to @banjo’s advice.]

xf86-video-intel already exists in filesystem errors

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

If you get something like this:

error: failed to commit transaction (conflicting files)
xf86-video-intel: /usr/bin/intel-virtual-output exists in filesystem
xf86-video-intel: /usr/lib/libI810XvMC.so exists in filesystem
...
xf86-video-intel: /usr/share/man/man4/intel.4.gz exists in filesystem
xf86-video-intel: /usr/share/polkit-1/actions/org.x.xf86-video-intel.backlight-helper.policy exists in filesystem
Errors occurred, no packages were upgraded.

Just delete the files that are in conflictand perform the upgrade again.

nvidia-450xx-utils and nvidia-440xx-utils are in conflict

Please click the ► at the beginning of this line to view this solution
  • If you get the following error message:

    resolving dependencies...
    looking for conflicting packages...
    :: nvidia-450xx-utils and nvidia-440xx-utils are in conflict (nvidia-libgl). Remove nvidia-440xx-utils? [y/N] y
    error: failed to prepare transaction (could not satisfy dependencies)
    :: unable to satisfy dependency 'nvidia-440xx-utils=440.100' required by linux54-nvidia-440xx
    :: removing nvidia-440xx-utils breaks dependency 'nvidia-440xx-utils=440.100' required by linux58-nvidia-440xx
    

Warning: do not reboot until this procedure tells you to starting from the next step!

  • Please note the exact nVidia driver you have running by executing:

    mhwd --listinstalled
    
  • Please note the kernel(s) you’ve got installed and remove anything 440-related, including CUDA by executing:

    pamac remove nvidia-440xx-utils linuxZZ-nvidia-440xx cuda nvtop
    

    where ZZ is/are the kernel version(s) you’re running.

  • Repeat for all the kernel versions you have

    How do I know which kernel versions I have?
    • execute ls /boot/linux*
    • any nulber after linux before the - (minus sign) are the kernel(s) you have installed
  • If you would have any other old nVidia drivers that you don’t need any more because your card is supported by the 450 series get rid of them as well.

  • now install the same family of 450 driver you had for the 440 driver, by executing:

    mhwd --install pci Your450Family
    

    where Your450Family is obviously one of video-hybrid-amd-nvidia-440xx-prime OR video-nvidia-440xx that you noted above

  • And finally:

    sudo reboot
    

If this would not have solved your issue, please open a new issue here and state that you followed this procedure already.


Warning: directory permissions differ on /var/lib/dhcpcd/

followed by:

filesystem: 700 package: 755

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

    sudo chmod 755 /var/lib/dhcpcd/
    
  • The explanation:
    The DHCP Daemon expects the security permissions to be 755 but your system is set to 700. 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.


virtualbox NS_ERROR_FAILURE (0x80004005)

Please click the ► at the beginning of this line to view this solution
  • The solution:
  1. You need to add your user back into the virtualbox user group

    sudo usermod --append --groups vboxusers $USER
    

    (Change $USER to the correct user name if not for yourself)

  2. Upgrade the VirtualBox extension pack to the latest version by executing:

    pamac build virtualbox-ext-oracle
    

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

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

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”


Bad font rendering after freetype2 upgrade

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

There were some changes in the freetype2 version 2.10.3 which enable subpixel rendering.
This might look ugly without enabling lcdfilter at the same time.

You can create a symlink in /etc/fonts/conf.d/ to enable “lcddefault” as filter.

sudo ln -s /etc/fonts/conf.avail/11-lcdfilter-default.conf /etc/fonts/conf.d/

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.

7 Likes

Hi, nice update, everything went fine, however starting teamviewer causes the systray-plugin of the new xfce4-panel to crash. I am attaching the journalctl core dump here. Is this issue known? Or should I open a separate thread for this? Or is this an upstream bug?

Jan 19 11:31:40 rhudonia systemd-coredump[7076]: Process 1412 (panel-4-systray) of user 1000 dumped core.
                                                 
                                                 Stack trace of thread 1412:
                                                 #0  0x00007f13ae1f2e63 g_variant_iter_loop (libglib-2.0.so.0 + 0x9ce63)
                                                 #1  0x00007f13aeef3e12 n/a (libsystray.so + 0x14e12)
                                                 #2  0x00007f13ae39c0f4 n/a (libgio-2.0.so.0 + 0xa10f4)
                                                 #3  0x00007f13ae3a0639 n/a (libgio-2.0.so.0 + 0xa5639)
                                                 #4  0x00007f13ae40320d n/a (libgio-2.0.so.0 + 0x10820d)
                                                 #5  0x00007f13ae39c0f4 n/a (libgio-2.0.so.0 + 0xa10f4)
                                                 #6  0x00007f13ae3a0639 n/a (libgio-2.0.so.0 + 0xa5639)
                                                 #7  0x00007f13ae3f5340 n/a (libgio-2.0.so.0 + 0xfa340)
                                                 #8  0x00007f13ae39c0f4 n/a (libgio-2.0.so.0 + 0xa10f4)
                                                 #9  0x00007f13ae39c129 n/a (libgio-2.0.so.0 + 0xa1129)
                                                 #10 0x00007f13ae1a8a84 g_main_context_dispatch (libglib-2.0.so.0 + 0x52a84)
                                                 #11 0x00007f13ae1fc9b1 n/a (libglib-2.0.so.0 + 0xa69b1)
                                                 #12 0x00007f13ae1a7fd3 g_main_loop_run (libglib-2.0.so.0 + 0x51fd3)
                                                 #13 0x00007f13ae8db22f gtk_main (libgtk-3.so.0 + 0x1e122f)
                                                 #14 0x00005573c2bbd337 main (wrapper-2.0 + 0x3337)
                                                 #15 0x00007f13adfb5152 __libc_start_main (libc.so.6 + 0x28152)
                                                 #16 0x00005573c2bbd48e _start (wrapper-2.0 + 0x348e)
                                                 
                                                 Stack trace of thread 1422:
                                                 #0  0x00007f13ae08246f __poll (libc.so.6 + 0xf546f)
                                                 #1  0x00007f13ae1fc93f n/a (libglib-2.0.so.0 + 0xa693f)
                                                 #2  0x00007f13ae1a7fd3 g_main_loop_run (libglib-2.0.so.0 + 0x51fd3)
                                                 #3  0x00007f13ae3fcfe8 n/a (libgio-2.0.so.0 + 0x101fe8)
                                                 #4  0x00007f13ae1d5ec1 n/a (libglib-2.0.so.0 + 0x7fec1)
                                                 #5  0x00007f13ad86c3e9 start_thread (libpthread.so.0 + 0x93e9)
                                                 #6  0x00007f13ae08d293 __clone (libc.so.6 + 0x100293)
                                                 
                                                 Stack trace of thread 1421:
                                                 #0  0x00007f13ae08246f __poll (libc.so.6 + 0xf546f)
                                                 #1  0x00007f13ae1fc93f n/a (libglib-2.0.so.0 + 0xa693f)
                                                 #2  0x00007f13ae1a72b1 g_main_context_iteration (libglib-2.0.so.0 + 0x512b1)
                                                 #3  0x00007f13ae1a7302 n/a (libglib-2.0.so.0 + 0x51302)
                                                 #4  0x00007f13ae1d5ec1 n/a (libglib-2.0.so.0 + 0x7fec1)
                                                 #5  0x00007f13ad86c3e9 start_thread (libpthread.so.0 + 0x93e9)
                                                 #6  0x00007f13ae08d293 __clone (libc.so.6 + 0x100293)
                                                 
                                                 Stack trace of thread 7071:
                                                 #0  0x00007f13ae087d5d syscall (libc.so.6 + 0xfad5d)
                                                 #1  0x00007f13ae1f5a9b g_cond_wait_until (libglib-2.0.so.0 + 0x9fa9b)
                                                 #2  0x00007f13ae178853 n/a (libglib-2.0.so.0 + 0x22853)
                                                 #3  0x00007f13ae1d8ecb n/a (libglib-2.0.so.0 + 0x82ecb)
                                                 #4  0x00007f13ae1d5ec1 n/a (libglib-2.0.so.0 + 0x7fec1)
                                                 #5  0x00007f13ad86c3e9 start_thread (libpthread.so.0 + 0x93e9)
                                                 #6  0x00007f13ae08d293 __clone (libc.so.6 + 0x100293)

Jan 19 11:31:41 rhudonia systemd-coredump[7094]: Process 7085 (panel-4-systray) of user 1000 dumped core.
                                                 
                                                 Stack trace of thread 7085:
                                                 #0  0x00007f8749b98e63 g_variant_iter_loop (libglib-2.0.so.0 + 0x9ce63)
                                                 #1  0x00007f874a899e12 n/a (libsystray.so + 0x14e12)
                                                 #2  0x00007f8749d420f4 n/a (libgio-2.0.so.0 + 0xa10f4)
                                                 #3  0x00007f8749d46639 n/a (libgio-2.0.so.0 + 0xa5639)
                                                 #4  0x00007f8749da920d n/a (libgio-2.0.so.0 + 0x10820d)
                                                 #5  0x00007f8749d420f4 n/a (libgio-2.0.so.0 + 0xa10f4)
                                                 #6  0x00007f8749d46639 n/a (libgio-2.0.so.0 + 0xa5639)
                                                 #7  0x00007f8749d9b340 n/a (libgio-2.0.so.0 + 0xfa340)
                                                 #8  0x00007f8749d420f4 n/a (libgio-2.0.so.0 + 0xa10f4)
                                                 #9  0x00007f8749d42129 n/a (libgio-2.0.so.0 + 0xa1129)
                                                 #10 0x00007f8749b4ea84 g_main_context_dispatch (libglib-2.0.so.0 + 0x52a84)
                                                 #11 0x00007f8749ba29b1 n/a (libglib-2.0.so.0 + 0xa69b1)
                                                 #12 0x00007f8749b4dfd3 g_main_loop_run (libglib-2.0.so.0 + 0x51fd3)
                                                 #13 0x00007f874a28122f gtk_main (libgtk-3.so.0 + 0x1e122f)
                                                 #14 0x000055db671cd337 main (wrapper-2.0 + 0x3337)
                                                 #15 0x00007f874995b152 __libc_start_main (libc.so.6 + 0x28152)
                                                 #16 0x000055db671cd48e _start (wrapper-2.0 + 0x348e)
                                                 
                                                 Stack trace of thread 7086:
                                                 #0  0x00007f8749a2846f __poll (libc.so.6 + 0xf546f)
                                                 #1  0x00007f8749ba293f n/a (libglib-2.0.so.0 + 0xa693f)
                                                 #2  0x00007f8749b4d2b1 g_main_context_iteration (libglib-2.0.so.0 + 0x512b1)
                                                 #3  0x00007f8749b4d302 n/a (libglib-2.0.so.0 + 0x51302)
                                                 #4  0x00007f8749b7bec1 n/a (libglib-2.0.so.0 + 0x7fec1)
                                                 #5  0x00007f87492123e9 start_thread (libpthread.so.0 + 0x93e9)
                                                 #6  0x00007f8749a33293 __clone (libc.so.6 + 0x100293)
                                                 
                                                 Stack trace of thread 7090:
                                                 #0  0x00007f8749a2dd5d syscall (libc.so.6 + 0xfad5d)
                                                 #1  0x00007f8749b9ba9b g_cond_wait_until (libglib-2.0.so.0 + 0x9fa9b)
                                                 #2  0x00007f8749b1e853 n/a (libglib-2.0.so.0 + 0x22853)
                                                 #3  0x00007f8749b7eecb n/a (libglib-2.0.so.0 + 0x82ecb)
                                                 #4  0x00007f8749b7bec1 n/a (libglib-2.0.so.0 + 0x7fec1)
                                                 #5  0x00007f87492123e9 start_thread (libpthread.so.0 + 0x93e9)
                                                 #6  0x00007f8749a33293 __clone (libc.so.6 + 0x100293)
                                                 
                                                 Stack trace of thread 7087:
                                                 #0  0x00007f8749a2846f __poll (libc.so.6 + 0xf546f)
                                                 #1  0x00007f8749ba293f n/a (libglib-2.0.so.0 + 0xa693f)
                                                 #2  0x00007f8749b4dfd3 g_main_loop_run (libglib-2.0.so.0 + 0x51fd3)
                                                 #3  0x00007f8749da2fe8 n/a (libgio-2.0.so.0 + 0x101fe8)
                                                 #4  0x00007f8749b7bec1 n/a (libglib-2.0.so.0 + 0x7fec1)
                                                 #5  0x00007f87492123e9 start_thread (libpthread.so.0 + 0x93e9)
                                                 #6  0x00007f8749a33293 __clone (libc.so.6 + 0x100293)
                                                 
                                                 Stack trace of thread 7091:
                                                 #0  0x00007f8749a2dd5d syscall (libc.so.6 + 0xfad5d)
                                                 #1  0x00007f8749b9ba9b g_cond_wait_until (libglib-2.0.so.0 + 0x9fa9b)
                                                 #2  0x00007f8749b1e853 n/a (libglib-2.0.so.0 + 0x22853)
                                                 #3  0x00007f8749b7eecb n/a (libglib-2.0.so.0 + 0x82ecb)
                                                 #4  0x00007f8749b7bec1 n/a (libglib-2.0.so.0 + 0x7fec1)
                                                 #5  0x00007f87492123e9 start_thread (libpthread.so.0 + 0x93e9)
                                                 #6  0x00007f8749a33293 __clone (libc.so.6 + 0x100293)


So, to be clear, if we get these warnings, we have to run these commands?

sudo rm /usr/bin/intel-virtual-output
sudo rm /usr/lib/libI810XvMC.so
sudo rm /usr/share/man/man4/intel.4.gz
sudo rm /usr/share/polkit-1/actions/org.x.xf86-video-intel.backlight-helper.policy
1 Like

Yes, that’s it.

1 Like

You should open a new topic and you should report the crash to XFCE bugtracker.

EDIT: before doing that, have you tried to update or rebuild teamviewer?

2 Likes

Edit this: currently, we have 84.0.2-0.1 :slight_smile:

5 Likes

is it better for large updates like this to use “sudo pacman -Syyu” instead of Pamac?

1 Like

I didn’t have issues with Manjaro during update this time, but the issue was with the somewhat outdated python2-pyqt4 package that still has sip as a dependency instead of sip4.

qt4 was removed with this update, so python2-pyqt4 probably was too.

I am using pacman -Syyu on console to update my systems.

2 Likes

Last stable update, I compiled old nvidia driver (450) for linux54. This update ships with a newer linux54 version, and as told in the support topic:

You may need to recompile nvidia-4YYxx whenever we release a new linux54 kernel.

I indeed needed to recompile nvidia-450xx after this update. Here’s how to do it (you can change all occurrences of “450” with your desired driver):

  1. Add the line IgnorePkg = lib32-nvidia-utils lib32-opencl-nvidia mhwd-nvidia opencl-nvidia in file /etc/pacman.conf
  2. Upgrade your packages (graphical interface or sudo pacman -Syyu)
  3. Reboot (sudo reboot) on kernel 5.4 (see Note 1 below on how to do this)
  4. Boot will be stuck because no driver has been found, just open a console with CTRL + ALT + F2.
  5. First read Note 2 below, then get the sources for your driver (in my case, 450xx):
git clone https://gitlab.manjaro.org/packages/extra/nvidia-450xx-utils.git
git clone https://gitlab.manjaro.org/packages/multilib/lib32-nvidia-450xx-utils.git
git clone https://gitlab.manjaro.org/packages/extra/linux54-extramodules/nvidia-450xx.git
  1. Compile the driver (if you get an error, see Note 3):
cd nvidia-450xx-utils && makepkg -si
cd ../lib32-nvidia-450xx-utils && makepkg -si
cd ../nvidia-450xx && makepkg -sif
  1. Reboot (sudo reboot) on kernel 5.4 (see Note 1 below on how to do this)

Now, everything is working again! To check if you’re indeed running kernel linux 5.4, you can run uname -r in a console, and to check if you’re running the driver you just compiled, you can run inxi -G --display.

Note 1: to choose which kernel to boot on, you need to edit those two lines in /etc/default/grub to match those (5 as in 5 seconds to make your choice on the menu, you can put whatever):

GRUB_TIMEOUT=5
GRUB_TIMEOUT_STYLE=menu

Then, run sudo update-grub. When booting, you’ll now see a menu with all installed kernels so you can choose which one to use for this session.

Note 2: During step 5 and 6: If you had already compiled the nvidia driver last update, you can skip cloning nvidia-450xx-utils and lib32-nvidia-450xx-utils (you already have the sources, you just need to compile them again), but I suggest you remove your older nvidia-450xx folder (rm -rf nvidia-450xx) and clone it again before compiling this one, otherwise you will get an error like “folder already exists” when trying to compile.

Note 3: When trying to compile the driver, you might get an error with two nvidia packages creating conflicts (I think lib32-nvidia-utils was one of them, I don’t remember the other one). To fix that, just uninstall those packages with sudo pacman -R <package>.

9 Likes
$ pactree -rl qt4
qt4
libdbusmenu-qt4
sni-qt
phonon-qt4

I guess it’s safe to remove qt4 altogether now?

There are some minor cosmetic problems that I realized.

  • xfce4-power-manager system tray icons are different from my choosen icon package. It wasn’t changed when I’d chosen a different icon package, it uses the same icon whatever I choose things.
    Downgrade package is resolve the problem for temporary.
  • Standard favorite apps seen on Whisker Menu has disappeared.
    I did not do anything.

As far as I can see, the update went fine on three computers:
1 * KDE and 2 * XFCE.

Thanks!

2 Likes

Yes, I rebuilt teamviewer but the crash still occurs. I’ll follow your advice and report to the bugtracker too.
Edit: Found an open bug report on this at Status Notifier crashes opening TeamViewer 13 o 14 (#6) · Issues · Panel Plugins / xfce4-statusnotifier-plugin · GitLab

2 Likes

After this update, on reboot I have :
Failed to start load kernel modules
and the system stop.
I don’t know to fix that.

1 Like

After doing

pacman -Syyu

I get

error: gptfdisk: signature from "Evangelos Foutras <evangelos@foutrelis.com>" is invalid :: File /var/cache/pacman/pkg/gptfdisk-1.0.6-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)). Do you want to delete it? [Y/n]

Help appreciated.

On the upstream there is a fix for the xfce panel: statustray: Prevent crash when parsing properties (Fixes #379) (e4616236) · Commits · Xfce / xfce4-panel · GitLab
which has been appplyed two weeks ago; can you consider to push it on Manjaro’s branches?

Sorry: maybe is not related:

Everything went fine, apart from a broken power icon on XFCE.

1 Like