[Stable Update] 2026-10-28 - Plasma 6.75, GNOME 50.5, COSMIC 1.9.0

I have two questions prior to executing this stable upgrade.

I’m an AMD user (CPU, GPU) and currently only linux-firmware-amdgpu 20260810-2 is installed. I’ve also removed the linux-firmware metapackage in the past. This means, I’m affected by the mentioned firmware changes in the ‘Known Issues’ section. The section doesn’t explicitly mention though when to install the other file (I guess linux-firmware-amd in my case). Do I get that right when I assume it’s meant to be installed right after the upgrade with sudo pacman -S linux-firmware-amd but before the reboot?

The second question is about the GRUB pacnew. My current situation is as follows:

  • install-grub and update-grub have been installed in the past.
  • My current GRUB_CMDLINE_LINUX_DEFAULT looks like this:
apparmor=1 security=apparmor resume=UUID='LONG-NUMBER' udev.log_priority=3 sysrq_always_enabled=1
  • The HOOKS in /etc/mkinitcpio.conf are:
HOOKS=(systemd autodetect microcode modconf kms keyboard sd-vconsole block filesystems fsck)

I have removed Plymouth in the past because I prefer to look at the boot messages during startup. Therefore I removed the ‘quiet’ parameter from GRUB and the ‘plymouth’ hook. I get that I can upgrade GRUB after rebooting but I’m not sure which parts to keep.

Since I’m using ‘systemd’ in the HOOKS, I’m pretty sure I have to replace udev.log_priority=3 with loglevel=3 rd.udev.log_level=3 as it has been suggested by @Marsa in post #42.

But what about the other kernel boot parameters? Do I have to remove any of them for the new GRUB to work or should they stay?

Do I get it right that install-grub won’t solve the .pacnew issue during the update but it requires manual intervention after the reboot with sudo update-grub after changing /etc/default/grub?

I’m asking to be on the safe side because I have a slight (admitted) paranoia about ending up with an unbootable system.

Just installing it is probably not enough. You’ll need to rebuild your initramfs and then update your boot loader again.

So before rebooting, you need to execute these two commands… :backhand_index_pointing_down:

sudo mkinitcpio -P
sudo update-grub

That is correct.

They can stay.

You have to understand that all install-grub does is make sure that /boot/efi/EFI/boot/bootx64.efi and /boot/efi/EFI/manjaro/grubx64.efi are identical by copying the latter over the former.

This has nothing to do with update-grub, which is a script that in turn executes the following command… :backhand_index_pointing_down:

grub-mkconfig -o /boot/grub/grub.cfg

The latter is where the configuration from your /etc/default/grub and the scripts in /etc/grub.d/ is being applied.

6 Likes

9 posts were split to a new topic: Issue with HP LIP 3.26.6-1: scanning doesn’t work (HP Officejet 4630)

Just sharing a fix in case someone hits the same conflict.
Following the Known issues note, I ran pacman -S linux-firmware-amd and pacman refused with a conflict involving the old linux-firmware-meta I still had installed (sorry, I no longer have the exact message). Replacing it fixed it:

sudo pacman -Syu linux-firmware

I answered y when pacman asked to remove linux-firmware-meta; linux-firmware-amd, -amdgpu and -ti came in as dependencies. The meta package was already orphaned on my system (installed as a dependency, required by nothing).

2 Likes

The ‘Known issues’ section doesn’t mention that rebuilding the initramsfs is necessary. So thanks for the tip and deepening the understanding of install-grub and upgrade-grub. :slight_smile:

Since I’m rebuilding the GRUB configuration after rebuilding the initramfs, I was asking myself if it would make sense to make the discussed .pacnew GRUB changes before that step to ‘kill two birds with one stone’ so to speak.

  1. sudo pacman -Syu for the stable upgrade
  2. pacman -S linux-firmware-amd
  3. sudo mkinitcpio -P
  4. Make the changes to /etc/default/grub/
  5. sudo update-grub
  6. sudo reboot now

Is there anything wrong with that or should GRUB only be modified after the reboot?

3 Likes

No, that is the correct procedure. :wink:

3 Likes
2 Likes

You might save a few keystrokes like this;

sudo pacman -Syu linux-firmware-amd

:point_right: Normally a package is installed by only using sudo pacman -S <package> but, package(s) can also be installed while actually performing an update/sync sudo pacman -Syu <package>. :eyes:

Make changes to /etc/default/grub

sudo mkinitcpio -P
sudo update-grub
sudo reboot now

Either way, it still gets the job done.

5 Likes

It might not look like much at first but I love those small little nuggets of wisdom and efficency. :star_struck: Thanks for that.

I’m always happy to learn a new self-optimizing trick and saving keystrokes. You wouldn’t believe how mind-blown I was when I learnt about sudo !! :exploding_head:

4 Likes

Today i experience that Veracrypt tray menue refused to show up but instead has a strange request after this stable update, always when i right click on the tray icon this shows up:

I denieing that again and again but doesn’t help… so im forced to start veracrypt from Taskbar again to finally unmount my storage:

Im wondering if it has something to do with:
GDK_BACKEND=x11

which i use to restore a Tray Icon under Wayland.

To me it looks like wayland dialog. How long will kde support x11 at all i wonder. Maybe that variable doesn’t work anymore.

xembedsniproxy is a component being provided by plasma-workspace. Veracrypt use an outdated protocol called XEmbed to embed their icons directly into the system tray panel. So, it should be totally safe to allow it.

3 Likes

I have this Dialog on my new PC & Laptop where im using Wayland, so yeah it is a Wayland dialog. I only use X11 on my old PC.

Thanks im allowing full access then.

Im wondering why it was working before this update (with Wayland), but thanks i allow it then.

Do you know how i revert this decision in future? Hopefully this access isn’t needed after the next updates.

If you install the flatpak-kcm package, you will then have a new Application Permissions section in Plasma’s System Settings where you can set and change the permissions for X11 applications. That should allow you to revoke previously allowed permissions (although I haven’t tested it myself).

2 Likes

Thank you Scotty for pointing at this package.

Im wonderin why this permissions are required and integrated in KDE Wayland, but to revert that permissions we need a flatpak-kcm package.

I would expect that this adjustments are stored somewhere deep inside system-controls in a sub-menue.

That situation looks to me, that KDE isn’t still ready for Wayland yet, otherwise they would have integrated this option in Plasma.

flatpak-kcm is in the plasma group and part of the plasma-meta package. I was just looking at the KDE Plasma ISO profile to see what needed to be added / removed, in fact. I can include in the next ISO.

EDIT: I’ll also add flatseal for managing Flatpak permissions to the GNOME ISO.

6 Likes

You might consider adding plasma-firewall (front end for firewalld) as well, if it isn’t already.

I have the same System as you have listed and am seeing the same issue. I haven’t tried using the NumLock key before logging in. Thanks for the hint.

Is it considered safe to keep rolling with non LTS kernels with stable repos? Isn’t now the latest kernel 7.2 basically EOL, but it’s the highest that is available on stable repos?

How would i go on switching to testing repos perhaps, because it’s rumored that the LTS will be 7.3 and i basically need the 7.4 on my system to get VRR?

1 Like

Yes. Why wouldn’t it be?

Yes, 7.2 is EOL, but so far only in the Unstable branch. The reason why it’s still the newest non-LTS kernel in the Stable branch is that it had been since early September that there had been a Stable Update — in the announcement of which Philip stated that he was temporarily freezing Manjaro — and even the Testing branch was already getting a bit stale.

As such, the Team has taken matters into our own hands and pushed out a Stable Update and a Testing Update in short succession.

sudo pacman-mirrors -a -B testing && sudo pacman-mirrors -f && sudo pacman -Syyu

The next LTS will most likely be 7.4, not 7.3. :wink:

3 Likes