[Stable Update] 2024-11-30 - Kernels, Plasma, GNOME, COSMIC, LXQT, SYSTEMD

Hello community, here we have another set of package updates.

Current Promotions

  • Find out all about our current Gaming Laptop the Hero with Manjaro pre-installed from Spain!
  • Protect your personal data, keep yourself safe with Surfshark VPN: Get 4 months extra

Recent News

Previous News
Finding information easier about Manjaro

Finding information easier about Manjaro always has been a topic that needed to be solved. With our new search we have put all Manjaro data accessible in one place and divided by sections so it makes it easier to digest: News – Manjaro

image

Notable Package Updates

Additional Info

Nvidia driver downgrade

Nvidia drivers got downgraded to 550.100, therefore update with sudo pacman -Syuu. If you want to stay on the 555 driver series you may either switch to unstable or install nvidia-dkms via: sudo pacman -U https://mirror.easyname.at/manjaro/pool/overlay/nvidia-dkms-555.58.02-1-x86_64.pkg.tar.zst. More info about Nvidia drivers here:

555 release feedback & discussion - Linux - NVIDIA Developer Forums
550.78 release feedback & discussion thread - Linux - NVIDIA Developer Forums

Python 3.12 info

:information_source: You will need to rebuild any AUR Python packages that install files to site-packages or link to libpython3.11.so. :information_source:

Print a list of of packages that have files in /usr/lib/python3.11/ :

pacman -Qoq /usr/lib/python3.11/

Rebuild them all at once:*

pamac build $(pacman -Qoq /usr/lib/python3.11)

* Note that if any fail to build, you’ll have to rebuild what’s remaining one or a few at a time.

Use rebuild-detector to see if anything else needs to be rebuilt:

checkrebuild
Info about AUR packages

:warning: 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.

For help with AUR packages, please create a new topic in AUR and a helpful volunteer may be able to assist you.

Get our latest daily developer images now from Github: Plasma, GNOME, XFCE. You can get the latest stable releases of Manjaro from CDN77. Stable ISOs including this update are available for review here: Release 202412010210 · manjaro/release-review · GitHub


Our current supported kernels

  • linux419 4.19.324
  • linux54 5.4.286
  • linux510 5.10.230
  • linux515 5.15.173
  • linux61 6.1.119
  • linux66 6.6.63
  • linux611 6.11.10
  • linux612 6.12.1
  • linux61-rt 6.1.112_rt43
  • linux66-rt 6.6.53_rt44
  • linux610-rt 6.10.2_rt14

Package Changes (Thu Nov 28 03:30:47 CET 2024)

  • stable core x86_64: 104 new and 111 removed package(s)
  • stable extra x86_64: 6329 new and 6338 removed package(s)
  • stable multilib x86_64: 70 new and 84 removed package(s)

A 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:


16 Likes

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:

:arrow_right: 2024-11-30

Plasma 6.2 might create a black screen when using X11 and default theme

For a while we are tracking the following bug of Plasma 6.2: 483163 – Sometimes on X11 with compositing turned on, black lock screen when using Breeze Plasma style, but controls are all there and remain interactive. There seems to be a regression when using X11 and the default theme breeze. A workaround is to use some other variant of Breeze or use Wayland. People who have issues could comment on that bug report in a polite and helpful way, so the KDE developers may fix it soon.

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

:warning: Linux 6.10 is EOL

Linux 6.10 is EOL and got removed from the repo.

Please ensure your system use a supported kernel mhwd-kernel -l

:zap: 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

:information_source: 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=000
  • default_permissions → [drop]
  • user_id=1000 → uid=1000
  • group_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:

3 Likes

Just updated on Cinnamon, with kernel 6.11 on a laptop with AMD and Nvidia, no issues, flawless update.

Cinnamon 6.4 seems real smooth.

:+1:

1 Like

I’m getting this error when I try to pacman -Syu:

mutter46-46.5-1 and mutter-47.2-1 are in conflict

Spectacle crashes after update, but it works if I remove libva-vdpau-driver.

To confirm, is it safe to remove libva-vdpau-driver on a KDE-wayland-nvidia system ? Thanks.

https://bugs.kde.org/show_bug.cgi?id=481977

Spectacle log without libva-vdpau-driver :

$ journalctl -r --grep=spectacle 
Nov 30 19:39:52 workstation systemd[835]: app-org.kde.spectacle.service: Consumed 456ms CPU time, 191.4M memory peak.
Nov 30 19:39:50 workstation systemd[835]: Started Spectacle screenshot capture utility.
Nov 30 19:39:50 workstation systemd[835]: Starting Spectacle screenshot capture utility...

Spectacle log with lbva-vdpau-driver :

$ journalctl -r --grep=spectacle                                                                                                                                                                      
Nov 30 18:33:32 workstation systemd[835]: Failed to start Spectacle screenshot capture utility.
Nov 30 18:33:32 workstation systemd[835]: app-org.kde.spectacle.service: Failed with result 'core-dump'.
Nov 30 18:33:32 workstation systemd[835]: app-org.kde.spectacle.service: Main process exited, code=dumped, status=11/SEGV
Nov 30 18:33:32 workstation systemd-coredump[3115]: [🡕] Process 3108 (spectacle) of user 1000 dumped core.
                                                    
                                                    Stack trace of thread 3113:
                                                    #0  0x000072d3bf0e6514 XDisplayString (libX11.so.6 + 0x27514)
                                                    #1  0x000072d39c6fad00 __vaDriverInit_1_21 (nvidia_drv_video.so + 0xdd00)
                                                    #2  0x000072d3bd170064 vaInitialize (libva.so.2 + 0x8064)
                                                    #3  0x000072d3c1ae8589 _ZN10VaapiUtils10openDeviceEPiRK10QByteArray (libKPipeWire.so.6 + 0x1c589)
                                                    #4  0x000072d3c1ae8b22 _ZNK10VaapiUtils12supportsH264ERK10QByteArray (libKPipeWire.so.6 + 0x1cb22)
                                                    #5  0x000072d3c1ae8cd5 _ZN10VaapiUtilsC1ENS_7PrivateE (libKPipeWire.so.6 + 0x1ccd5)
                                                    #6  0x000072d3c1ae8e98 _ZN10VaapiUtils8instanceEv (libKPipeWire.so.6 + 0x1ce98)
                                                    #7  0x000072d3c7c747af _ZNK25PipeWireBaseEncodedStream17suggestedEncodersEv (libKPipeWireRecord.so.6 + 0xd7af)
                                                    #8  0x000072d3c7c74f3c _ZN25PipeWireBaseEncodedStreamC1EP7QObject (libKPipeWireRecord.so.6 + 0xdf3c)
                                                    #9  0x000072d3c7c77d86 _ZN14PipeWireRecordC2EP7QObject (libKPipeWireRecord.so.6 + 0x10d86)
                                                    #10 0x000060571de1d3f1 n/a (spectacle + 0xc93f1)
                                                    #11 0x000060571de2401b n/a (spectacle + 0xd001b)
                                                    #12 0x000072d3c26dec15 n/a (libQt6Core.so.6 + 0x2dec15)
                                                    #13 0x000072d3c26d840f n/a (libQt6Core.so.6 + 0x2d840f)
                                                    #14 0x000072d3c1ea339d n/a (libc.so.6 + 0x9439d)
                                                    #15 0x000072d3c1f2849c n/a (libc.so.6 + 0x11949c)
                                                    
                                                    Stack trace of thread 3109:
                                                    #0  0x000072d3c1f1abb0 ppoll (libc.so.6 + 0x10bbb0)
                                                    #1  0x000072d3be67d227 n/a (libglib-2.0.so.0 + 0xc0227)
                                                    #2  0x000072d3be619a55 g_main_context_iteration (libglib-2.0.so.0 + 0x5ca55)
                                                    #3  0x000072d3c27bf71d _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3bf71d)
                                                    #4  0x000072d3c2564566 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x164566)
                                                    #5  0x000072d3c2657072 _ZN7QThread4execEv (libQt6Core.so.6 + 0x257072)
                                                    #6  0x000072d3c4f7379e n/a (libQt6DBus.so.6 + 0x2e79e)
                                                    #7  0x000072d3c26d840f n/a (libQt6Core.so.6 + 0x2d840f)
                                                    #8  0x000072d3c1ea339d n/a (libc.so.6 + 0x9439d)
                                                    #9  0x000072d3c1f2849c n/a (libc.so.6 + 0x11949c)
                                                    
                                                    Stack trace of thread 3110:
                                                    #0  0x000072d3c1e9fa19 n/a (libc.so.6 + 0x90a19)
                                                    #1  0x000072d3c1ea2479 pthread_cond_wait (libc.so.6 + 0x93479)
                                                    #2  0x000072d3c26dd030 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x2dd030)
                                                    #3  0x000072d3c596e3af n/a (libQt6WaylandClient.so.6 + 0x5f3af)
                                                    #4  0x000072d3c26d840f n/a (libQt6Core.so.6 + 0x2d840f)
                                                    #5  0x000072d3c1ea339d n/a (libc.so.6 + 0x9439d)
                                                    #6  0x000072d3c1f2849c n/a (libc.so.6 + 0x11949c)
                                                    
                                                    Stack trace of thread 3111:
                                                    #0  0x000072d3c1f1a63d __poll (libc.so.6 + 0x10b63d)
                                                    #1  0x000072d3c596e417 n/a (libQt6WaylandClient.so.6 + 0x5f417)
                                                    #2  0x000072d3c26d840f n/a (libQt6Core.so.6 + 0x2d840f)
                                                    #3  0x000072d3c1ea339d n/a (libc.so.6 + 0x9439d)
                                                    #4  0x000072d3c1f2849c n/a (libc.so.6 + 0x11949c)
                                                    
                                                    Stack trace of thread 3108:
                                                    #0  0x000072d3c1f1d8dc fdatasync (libc.so.6 + 0x10e8dc)
                                                    #1  0x000072d3c2527bdd _ZN9QLockFile7tryLockENSt6chrono8durationIlSt5ratioILl1ELl1000EEEE (libQt6Core.so.6 + 0x127bdd)
                                                    #2  0x000072d3c2527ef7 _ZN9QLockFile7tryLockENSt6chrono8durationIlSt5ratioILl1ELl1000EEEE (libQt6Core.so.6 + 0x127ef7)
                                                    #3  0x000072d3c2527ef7 _ZN9QLockFile7tryLockENSt6chrono8durationIlSt5ratioILl1ELl1000EEEE (libQt6Core.so.6 + 0x127ef7)
                                                    #4  0x000072d3c58ce2f5 n/a (n/a + 0x0)
                                                    #5  0x000072d3c58bab62 n/a (n/a + 0x0)
                                                    #6  0x000060571dda4186 n/a (spectacle + 0x50186)
                                                    #7  0x000060571dda9256 n/a (spectacle + 0x55256)
                                                    #8  0x000060571de9a55f n/a (spectacle + 0x14655f)
                                                    #9  0x000060571dde086d n/a (spectacle + 0x8c86d)
                                                    #10 0x000060571de9d908 n/a (spectacle + 0x149908)
                                                    #11 0x000060571dd9c3e2 n/a (spectacle + 0x483e2)
                                                    #12 0x000072d3c1e34e08 n/a (libc.so.6 + 0x25e08)
                                                    #13 0x000072d3c1e34ecc __libc_start_main (libc.so.6 + 0x25ecc)
                                                    #14 0x000060571dd9fd55 n/a (spectacle + 0x4bd55)
                                                    ELF object binary architecture: AMD x86-64
Nov 30 18:33:32 workstation systemd-coredump[3114]: Process 3108 (spectacle) of user 1000 terminated abnormally with signal 11/SEGV, processing...
Nov 30 18:33:32 workstation systemd[835]: Starting Spectacle screenshot capture utility...

System summary :

$ inxi -zv1                                                                                                                                                                                                   
System:
  Kernel: 6.12.1-4-MANJARO arch: x86_64 bits: 64
  Desktop: KDE Plasma v: 6.2.4 Distro: Manjaro Linux
CPU:
  Info: 6-core 12th Gen Intel Core i5-12400F [MT MCP] speed (MHz): avg: 800
    min/max: 800/4400
Graphics:
  Device-1: NVIDIA GA104 [GeForce RTX 3070 Ti] driver: nvidia v: 550.135
  Display: wayland server: X.org v: 1.21.1.14 with: Xwayland v: 24.1.4
    compositor: kwin_wayland driver: X: loaded: nvidia gpu: nvidia resolution:
    1: 2048x1152 2: 2048x1152
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.135
    renderer: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2
Drives:
  Local Storage: total: 1.86 TiB used: 70.7 GiB (3.7%)
Info:
  Memory: total: 32 GiB available: 31.14 GiB used: 5.6 GiB (18.0%)
  Processes: 358 Uptime: 21m Shell: Zsh inxi: 3.3.36

I’m getting this message when trying to update through pacman -Syu and pamac update

error: failed to prepare transaction (could not satisfy dependencies)
:: installing expat (2.6.4-1) breaks dependency 'expat=2.6.3' required by lib32-expat
:: installing libcap (2.71-1) breaks dependency 'libcap=2.70' required by lib32-libcap
:: installing libelf (0.192-2) breaks dependency 'libelf=0.191' required by lib32-libelf
:: installing ppp (2.5.1-1) breaks dependency 'ppp=2.5.0' required by networkmanager-l2tp
:: installing ppp (2.5.1-1) breaks dependency 'ppp=2.5.0' required by networkmanager-pptp

After the update, Manjaro would not restart. Error was at systemd startup “nvidia-persistance [
]”. Then it stopped few lines later.

Had to enter grub menu, edit the grub parameters by adding a " 3" after the linux boot parameter. Then I started in the console, logged in and restored with Timeshift.

God bless Timeshift! :hugs:

1 Like

@JPL, you may want to check via pacman -Qi mutter46 why you might have installed this package. Normally it is a dependency of these packages: gala, lightdm-pantheon-greeter, wingpanel

@rousseau: libva-vdpau-driver got removed from the repos and is therefore orphan. It is save to remove it. libva is now provided by mesa.

@Kyoketsu9513 networkmanager-pptp 1.2.12-4 and networkmanager-l2tp 1.20.16-2 are fine with ppp 2.5.1. So your mirrorlist might not been updated. Check that and try again.

@Humbi your issue sounds like this one: [SOLVED]Nvidia Persistence Daemon fails to start / Newbie Corner / Arch Linux Forums. This update normally removes linux610 kernel. You can check first if you have all modules of nvidia drivers installed for the newer kernel. You also can install an older kernel like 6.6. You can check with pacman -Q | grep nvidia on what is installed Nvidia related on your system.

3 Likes

If I type in terminal “pacman -Syyu” it says “nothing to update”. It is normally?

Yes, just wait a bit until your mirrors have updated.

2 Likes

The correct command would be:

sudo pacman -Syu

Don’t use a double-y. I’ve heard it can cause problems and it thrashes the servers if you do it unnecessarily. Rather just be patient.

2 Likes

The correct Firefox version is 133.0.
Firefox 132 got passed over.

@Marsa thx. I’ve double-checked the release versions and corrected the list.

1 Like

Do you use dark mode or light mode? Several apps default to dark mode after the update regardless of the setting in preferences. They only swap to light mode if I toggle the setting. The novelty is already wearing off.

Everything worked fine on my side.
pacman remove -o now lists several packages to remove. Is it safe to do that? I feel like it would remove too much, I have kernel 6.11 still installed.

To remove (15):
v86d 0.1.10-13
python-validate-pyproject 0.22-1 extra
python-fastjsonschema 2.20.0-1 (Orphan Of: python-validate-pyproject) extra
python-trove-classifiers 2024.10.21.16-1 (Orphan Of: python-validate-pyproject) extra
python-tomli 2.0.1-4 extra
linux-meta 6.11-1 core
libgusb 0.4.9-1 extra
python-ordered-set 4.1.0-5 extra
libsoup 2.74.3-1 extra
linux-headers-meta 6.11-1 core
linux611-headers 6.11.10-2 (Orphan Of: linux-headers-meta) core
linux-nvidia-meta 6.11-1 extra
linux611-nvidia 550.135-3 (Orphan Of: linux-nvidia-meta) extra
linux-virtualbox-host-modules-meta 6.11-1 extra
lua52 5.2.4-7 extra

Total removed size: 202,3 MB

But actually, I don’t need kernel 6.11 anymore. I tried to remove it via the Manjaro settings. It says it can’t uninstall that because of dependencies:

Starting

checking dependencies


:: removing linux611-headers breaks dependency ‘linux611-headers’ required by linux-headers-meta

:: removing linux611 breaks dependency ‘linux611’ required by linux-meta

:: removing linux611-nvidia breaks dependency ‘linux611-nvidia’ required by linux-nvidia-meta

:: removing linux611-virtualbox-host-modules breaks dependency ‘linux611-virtualbox-host-modules’ required by linux-virtualbox-host-modules-meta

I think the root problem of both is the same.

The linux-meta packages get installed when we drop a kernel from the repos. In this case 6.10 series got dropped. You can remove the meta packages with the kernel packages it installed for you. More information about it here: Find a proper solution to automate EOL kernel removal via ALPM (#13) · Issues · Release plan / Packaging · GitLab

1 Like

Pamac somehow crashed (gui disappeared) twice during update-download so I used pacman instead and it worked flawlessly.

1 Like

It is recommended to use the cli tools for bigger updates on GNOME and Plasma. The newer pamac might be more robust in that regard.

2 Likes

The only thing that broke is dino, a xmpp client, version 0.4.4-1 It does not start and gives the following message when

(dino:3264): Adwaita-WARNING **: 10:22:03.434: Using GtkSettings:gtk-application-prefer-dark-theme with libadwaita is unsupported. Please use AdwStyleManager:color-scheme instead.

followed by some gstreamer errors.

System info:

System:
Kernel: 6.11.10-2-MANJARO arch: x86_64 bits: 64
Desktop: KDE Plasma v: 6.2.4 Distro: Manjaro Linux
CPU:
Info: 8-core AMD Ryzen 7 7800X3D [MT MCP] speed (MHz): avg: 3599
min/max: 545/5050
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 32 [Radeon RX 7700 XT /
7800 XT] driver: amdgpu v: kernel
Device-2: Advanced Micro Devices [AMD/ATI] Raphael driver: amdgpu
v: kernel
Display: wayland server: X.org v: 1.21.1.14 with: Xwayland v: 24.1.4
compositor: kwin_wayland driver: X: loaded: amdgpu
unloaded: modesetting,radeon dri: radeonsi gpu: amdgpu,amdgpu
resolution: 3072x1728
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.2.7-arch1.1
renderer: AMD Radeon RX 7800 XT (radeonsi navi32 LLVM 18.1.8 DRM 3.59
6.11.10-2-MANJARO)

You can check your GTK settings and remove the preffered dark theme flag. With GNOME 47 release accent colours got added. That got also updated in gtk3 and gtk4 packages.