Known issues and solutions
This is a wiki post; please edit as necessary.
Please, consider subscribing to the Stable Updates Announcements RSS feed
Please RTFT (Read This Fine Thread) first before reporting the same issues over and over again!
Note: Do not forget to review your .pacnew files:
2024-11-30
GTK4 apps may not start due to Vulkan GSK Renderer by Default on Wayland
With GTK 4.16 release GNOME switched to Vulkan GSK Renderer by default. When you have not setup Vulkan support properly your GTK4 apps might not work as expected. Also users with Nvidia drivers might have issues, such as people using RasberryPi and older hardware. You can override it by setting the GSK_RENDERER=ngl or GDK_DISABLE=vulkan environment variable in /etc/environment file. For much more older PCs even GSK_RENDERER=gl is recommended. To boost rendering you can also set GDK_GL_DISABLE=buffer-storage, so the ngl renderer would perform similar to what you knew from GNOME 46.
Graphical interface might not start due to missing libpixbufloader-svg.so
Seems there was a so-name naming change within librsvg: 2.58.90: -/_ switch in the name of the pixbuf loader? (#1075) · Issues · GNOME / librsvg · GitLab. To fix it issue: sudo gdk-pixbuf-query-loaders --update-cache
More information here: After today's update my machine is stuck on loading lightdm, no TTY access possible either - #36 by Photon
Pamac might not find AUR database
It is a known bug to have a message like this:
Failed to read AUR data from /var/lib/pacman/sync/packages-meta-ext-v1.json.gz : Error opening file /var/lib/pacman/sync/packages-meta-ext-v1.json.gz: No such file or directory
You can fix it by doing this: pamac upgrade --aur --force-refresh --dry-run
If it does not work that way try without --dry-run parameter.
Cursor sizes may vary when Wayland is used
If you enabled global scaling in Wayland within Plasma 6, especially with a fractional scale like 2.5x, cursor sizes would be a mess across various apps. For more information see this blog post: Cursor Size Problems In Wayland, Explained - KDE Blogs
Cinnamon 6.4 might change the default theme to a dark one
With Cinnamon 6.4 a lot of changes were made. The theme is significantly darker and offers more contrast than previous versions. Objects within the interface are now rounded, and a gap has been introduced between applets and the panel, giving the desktop environment a modern and polished appearance.
Nvidia: drivers might not work with 6.12 kernel
See also this open issue: 6.12: drm_open_helper RIP · Issue #712 · NVIDIA/open-gpu-kernel-modules · GitHub Nvidia provided a patch and shipped it in their 550.135 driver. More information here: Patch for 565.57.01 + Linux kernel 6.12 - Linux - NVIDIA Developer Forums.
We also patched 470xx and 390xx driver series as needed. Based on the current feedback, it seems that 470xx and 390xx drivers might not work at all with 6.12 kernel. 390xx got its last update by end of 2022, and we managed to keep it alive with kernel patches. If you have a legacy gpu you may consider to use the FOSS nouveau driver or exchange the GPU for a newer hardware.
Those who face issues with current provided drivers, may politely voice-up at the Nvidia developer forums in a civil manner and report their issue there: »»»»»»»»»» If you have a problem, PLEASE read this first «««««««««« - Linux - NVIDIA Developer Forums
2024-10-13
Kernel 6.10 has been marked [EOL] on kernel.org
Linux 6.10 is EOL and got removed from the repo.
Please ensure your system use a supported kernel mhwd-kernel -l
KERNELS REMOVED
Linux 6.9 and 6.10 have been removed from repo.
2024-10-10
Steam games may not launch
Those who have issues with steam games may check this thread for help: Steam games won't launch after 2024-10-10 stable update
Electron apps may crash and flatpak apps may not start
It got reported that electron apps may crash. Also flatpaks might not work. Most likely fixed via adwaita-icon-theme-legacy 46.2-3. More information about it here
2024-10-01
Introducing linux-meta package to deal with EOL kernels more automated
Since we got several reports about issues around linux69 removal we created meta packages called linux-meta and packages for the extramodules. It will detect end of life Kernels and replace them with the current recommended kernel. For now with linux610 series. Please report back if you have any issues with this provided solution.
Users with Nvidia graphic cards may get unbootable systems into graphical environments
Since we removed the linux69 kernel from our repositories and most users will use pamac to update their systems, there is a chance that you may land in a TTY after you reboot your system. Here is why:
- pamac has an auto-conflict resolution and might have put the linux69-nvidia package on the removal list.
- you only had linux69 as your kernel installed, since it got shipped by default in Manjaro 24.0 ISOs
- you rebooted your system without noticing that possible issue
How to fix:
- first donât panic and log in to your TTY with your user name and password
- then install a kernel like 6.6 LTS or 6.10 to your system via:
sudo mhwd-kernel -i linux66 or sudo mhwd-kernel -i linux610
- then install the nvidia drivers via:
sudo mhwd --auto pci ${DRIVER} 0300
VirtualBox: might show an error message after update to 7.1
You may have an error message like this: Failed to acquire the VirtualBox COM object. The application will now terminate.Callee RC%3ANS_ERROR_FAILURE (0x80004005). Simply restart the application
Random QML widgets and System Settings pages failing to launch in Plasma settings
⊠until Qtâs QML cache folder is cleared (if you do this, please save it first and attach it to the bug report).
System freeze on suspend
A feature in systemd 256 freezing a user session when suspending may freeze the system.
The issue is most prominent with Nvidia systems but reports exist that it may affect other systems as well.
System freezes for 60 seconds and then wakes back up or hangs after waking up
Since systemd v256, systemd freezes user.slice before sleeping. This process can fail due to kernel bugs, particularly when KVM is in use.[13][14]
Messages in the logs will contain Failed to freeze unit 'user.slice' before sleep. When such an issue occurs, trying to login (start another session) would fail with pam_systemd(process:session): Failed to create session: Job 9876 for unit 'session-6.scope' failed with 'frozen'.
To temporarily revert back to the old behavior, edit systemd-suspend.service, systemd-hibernate.service, systemd-hybrid-sleep.service, and systemd-suspend-then-hibernate.service with the following drop-in:
[Service]
Environment="SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=false"
â Power management/Suspend and hibernate - ArchWiki
KDE Plasma hangs on Shutdown, Restart and Logout
With KDE Plasma 6.1, the session saving feature can make Plasma hang.
A workaround is to disable it in System settings > Session > Desktop Session, by choosing âStart with an empty sessionâ.
Session auto login can't be re-enabled for X11
Once session auto login for X11 gets disabled, it canât be re-enabled in settings.
A workaround is to edit the /etc/sddm.conf.d/kde_settings.conf file and replace Session=Plasma (X11) by Session=plasma
2024-09-09
Added by @linux-arhus
System freeze on suspend
A feature in systemd 256 freezing a user session when suspending may freeze the system.
The issue is most prominent with Nvidia systems but reports exist that it may affect other systems as well.
System freezes for 60 seconds and then wakes back up or hangs after waking up
Since systemd v256, systemd freezes user.slice before sleeping. This process can fail due to kernel bugs, particularly when KVM is in use.[13][14]
Messages in the logs will contain Failed to freeze unit 'user.slice' before sleep. When such an issue occurs, trying to login (start another session) would fail with pam_systemd(process:session): Failed to create session: Job 9876 for unit 'session-6.scope' failed with 'frozen'.
To temporarily revert back to the old behavior, edit systemd-suspend.service, systemd-hibernate.service, systemd-hybrid-sleep.service, and systemd-suspend-then-hibernate.service with the following drop-in:
[Service]
Environment="SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=false"
â Power management/Suspend and hibernate - ArchWiki
2024-08-20
Some GTK apps on Gnome suddenly changed to other (bright) theme
The adw-gtk3 package is now called adw-gtk-theme which replaces the old adw-gtk-theme.
With that change, you may need to set Legacy Applications to Adw-gtk3-dark in the Tweaks application under Appearance. It may have been set to the now removed Adw-dark previously.
2024-08-08
pipewire-pulse conflicts with pulseaudio-ctl
pulseaudio-ctl is not compatible with PipeWire and should be removed:
pamac remove pulseaudio-ctl
Noisetorch from Extra repository cannot be updated
noisetorch on AUR has been updated to change pulseaudio dependency to pulse-native-provider
A similar change has not been implemented for repository package yet, so pipewire-pulse users may need to remove package before update
pamac remove noisetorch
Noisetorch 0.12.2-4 with pulse-native-provider dependency has been released to all Manjaro branches - Branch compare for Manjaro - noisetorch
2024-07-01
The sshd service needs to be restarted after upgrading to openssh-9.8p1
2024-07-01 - Robin Candau
After upgrading to openssh-9.8p1, the existing SSH daemon will be unable to accept new connections (see Can't login after openssh 9.8p1-1 upgrade, MUST restart sshd (#5) · Issues · Arch Linux / Packaging / Packages / openssh · GitLab).
When upgrading remote hosts, please make sure to restart the sshd service using systemctl try-restart sshd right after upgrading.
We are evaluating the possibility to automatically apply a restart of the sshd service on upgrade in a future release of the openssh-9.8p1 package.
â Arch Linux - News: The sshd service needs to be restarted after upgrading to openssh-9.8p1
Virtual machines using libvirt have no internet if the host uses UFW
This is a known bug. âWorkaroundâ is to change the firewall with firewalld or to disable UFW.
Another easier workaround is to edit /etc/libvirt/network.conf, and add
firewall_backend = "iptables"
2024-05-14
No plasma interface with kernel 6.9 + Nvidia gpu + Wayland
If you encouter a black screen with no inteface after login in, itâs probably a problem with simpledrm loading.
To solve it add nvidia_drm.fbdev=1 to /etc/default/grub
in the line begining with GRUB_CMDLINE_LINUX=" .
Verify that you also have nvidia_drm.modeset=1 in the same line.
Then exec sudo update-grub
Also, verify that you have nvidia_drm in /etc/mkinitcpio.conf in the MODULES= or HOOKS= line.
Exemple :
MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm)
If it was not present, then run sudo mkinitcpio -P after adding it.
2024-05-13
Python interpreter upgrade
If you have a lot of pip/AUR packages to upgrade to Python 3.12, read this.
If you installed python312 from the AUR, you need to uninstall it before running this update.
Qemu: MacOS is not bootable with 9.0
Due to a bug MacOS is not bootable with 9.0: [9.0.0] qemu breaks mac os vm (#2334) · Issues · QEMU / QEMU · GitLab
Workaround: remove virtio-serial and org.qemu.guest_agent.0 from libvirt XML until bug will be fixed.
If you use KDE you better logout of your session and do the update via Pacman or Pamac in tty.
Helper script to reset plasma Manjaro-Plasma-Reset/manjaro-plasma-reset.sh at main - wonky/Manjaro-Plasma-Reset - Codeberg.org @liinux-aarhus
Also I would, before the update:
- make a Timeshift snapshot if you ainât got no recent one.
- ( export content of widgets like your radio stations in Advanced Radio Player or your Podcasts in Kasts or any podcatcher as a backup )
- make a fresh boot, but before that even:
- System Settings > Appearance > Global Theme > set to Breath and tick both options for defaults
- You might go to the hamburger menu in System Settings and look what changes you made away from default by selecting: Highlight Changed Settings and see if you want to make the effort to get back more defaults
- System Settings > Workspace > Startup and Shutdown: SDDM defaults and Desktop Session: Start with empty session
- disable all user-installed widgets that are still on your desktop, panels and even lock screen or wallpaper (e.g. Active Blur)
- Export your custom shortcuts or mouse gestures in SS> Workspace > Shortcuts
- Reboot, Timeshift snapshot, reboot
- then do not log in, do the update via tty (CTRL+ALT+F3, same with F2 gets you back)
- reboot, login, check through System Settings
- reboot again
- enjoy 8)
post-install:
- look for Plasma 6 replacements for your widgets after the install
- in case you have Github-installed theming: uninstall the KDE5-version of klassy, install the Plasma 6 version of klassy, maybe reinstall lightly
(greetings, @1efaf7d71a8637c6800a , PS: these are just my thoughts; I didnât do this update yet!)
How to fix `plasma-firewall` error in System Settings GUI when running `ufw`
Open /usr/lib/kde_ufw_plugin_helper.py and change the first line from #!/usr/bin/python3.11 to #!/usr/bin/python3.12. This fixed the issue for me immediately and makes sense since Manjaro is currently on Python 3.12.
Xfce has inconsistent themes for Qt applications
Qt 6 is now default but some apps are still using Qt 5
To restore the look of QT apps after this update
pamac install kvantum-qt5
Manjaro-settings-manager has light theme instead of dark
2024-04-04
DKMS fails for v4l2loopback on 6.8 kernel
DKMS fails for v4l2loopback on 6.8 kernel (#2) · Issues · Arch Linux / Packaging / Packages / v4l2loopback · GitLab
issues with auto-mount of ntfs filesystem using Kernel 6.8
The kernel changed default ntfs driver from FUSE one to ntfs3.
These two are not fully compatible, mainly as far as mount options go. If you have custom mount options in the fstab (or any other application, such as VeraCrypt) they need to be changed.
Symptoms:
Mount fails with: Device or resource busy
DMesg reports: Can't open blockdev
Solution:
Migrate your mount options. For me the changes were:
allow_other â umask=000default_permissions â [drop]user_id=1000 â uid=1000group_id=1000 â gid=1000
2024-03-06
gnome-keyring: ssh component is not included
ssh component is not included (#3) · Issues · Arch Linux / Packaging / Packages / gnome-keyring · GitLab
2024-02-21
plymouth update may cause black screens
With a newer version of plymouth than 22.02.122 you may experience an unbootable system with a black screen. This might be due to not having early KMS enabled. If you have an Nvidia GPU you could set nvidia_drm.modeset=1 nvidia_drm.fbdev=1 to the kernel parameters in your bootloader config to avoid the need of KMS. However, with Wayland around the corner, KMS will be needed.
To âfixâ the current problem, we have downgraded plymouth once again to have more time to find a proper solution to migrate most of your installations to a working state with newer plymouth versions.
sudo pacman -Syuu
Those who donât have issues can enjoy the newer version of plymouth.
Directions for adding kms to your system configuration and how you can help troubleshooting by providing some sysinfo, read more â Black Screen with Plymouth - Cause and Solution
polkit update might remove your local modified config
With polkit 124-1 there were changes made to etc/pam.d/polkit-1. So check if you made local changes to the file. See also: https://www.reddit.com/r/archlinux/comments/19bnj0i/comment/kit2v33/
bashrc-manjaro is now merged into bash
- Yes, replace
bashrc-manjaro with bash
- Please also compare your:
/etc/bash.bashrc
with the generated
/etc/bash.bashrc.pacsave
and retrofit all of your customisations as there was no .pacnew file generated.
- Same goes for
/etc/skel/.bashrc
pacman and pacman-contrib changes
pacman-contrib is now split out from pacman. If you have anything installed that depends on pacman-contrib, update (after you finished the Release Update) with:
sudo pacman -Syu pacman-contrib
2024-01-13
Initramfs image can be bigger on 6.7 kernel due to Nvidia GSP Boot firmware
We all known that kernel 6.7 is very feature rich. One of the features is the inclusion of Nvidiaâs GSP Boot firmware into Initramfs. However this will increase your image by 150 MB and the fallback image might be 240 MB in size. A way would be to remove kms from mkinitcpio.conf and redo your initramfs images. A discussion regarding that can be found at Arch Gitlab: kms hook increases the initramfs size heavily starting with 6.7 kernel (#238) · Issues · Arch Linux / Mkinitcpio / mkinitcpio · GitLab
To reduce size add fallback_options="-S autodetect -S kms" to /etc/mkinitcpio.d/linux67.preset
Making dbus-broker our default D-Bus daemon
2024-01-09 - Jan Alexander Steffens
We are making dbus-broker our default implementation of D-Bus, for improved performance, reliability and integration with systemd.
For the foreseeable future we will still support the use of dbus-daemon, the previous implementation. Pacman will ask you whether to install dbus-broker-units or dbus-daemon-units. We recommend picking the default.
For a more detailed rationale, please see our RFC 25.
â Arch Linux - News: Making dbus-broker our default D-Bus daemon
In some cases, however it is better to keep the legacy way. Here are some examples: Dbus-broker warnings
Previous stable update threads:
AUR (Arch User Repository) packages are neither supported by Arch nor Manjaro. Posts about them in Announcements topics are off-topic and will be flagged, moved or removed without warning.
