[Stable Update] 2025-03-18 - Kernel, Systemd, Plasma 6.3.3, KDE Gear 24.12.3

Hello community, here we have another set of package updates. I’m now back in Europe. However, since I still need to settle down I may not respond much in this forum until I find time again for it. Anyhow, here we have the updates. Please check also in our last Testing update for known issues.

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: See current promotion

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

Python 3.13 info

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

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

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

Rebuild them all at once:*

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

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

 checkrebuild

* It’s recommended to clean your build cache first with pamac clean --build-files

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.


Our current supported kernels

  • linux54 5.4.290
  • linux510 5.10.234
  • linux515 5.15.178
  • linux61 6.1.130
  • linux66 6.6.82
  • linux612 6.12.18
  • linux613 6.13.6
  • linux614 6.14.0-rc6
  • linux66-rt 6.6.78_rt51
  • linux612-rt 6.12.16_rt9
  • linux613-rt 6.13_rt5

Package Changes (Wed Mar 12 15:24:00 CET 2025)

  • stable core x86_64: 51 new and 52 removed package(s)
  • stable extra x86_64: 2854 new and 2975 removed package(s)
  • stable multilib x86_64: 33 new and 28 removed package(s)

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


13 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: 2025-03-18

2025-03-05

[community] repo removed from servers

Similar to Arch we removed our [community] repos from our mirrors and servers. You may want to check your pacnew files or manually remove [community] and [kde-unstable] when used in your /etc/pacman.conf file.

2025-02-16

Update only regular repository packages first, no AUR

Follow the best practice of first updating only regular repository packages, followed separately by AUR packages.

  1. Update regular repository packages first with
    • pamac update --no-aur
      or
    • sudo pacman -Syu
  2. Then, if needed, update AUR packages.

Failure to follow this practice may result in the installation of packages that you may not need, and may cause problems. For further details, see:

Keyboard layout issues / Update issues with fcitx5

If a system had sdl2 installed and AUR updates enabled, fcitx5 might be installed as a make dependency

It is recommended to remove fcitx5 and any other orphan packages following the update

pamac remove --orphans

Update issues with fcitx5

2025-02-04

Kernel 4,19 and 6.11 are EOL, 6.11 and 4.19 got removed from repos

Kernel 6.11 and 4.19 got marked [EOL] on kernel.org
Linux 6.11 and 4.19 have been removed from the repositories.
Please ensure your system use a supported kernel mhwd-kernel -l

PostgreSQL users should consider to prepare the change of major version 16→17

More info here and here

Update libpamac before installing the 2025-02-04 updates

Run sudo pacman -Sy libpamac in a terminal to make sure pamac-manager doesn’t crash during the update.

XFCE 4.20 may blank display after 5 mins idle time regardless of power management settings

Most likely this: Disable screen blanking

Call xfce4-screensaver-preferences and disable the screensaver.
xfce4-screensaver - Usage [Xfce Docs]

2024-12-16

Linux-Meta packages may prevent removal of linux611

Since we introduced the new meta packages to remove EOL kernels, as soon as we drop them from our repos, the newly EOLed linux611 kernel might be prevented to be removable due to possible installation of them when linux610 got removed.

If you want to remove the kernel now, please add modules like linux-meta and linux-nvidia-meta to your removal list.

Example:

sudo pacman -R linux611 linux611-nvidia linux-meta linux-nvidia-meta

More fancier cmd:

sudo pacman -Rns $(pacman -Qq linux611 | sed ‘s/611//’ | sed -e ‘s/$/-meta/’) $(pacman -Qq linux611)

You can find more information about it here: Find a proper solution to automate EOL kernel removal via ALPM (#13) · Issues · Release plan / Packaging · GitLab

Critical rsync security release 3.4.0

2025-01-16 - Robin Candau

We’d like to raise awareness about the rsync security release version 3.4.0-1 as described in our advisory ASA-202501-1.

An attacker only requires anonymous read access to a vulnerable rsync server, such as a public mirror, to execute arbitrary code on the machine the server is running on. Additionally, attackers can take control of an affected server and read/write arbitrary files of any connected client. Sensitive data can be extracted, such as OpenPGP and SSH keys, and malicious code can be executed by overwriting files such as ~/.bashrc or ~/.popt.

We highly advise anyone who runs an rsync daemon or client prior to version 3.4.0-1 to upgrade and reboot their systems immediately. As Arch Linux mirrors are mostly synchronized using rsync, we highly advise any mirror administrator to act immediately, even though the hosted package files themselves are cryptographically signed.

All infrastructure servers and mirrors maintained by Arch Linux have already been updated.

Arch Linux - News: Critical rsync security release 3.4.0

2024-12-06

Nvidia 470xx driver may cause black screen and cursor on Plasma with Wayland

When you try to use Wayland with the Nvidia 470xx driver you may have an activated a ghost screen, which leads to a so called ghost screen.

You can still use the right-click context menu and go to screen settings. Choose your other screen as primary and deactivate your ghost screen. Else you can use X11, which should not have that issue. More information about it here: Help testing Nvidia drivers with Kernel 6.12 - #20 by Arrababiski

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: Making sure you're not a bot!. 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 is EOL, 6.10 and 6.9 removed from repos

Kernel 6.10 has been marked [EOL] on kernel.org
Linux 6.9 and 6.10 have been removed from the repositories.
Please ensure your system use a supported kernel mhwd-kernel -l

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

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

Previous stable update threads:

The update was successful, but the fallback image generation failed at the end of the update (fortunately, not the regular image).

==> Building image from preset: /etc/mkinitcpio.d/linux612.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.12-x86_64 -g /boot/initramfs-6.12-x86_64.img
==> Starting build: '6.12.19-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [microcode]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [block]
  -> Running build hook: [mdadm_udev]
Custom /etc/mdadm.conf file will be used in initramfs for assembling arrays.
  -> Running build hook: [zfs]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
  -> Running build hook: [plymouth]
  -> Running build hook: [resume]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.12-x86_64.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux612.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.12-x86_64 -g /boot/initramfs-6.12-x86_64-fallback.img -S autodetect
==> Starting build: '6.12.19-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [microcode]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
==> WARNING: Possibly missing firmware for module: 'ast'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'wd719x'
  -> Running build hook: [mdadm_udev]
Custom /etc/mdadm.conf file will be used in initramfs for assembling arrays.
  -> Running build hook: [zfs]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
  -> Running build hook: [plymouth]
  -> Running build hook: [resume]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.12-x86_64-fallback.img'
  -> Early uncompressed CPIO image generation successful
bsdtar: Error reading archive -: Damaged tar archive (bad header checksum)
bsdtar: Error exit delayed from previous errors.
==> ERROR: Initcpio image generation FAILED: 'bsdtar (step 2)' reported an error

It turned out that my ESP was 100% full (the ESP size is 512 Mb). To make it work, I had to disable fallback in /etc/mkinitcpio.d/linux612.preset.
The growing kernel size really makes the traditional 512 Mb ESP obsolete…

Another faultless update. 0 pacnew files. Thanks.

3 Likes

Pipewire maxes out a single CPU thread with this update on an ASUS laptop. I’ve solved it by installing manjaro-pulse and running

sudo systemctl disable --global pipewire  

Not a difficult fix. But I must say I’m sick to death of pipewire. I run into something different with it on every single system I use, whether its XFCE, KDE or Gnome, whatever the hardware.

8 Likes

After the update my sound was gone, only showed dummy output in setting>sound. I rolled back with snapshot, all working again. Will this pipewire command fix the issue if I update again?
Stretched for time now, will try again tomorrow.

1 Like

Update without problems.
Thanks!
KDE+kernel 6.12
XFCE+kernel 6.12

1 Like

Xfce, all fine as usual.

I had the following orphan: appstream-glib.
For curiosity I examinated pacman.log, and I discovered that, over the years, this package has been upgraded/installed/removed many times:

cat /var/log/pacman.log | grep -ae "installed appstream-glib" -e "upgraded appstream-glib" -e "removed appstream-glib"
[2019-03-13 13:57] [ALPM] upgraded appstream-glib (0.7.14-1 -> 0.7.15-1)
[2019-10-16 13:33] [ALPM] upgraded appstream-glib (0.7.15-1 -> 0.7.16-1)
[2019-11-05 09:24] [ALPM] upgraded appstream-glib (0.7.16-1 -> 0.7.16-2)
[2020-03-03T13:43:01+0100] [ALPM] upgraded appstream-glib (0.7.16-2 -> 0.7.17-1)
[2020-09-12T14:36:27+0200] [ALPM] upgraded appstream-glib (0.7.17-1 -> 0.7.18-1)
[2020-12-25T15:40:47+0100] [ALPM] upgraded appstream-glib (0.7.18-1 -> 0.7.18-2)
[2021-07-15T12:14:41+0200] [ALPM] upgraded appstream-glib (0.7.18-2 -> 0.7.18-3)
[2022-07-30T10:59:55+0200] [ALPM] upgraded appstream-glib (0.7.18-3 -> 0.8.0-1)
[2022-08-13T10:44:55+0200] [ALPM] upgraded appstream-glib (0.8.0-1 -> 0.8.1-1)
[2022-11-14T12:53:28+0100] [ALPM] upgraded appstream-glib (0.8.1-1 -> 0.8.2-1)
[2023-08-25T21:09:43+0200] [ALPM] upgraded appstream-glib (0.8.2-1 -> 0.8.2-3)
[2023-08-25T22:02:03+0200] [ALPM] removed appstream-glib (0.8.2-3)
[2024-02-10T19:07:52+0100] [ALPM] installed appstream-glib (0.8.2-3)
[2024-02-22T01:19:36+0100] [ALPM] removed appstream-glib (0.8.2-3)
[2024-10-01T14:54:54+0200] [ALPM] installed appstream-glib (0.8.3-1)
[2024-10-01T14:57:47+0200] [ALPM] removed appstream-glib (0.8.3-1)
[2024-10-01T14:58:39+0200] [ALPM] installed appstream-glib (0.8.3-1)
[2024-10-01T15:00:45+0200] [ALPM] removed appstream-glib (0.8.3-1)
[2025-03-18T06:58:14+0100] [ALPM] installed appstream-glib (0.8.3-2)
[2025-03-18T14:06:06+0100] [ALPM] removed appstream-glib (0.8.3-2)

1 Like

Neither Youtube nor other video hosting sites play any videos after this update. Offline AVI files do play but there is no sound. Sound settings manager doesn’t play the test sounds. However, when I log in after restart, the initial greeting sound effect plays but after that there is no sound.

Edit:
I discovered that when I mute the sound on Youtube videos, they start to play, but as soon as I enable sound a loading indicator appears on the video. Also, I noticed that all sounds work properly in a 10-20 second window immediately after logging in. Then, something happens and sounds stop working.

When I change the output device in Sound application from Line Out to Digital Output and then back to Line out, then sound is restored for 10-20 seconds, but then gets muted again.

Solution:
Uninstalled pulseaudio packages that prevented me from installing manjaro-pipewire. Then, after having installed manjaro-pipewire, the sound started working after reboot.

13 Likes

Strange story here.

I have a docker pi-hole to manage my DNS

I did a first pamac update
It seemed to start as usual after calculating 4.2Go update.
Then, 10 sec later, it was suddendly stuck, no more web access.

I had to understand my pi-hole was kinda broken or non operative
After several box, system & docker restart, Web access again.

But !

➜  ~ pamac update                   
Préparation...
Synchronisation des bases de données des paquets...
Actualisation de chaotic-aur.db...                                                                                                                                                                                 
Actualisation de AUR...                                                                                                                                                                                            
Rien à faire.                                                                                                                                                                                                      
Transaction terminée avec succès.
➜  ~ pamac update
Préparation...

Synchronisation des bases de données des paquets...
Rien à faire.                                                                                                                                                                                                      
Transaction terminée avec succès.
➜  ~ sudo pacman -Syu
:: Synchronisation des bases de données de paquets…
 core est à jour
 extra est à jour
 multilib est à jour
 chaotic-aur est à jour
 warpdotdev est à jour
:: Début de la mise à jour complète du système…
 il n’y a rien à faire
➜  ~ 

The real issue there is that the update never happened !

  • Before these last commands I updated my mirrors with sudo pacman-mirrors --continent

How can I appear up to date, not having updated ?

[Edit] Uhh ! Am I back in the future ?

➜  ~ pacman -Q | grep "^linux[0-9]"
linux612 6.12.19-1
linux612-headers 6.12.19-1
linux612-virtualbox-host-modules 7.1.6-14
linux613 6.13.7-1
linux613-headers 6.13.7-1
linux613-virtualbox-host-modules 7.1.6-12
➜  ~```

I'm on stable, never been on testing nor unstable....

I think you mean /boot.
The ESP is in /boot/efi by default with Manjaro, should be on its own partition and only stores a few KB of data.
But /boot, where the kernels (and initramfs) go, can be on the same partition as /.
Keeping the fallback initramfs is a good idea if you change hardware at some point.

The fallback initramfs has increased from 80 MB with 6.6 to 130 MB with 6.12!

If you install manjaro-pulse, it will uninstall pipewire and use pulseaudio instead.
Then restart and check if the sound is back.

1 Like

Much like the last few updates, Manjaro boots to a completely black screen using kernels 6.13.7-1, and 6.12.19-1. Had to revert again to 6.6.83-1.

This time I have system information for you:

System:
  Kernel: 6.6.83-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.6-x86_64
    root=UUID=7361f228-1102-406f-93c9-8c30f3d4372e rw quiet splash apparmor=1
    security=apparmor udev.log_priority=3 nvidia_drm.modeset=1
  Desktop: Xfce v: 4.20.1 tk: Gtk v: 3.24.48 wm: xfwm4 v: 4.20.0
    with: xfce4-panel tools: light-locker vt: 7 dm: LightDM v: 1.32.0
    Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop Mobo: ASUSTeK model: Z170-A v: Rev 1.xx
    serial: <superuser required> part-nu: SKU uuid: <superuser required>
    UEFI-[Legacy]: American Megatrends v: 3802 date: 03/15/2018
Battery:
  Message: No system battery data found. Is one present?
Memory:
  System RAM: total: 16 GiB available: 15.56 GiB used: 2.36 GiB (15.2%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 64 GiB slots: 4 modules: 2 EC: None
    max-module-size: 16 GiB note: est.
  Device-1: ChannelA-DIMM1 type: DDR4 detail: synchronous size: 8 GiB
    speed: 2667 MT/s volts: curr: 1 width (bits): data: 64 total: 64
    manufacturer: Kingston part-no: KHX2666C15D4/8G serial: <filter>
  Device-2: ChannelA-DIMM2 type: no module installed
  Device-3: ChannelB-DIMM1 type: DDR4 detail: synchronous size: 8 GiB
    speed: 2667 MT/s volts: curr: 1 width (bits): data: 64 total: 64
    manufacturer: Kingston part-no: KHX2666C15D4/8G serial: <filter>
  Device-4: ChannelB-DIMM2 type: no module installed
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: Intel Core i7-6700K bits: 64 type: MT MCP arch: Skylake-S
    gen: core 6 level: v3 note: check built: 2015 process: Intel 14nm family: 6
    model-id: 0x5E (94) stepping: 3 microcode: 0xF0
  Topology: cpus: 1x dies: 1 clusters: 4 cores: 4 threads: 8 tpc: 2
    smt: enabled cache: L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB
    desc: 4x256 KiB L3: 8 MiB desc: 1x8 MiB
  Speed (MHz): avg: 800 min/max: 800/4200 scaling: driver: intel_pstate
    governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800
    8: 800 bogomips: 64026
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
    arch_capabilities arch_perfmon art avx avx2 bmi1 bmi2 bts clflush
    clflushopt cmov constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64
    dtherm dts epb ept ept_ad erms est f16c flexpriority flush_l1d fma fpu
    fsgsbase fxsr ht hwp hwp_act_window hwp_epp hwp_notify ibpb ibrs ida
    intel_pt invpcid lahf_lm lm mca mce md_clear mmx monitor movbe mpx msr
    mtrr nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq pdcm pdpe1gb pebs pge
    pln pni popcnt pse pse36 pti pts rdrand rdseed rdtscp rep_good sdbg sep
    smap smep ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm tm2
    tpr_shadow tsc tsc_adjust tsc_deadline_timer vme vmx vnmi vpid x2apic
    xgetbv1 xsave xsavec xsaveopt xsaves xtopology xtpr
  Vulnerabilities:
  Type: gather_data_sampling status: Vulnerable: No microcode
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
    vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: IBRS
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: IBRS; IBPB: conditional; STIBP: conditional;
    RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort mitigation: TSX disabled
Graphics:
  Device-1: NVIDIA GM204 [GeForce GTX 970] vendor: ASUSTeK driver: nvidia
    v: 550.144.03 alternate: nouveau,nvidia_drm non-free: 550/565.xx+
    status: current (as of 2025-01; EOL~2026-12-xx) arch: Maxwell code: GMxxx
    process: TSMC 28nm built: 2014-2019 pcie: gen: 1 speed: 2.5 GT/s lanes: 16
    link-max: gen: 3 speed: 8 GT/s ports: active: none off: DVI-I-1
    empty: DP-1,DVI-D-1,HDMI-A-1 bus-ID: 01:00.0 chip-ID: 10de:13c2
    class-ID: 0300
  Display: x11 server: X.Org v: 21.1.16 compositor: xfwm4 v: 4.20.0 driver:
    X: loaded: nvidia unloaded: modesetting alternate: fbdev,nouveau,nv,vesa
    gpu: nvidia,nvidia-nvswitch display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 678x382mm (26.69x15.04")
    s-diag: 778mm (30.64")
  Monitor-1: DVI-I-1 note: disabled model: Asus PB278 serial: <filter>
    built: 2015 res: mode: 2560x1440 hz: 60 scale: 100% (1) dpi: 109 gamma: 1.2
    chroma: red: x: 0.667 y: 0.329 green: x: 0.310 y: 0.631 blue: x: 0.149
    y: 0.039 white: x: 0.314 y: 0.329 size: 597x336mm (23.5x13.23")
    diag: 685mm (27") ratio: 16:9 modes: 2560x1440, 1920x1080, 1680x1050,
    1280x1024, 1440x900, 1280x960, 1280x800, 1152x864, 1280x720, 1024x768,
    800x600, 640x480
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia gbm:
    drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia inactive: wayland
  API: OpenGL v: 4.6.0 vendor: nvidia v: 550.144.03 glx-v: 1.4
    direct-render: yes renderer: NVIDIA GeForce GTX 970/PCIe/SSE2
    memory: 3.91 GiB
  API: Vulkan v: 1.4.304 layers: 3 device: 0 type: discrete-gpu
    name: NVIDIA GeForce GTX 970 driver: N/A device-ID: 10de:13c2
    surfaces: xcb,xlib
  Info: Tools: api: eglinfo, glxinfo, vulkaninfo de: xfce4-display-settings
    gpu: nvidia-settings,nvidia-smi x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel alternate: snd_soc_avs bus-ID: 00:1f.3
    chip-ID: 8086:a170 class-ID: 0403
  Device-2: NVIDIA GM204 High Definition Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 01:00.1 chip-ID: 10de:0fbb class-ID: 0403
  API: ALSA v: k6.6.83-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.4.1 status: off tools: pw-cli
  Server-3: PulseAudio v: 17.0-43-g3e2bb status: active
    with: pulseaudio-alsa type: plugin tools: pacat,pactl,pavucontrol
Network:
  Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15b8 class-ID: 0200
  IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IP v4: <filter> type: noprefixroute scope: global broadcast: <filter>
  Info: services: NetworkManager,systemd-timesyncd
  WAN IP: <filter>
Bluetooth:
  Message: No bluetooth data found.
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 3.64 TiB used: 899.23 GiB (24.1%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Sabrent model: Rocket Q
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: RKT30Q.1 temp: 25.9 C
    scheme: MBR
  ID-2: /dev/sda maj-min: 8:0 vendor: Seagate model: ST2000DM001-1ER164
    size: 1.82 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 7200 serial: <filter> fw-rev: CC25 scheme: MBR
  Optical-1: /dev/sr0 vendor: HL-DT-ST model: DVDRAM GH24NSC0 rev: LK00
    dev-links: cdrom
  Features: speed: 12 multisession: yes audio: yes dvd: yes
    rw: cd-r,cd-rw,dvd-r,dvd-ram state: running
Partition:
  ID-1: / raw-size: 1.82 TiB size: 1.79 TiB (98.37%) used: 899.23 GiB (49.1%)
    fs: ext4 dev: /dev/nvme0n1p1 maj-min: 259:1 label: N/A
    uuid: 7361f228-1102-406f-93c9-8c30f3d4372e
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: file size: 4 GiB used: 0 KiB (0.0%) priority: -2
    file: /swapfile
Unmounted:
  ID-1: /dev/sda1 maj-min: 8:1 size: 1.82 TiB fs: ntfs label: MM-storage
    uuid: 7DC123C74498A0AD
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 16 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 1-9:2 info: HP HyperX Alloy Core RGB type: keyboard,HID
    driver: hid-generic,usbhid interfaces: 4 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 500mA chip-ID: 03f0:0391 class-ID: 0300
  Device-2: 1-10:3 info: ASUSTek ROG GLADIUS III type: HID,mouse
    driver: hid-generic,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 100mA chip-ID: 0b05:197b class-ID: 0300
  Hub-2: 2-0:1 info: super-speed hub ports: 10 rev: 3.0
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-3: 3-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-4: 4-0:1 info: super-speed hub ports: 2 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 22.0 C mobo: N/A gpu: nvidia temp: 52 C
  Fan Speeds (rpm): N/A gpu: nvidia fan: 6%
Repos:
  Packages: pm: pacman pkgs: 1405 libs: 496 tools: pamac pm: flatpak pkgs: 0
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://cofractal-ewr.mm.fcix.net/manjaro/stable/$repo/$arch
    2: https://forksystems.mm.fcix.net/manjaro/stable/$repo/$arch
    3: https://coresite.mm.fcix.net/manjaro/stable/$repo/$arch
    4: https://mirror.math.princeton.edu/pub/manjaro/stable/$repo/$arch
    5: https://nnenix.mm.fcix.net/manjaro/stable/$repo/$arch
    6: https://nocix.mm.fcix.net/manjaro/stable/$repo/$arch
    7: https://mnvoip.mm.fcix.net/manjaro/stable/$repo/$arch
    8: https://ohioix.mm.fcix.net/manjaro/stable/$repo/$arch
    9: https://mirrors.gigenet.com/manjaro/stable/$repo/$arch
    10: https://southfront.mm.fcix.net/manjaro/stable/$repo/$arch
    11: https://volico.mm.fcix.net/manjaro/stable/$repo/$arch
    12: https://muug.ca/mirror/manjaro/stable/$repo/$arch
    13: https://irltoolkit.mm.fcix.net/manjaro/stable/$repo/$arch
    14: https://ziply.mm.fcix.net/manjaro/stable/$repo/$arch
    15: https://ridgewireless.mm.fcix.net/manjaro/stable/$repo/$arch
    16: https://codingflyboy.mm.fcix.net/manjaro/stable/$repo/$arch
    17: https://opencolo.mm.fcix.net/manjaro/stable/$repo/$arch
    18: https://mirrors.sonic.net/manjaro/stable/$repo/$arch
    19: https://mirrors.ucr.ac.cr/manjaro/stable/$repo/$arch
    20: https://mirrors.ocf.berkeley.edu/manjaro/stable/$repo/$arch
    21: https://mirror.xenyth.net/manjaro/stable/$repo/$arch
    22: http://mirror.fcix.net/manjaro/stable/$repo/$arch
Processes:
  CPU top: 5 of 269
  1: cpu: 100% command: ps pid: 3090 mem: 3.88 MiB (0.0%)
  2: cpu: 31.4% command: firefox pid: 1870 mem: 493.1 MiB (3.0%)
  3: cpu: 16.0% command: firefox pid: 2087 mem: 254.1 MiB (1.5%)
  4: cpu: 6.9% command: Xorg pid: 1051 mem: 101.1 MiB (0.6%)
  5: cpu: 6.6% command: xfce4-terminal pid: 3064 mem: 56.6 MiB (0.3%)
  Memory top: 5 of 269
  1: mem: 493.1 MiB (3.0%) command: firefox pid: 1870 cpu: 31.4%
  2: mem: 467.9 MiB (2.9%) command: thunderbird pid: 1749 cpu: 5.4%
  3: mem: 254.1 MiB (1.5%) command: firefox pid: 2087 cpu: 16.0%
  4: mem: 210.6 MiB (1.3%) command: firefox pid: 2022 cpu: 3.8%
  5: mem: 210.5 MiB (1.3%) command: firefox pid: 2091 cpu: 1.2%
Info:
  Processes: 269 Power: uptime: 2m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 6.18 GiB services: upowerd,xfce4-power-manager
    Init: systemd v: 257 default: graphical tool: systemctl
  Compilers: clang: 19.1.7 gcc: 14.2.1 Shell: Bash v: 5.2.37
    running-in: xfce4-terminal inxi: 3.3.37```

Try removing nvidia_drm.modeset=1 to see if it changes something.

1 Like

Are you sure? I seem to recall that was required from an update sometime last year, or the one before.

Also, I honestly don’t recall how that was done. What config file am I modifying, and where is it located?

/etc/default/grub

You will then need to regenerate grub with update-grub as root.

2 Likes

The easiest way to test it is during boot in GRUB, press e on the boot entry, remove that setting (it doesn’t persist across reboots) and press the key to boot.

4 Likes

On Manjaro Gnome, the sound did not work after upgrade, I couldn’t start playback.
It turned out I still used pulseaudio and there was a pipewire instance in processes too. So I installed manjaro-pipewire package (which uninstalled pulseaudio) and after restart the sound was back.

4 Likes

Just want to share that Pipewire 1.4.1 fixed USB audio glitching issues for me. I consistently had popping/skipping/glitching resync issues with my USB headset on Pipewire 1.2.x,

e.g.

Jul 30 19:02:22 lx-outofstock pipewire[2339]: spa.alsa: hw:0p: follower avail:2047 delay:2047 target:1024 thr:1024, resync (93 suppressed)
Jul 30 19:02:23 lx-outofstock pipewire[2339]: spa.alsa: front:4p: follower avail:752 delay:752 target:1024 thr:512, resync (125 suppressed)

I can report that I went the whole day today without this happening once. Very happy.

4 Likes

Brave tabs crashed after update, the browser itself crashed few minutes later
Tried to reboot running shutdown -r now:
It doesn’t boot.
Screen only shows Lenovo and Manjaro logos and the loading three dots.

This, unfortunately, sounds like disk corruption/failure.

Could you boot from a Live .ISO and run e.g. sudo smartctl -a /dev/sdX (change sdX to whatever your storage device is; lsblk should show)?

You might need to install smartmontools in the Live session.