[Testing Update] 2024-09-13 - Kernel, Qemu, Systemd, Plasma, KDE Gear, Virtualbox

[michaldybczak]

@philm

I think everything points to plasma here: [Plasma 6.1] Did something changed in performance for Intel CPUs? - Help - KDE Discuss .

I am using AMD CPU , so I don’t think this is related at all. At the moment backup was restored and I switched to stable branch, so there is nothing to test, because the 6.1.4 Plasma works fine for me.

However, if it comes to that, that the update will come to stable branch and the same issue happens, I’ll check X11 as well. However, it is problematic for me to test various things because I have 1444p screen and X11 is crap for it. My workflow depends heavily on plugins and tab groups in Firefox, while other browsers are for some other activities, so it’s not like I am ready to do hours of work there.

From DEs, LXQT is the safest thing to install alongside Plasma and that is easy to do, when it comes to that.

So far, a few hours of work on the downgraded system and no issue.

@Ben

the most stable desktop is XFCE (which you’ll likely hate after using Plasma)

I hated it BEFORE using Plasma. This isn’t a good solution for me. I am using Plasma sine 5.3 so for many, many, many years and stability of Plasma is not a problem for me. I had issues on the beginning, but it turned out to be some config problems and once everything was purged, the system became reliable.
So for years Plasma was a great experience for me, hence the surprise to see such a serious show stopping bug after the update.
There were some serious issues in the past, but I don’t recall them at the moment. Usually, it was enough to jump to stable branch, stay there for a while, jump again to testing and those issues were gone. I hope the same will happen here.

@trinitronx

Maybe it helps to save some time using LiveUSB + Ventoy?

Never heard of Ventoy. I’ll check it out. The problem with testing in Live system is that the issue happens randomly. It can happen after a few minutes or many hours or even days. I have personalized workflow and settings, so vanilla OSes aren’t working for me, at least not for hours. I really prefer to fix the current system on the bare metal and this worked well for me past last 8 years. My OS install is that long and even propagated into various machines , so I wouldn’t have to setup everything from scratch.

As to Plasma settings, I did purged Plasma configs after upgrade to Plasma 6, since it was needed to fix things. I don’t recall purging cache, so this is a thing I can try, but since I am working for so many months without issues, I doubt it would help, but it doesn’t hurt to try.

And yeah, I thought about the cursor issue where to report it too, and came to the same conclusion that Plasma and specifically kwin is responsible for it, so I’ll look for the reports there. Hopefully, someone noticed it as well and posted it.

[philm]

Removing cache is always a good thing. Heavy customization is not supported by Plasma. You should avoid that and use close to stock settings. That is how Plasma imagine their DE and that is what they are focusing on supporting also. Avoid plugins or themes. There are too many issues with those. Especially with 6.1 release of Plasma.

Updated to Plasma 6, having bad problems

https://www.reddit.com/r/kde/comments/1dkd1vy/error_loading_qml_file_in_settings_plasma_61/
https://bugs.kde.org/show_bug.cgi?id=487904#c11

There is a reason why I use XFCE for years

[nikgnomic]

@michaldybczak

the sound got fixed when I restored from backup.

I suggest you create a topic in Sound - Manjaro Linux Forum and post more information about system and audio device:

inxi -SMAa

pactl list cards

[michaldybczak]

@philm

Removing cache is always a good thing. Heavy customization is not supported by Plasma. You should avoid that and use close to stock settings. That is how Plasma imagine their DE and that is what they are focusing on supporting also. Avoid plugins or themes. There are too many issues with those.

Yeap and that is why, on Plasma 6 I am sticking to defaults, breeze and so on. I’m waiting for the moment till Plasma 6 theming and customization ecosystem matures.
What I meant by customization is that my browsers are customized with extensions, the system have a lot of apps that I need, all of those apps have their own settings, etc. Having a vanilla OS is painful, because you start to realize how much you relay on each app individual settings to work efficiently. When I came across default Dolphin, I was lost and couldn’t even find things that I consider basic, because it was hidden.

Anyway, my Plasma 5 was heavily customized with latte, its additions, etc, while Plasma 6 is just boring defaults. I cannot stress enough, till this update, there were no prominent issues and so far, after the downgrade, all works as intended.

It is possible that I purged not only configs but also cache when upgrading to Plasma 6, I just don’t recall it, since cache is meaningless. I only recall, that I had issues and they were all gone when I cleared Plasma old configs.

@nikgnomic

I suggest you create a topic in Sound - Manjaro Linux Forum and post more information about system and audio device:

I would, if I stayed on testing branch. I downgraded the system from backup, so at this moment it is impossible to debug it, since all works fine after downgrade. If the issue happens later, I will do that. It is common, that those bugs disappear with time. Usually I have patience to suffer through them and report them, but the busy time of a year is starting, so my time is getting shorter, thus “wait through it” is my default strategy at the moment, although normally I do like to be invlolved.

[omano]

It is unfortunate that you discover potential issue on Testing branch, and switch back to Stable, to wait for the potential issues to come to Stable. But you do as you wish, just that if they are issues in Plasma, triggered by your use case or hardware or whatever configuration, it will hit Stable too for the others.

[michaldybczak]

Yeah, I know, that is why I waited almost 3 days, in hope it’s not that bad and the issue was accidental. However, the problem is, I need the laptop to be operational and I cannot allow for such problems. Usually, I would prefer to debug it, but:

• I don’t know how to trigger this bug, sometimes it can be minutes, hours or days
• the busy season for me is coming and my time goes short, so if I could allow for experiments before, now it’s not the right time to do it
• when issue happens, I litterally can’t do much, aside switching to TTY and observe some processes and resource busyness, or have another laptop to check what I can test or look at, which again, requires time to research,
• the issue seems to be invisible in journald, so I could only change the conditions (like DE, another browser) and observe it for hours or days, in short, it would require a lot of work on my part and a lot of time spending and observing - this is the worst kind of issues to deal with and there is a line I have to draw
• even if I could allow myself for the time and debugging, I bet this would take weeks if not months to solve it, unless another update fixed it

If no one catches and report this, it will come to me eventually, but later. However, there is a chance it will be fixed with time, so with lack of time, I have to take that chance.

[spacecase-25]

Just now I was in the midst of the black void taking over my screen (triggered by mousing into an auto-hidden panel) and was able to save the session by disabling color correction via Display and Monitor settings. Previously it was configured to use “Built-in” profile (which provided no change over ICC correction being disabled, so I probably shouldn’t have enabled it in the first place). Upon saving this change, the black void disappeared and has not returned in the minute and a half it’s taken me to navigate back to this thread and post this reply.

EDIT: confirming that was the issue… I was able to expand the individual cpu usage applet without triggering the ever-expanding black void. That was a reliable way to trigger it previously. Issue seem to be whatever the “built in” ICC profile is or is lacking. I don’t have a properly calibrated, valid ICC profile to test on this machine currently.

[2old4gaming]

For when I don’t know what exactly triggers a bug, I open Konsole, run journalctl -f and leave it open. When the bug occurs, switch to Konsole to note any errors. For bugs that happen to bring down my system, I try to note the exact time (down to the second) after a forced reboot, run journalctl --since=today in Konsole and scroll to the exact time the bug occurred to try to glean what happened.

[philm]

@michaldybczak maybe try a different kernel than 6.10. Like 6.9 and see if there are any changes. Cos you might had noticed that those kernel series got patched a lot lately: Commits · main · Packages / core / linux610 · GitLab

[stephane]

i got theses errors for linux611 , this morning ( tuesday 17/09 )

==> Building image from preset: /etc/mkinitcpio.d/linux611.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.11-x86_64 -g /boot/initramfs-6.11-x86_64.img
==> Starting build: '6.11.0-2-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]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> ERROR: module not found: 'nvidia'
==> ERROR: module not found: 'nvidia_uvm'
==> ERROR: module not found: 'nvidia_drm'
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.11-x86_64.img'
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: /etc/mkinitcpio.d/linux611.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.11-x86_64 -g /boot/initramfs-6.11-x86_64-fallback.img -S autodetect
==> Starting build: '6.11.0-2-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]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> ERROR: module not found: 'nvidia'
==> ERROR: module not found: 'nvidia_uvm'
==> ERROR: module not found: 'nvidia_drm'
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.11-x86_64-fallback.img'
==> WARNING: errors were encountered during the build. The image may not be complete.
erreur : la commande n’a pas pu être exécutée correctement

[philm]

Did you install linux611-nvidia?

[stephane]

yes :

pacman -Qs linux611
local/linux611 6.11.0-2
    The Linux611 kernel and modules
local/linux611-headers 6.11.0-2
    Header files and scripts for building modules for Linux611 kernel
local/linux611-nvidia 550.107.02-1 (linux611-extramodules)
    NVIDIA drivers for linux

[philm]

make sure you have linux611-nvidia 550.107.02-2 installed.

[stephane]

may be this :

sudo pacman -S linux611-nvidia
erreur : impossible de trouver la cible : linux611-nvidia

i have redo pacman-mirrors -c all , no linux611-nvidia
mirrors are not all updated in testing

[philm]

Well you can try: sudo pacman -U https://mirror.easyname.at/manjaro/testing/extra/x86_64/linux611-nvidia-550.107.02-2-x86_64.pkg.tar.zst

[Boti]

Kernels 6.10.10-3 and -4 lead to display corruption on my internal notebook display. The corruption looks like the same as in this thread.

[stephane]

sudo pacman -U https://mirror.easyname.at/manjaro/testing/extra/x86_64/linux611-nvidia-550.107.02-2-x86_64.pkg.tar.zst
chargement des paquets…
avertissement : linux610-nvidia-550.107.02-8 est à jour -- réinstallation
résolution des dépendances…
recherche des conflits entre paquets…

Paquets (1) linux610-nvidia-550.107.02-8

Taille totale installée :      51,19 MiB
Taille de mise à jour nette :   0,00 MiB

:: Procéder à l’installation ? [O/n] O
(1/1) vérification des clés dans le trousseau      [----------------------] 100%
(1/1) vérification de l’intégrité des paquets      [----------------------] 100%
(1/1) chargement des fichiers des paquets          [----------------------] 100%
(1/1) analyse des conflits entre fichiers          [----------------------] 100%
(1/1) vérification de l’espace disque disponible   [----------------------] 100%
:: Traitement des changements du paquet…
(1/1) réinstallation linux610-nvidia               [----------------------] 100%
:: Exécution des crochets (« hooks ») de post-transaction…
(1/3) Arming ConditionNeedsUpdate...
(2/3) Updating module dependencies...
(3/3) Updating Kernel initcpios for Nvidia-DRM...
==> Building image from preset: /etc/mkinitcpio.d/linux610.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.10-x86_64 -g /boot/initramfs-6.10-x86_64.img
==> Starting build: '6.10.10-4-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]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.10-x86_64.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux610.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.10-x86_64 -g /boot/initramfs-6.10-x86_64-fallback.img -S autodetect
==> Starting build: '6.10.10-4-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]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.10-x86_64-fallback.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux611.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.11-x86_64 -g /boot/initramfs-6.11-x86_64.img
==> Starting build: '6.11.0-2-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]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> ERROR: module not found: 'nvidia'
==> ERROR: module not found: 'nvidia_uvm'
==> ERROR: module not found: 'nvidia_drm'
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.11-x86_64.img'
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: /etc/mkinitcpio.d/linux611.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.11-x86_64 -g /boot/initramfs-6.11-x86_64-fallback.img -S autodetect
==> Starting build: '6.11.0-2-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]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> ERROR: module not found: 'nvidia'
==> ERROR: module not found: 'nvidia_uvm'
==> ERROR: module not found: 'nvidia_drm'
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.11-x86_64-fallback.img'
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: /etc/mkinitcpio.d/linux61.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.1-x86_64 -g /boot/initramfs-6.1-x86_64.img
==> Starting build: '6.1.110-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]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.1-x86_64.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux61.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.1-x86_64 -g /boot/initramfs-6.1-x86_64-fallback.img -S autodetect
==> Starting build: '6.1.110-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]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.1-x86_64-fallback.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux66.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.6-x86_64 -g /boot/initramfs-6.6-x86_64.img
==> Starting build: '6.6.51-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]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.6-x86_64.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux66.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.6-x86_64 -g /boot/initramfs-6.6-x86_64-fallback.img -S autodetect
==> Starting build: '6.6.51-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]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.6-x86_64-fallback.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
erreur : la commande n’a pas pu être exécutée correctement

is it related to version 7 pacman , or i need to switch on another mirrors testing
i try with theses mirrors

sudo pacman-mirrors -c Germany

::INFO Téléchargement des miroirs depuis Manjaro
::INFO => Mirror pool: https://repo.manjaro.org/mirrors.json
::INFO => Mirror status: https://repo.manjaro.org/status.json
::INFO Liste de miroirs générée par l’utilisateur
::------------------------------------------------------------
::INFO Liste de miroirs personnalisée sauvegardée: /var/lib/pacman-mirrors/custom-mirrors.json
::INFO Utilisation de la liste des miroirs par défaut
::INFO Interrogation des miroirs - Cela peut prendre un certain temps
  0.283 Germany        : https://mirror.alpix.eu/manjaro/
  0.121 Germany        : https://mirrors.xtom.de/manjaro/
  0.199 Germany        : https://ftp.gwdg.de/pub/linux/manjaro/
  0.104 Germany        : https://mirror.23m.com/manjaro/
  0.223 Germany        : https://ftp.halifax.rwth-aachen.de/manjaro/
  0.151 Germany        : https://mirror.netcologne.de/manjaro/
  0.051 Germany        : https://manjaro.kurdy.org/
::INFO Écriture de la liste des miroirs
::Germany         : https://manjaro.kurdy.org/testing
::Germany         : https://mirror.23m.com/manjaro/testing
::Germany         : https://mirrors.xtom.de/manjaro/testing
::Germany         : https://mirror.netcologne.de/manjaro/testing
::Germany         : https://ftp.gwdg.de/pub/linux/manjaro/testing
::Germany         : https://ftp.halifax.rwth-aachen.de/manjaro/testing
::Germany         : https://mirror.alpix.eu/manjaro/testing
::INFO Liste de miroirs générée et sauvegardée dans: /etc/pacman.d/mirrorlist
sudo pacman -Syyu
:: Synchronisation des bases de données de paquets…
 core                                                                                  138,8 KiB  1186 KiB/s 00:00 [--------------------------------------------------------------------] 100%
 extra                                                                                   7,9 MiB  18,3 MiB/s 00:00 [--------------------------------------------------------------------] 100%
 multilib                                                                              140,4 KiB  1350 KiB/s 00:00 [--------------------------------------------------------------------] 100%
:: Début de la mise à jour complète du système…
 il n’y a rien à faire
sudo pacman -U linux611-nvidia-550.107.02-2-x86_64.pkg.tar.zst
chargement des paquets…
erreur : 'linux611-nvidia-550.107.02-2-x86_64.pkg.tar.zst': impossible de trouver ou de lire le paquet
sudo pacman -S linux611-nvidia
erreur : impossible de trouver la cible : linux611-nvidia

solved with new version linux611-nvidia 550.107.02-4 and linux611 6.11.0-3 and linux611-headers 6.11.0-3

[philm]

@Boti

Kernels 6.10.10-3 and -4 lead to display corruption on my internal notebook display.

@Boti can you please check if 6.10.10-2 added the regression you see and if 6.10.10-1 was the last kernel which worked fine on your end?

[Boti]

6.10.10-1 was ok, I forgot to mention explicitly. How can I check 6.10.10-2 ? Neither downgrade nor pacman -U https://mirror.easyname.at/manjaro/testing/core/x86_64/linux610-6.10.10-2-x86_64.pkg.tar.zst succeed.

[philm]

@Boti

How can I check 6.10.10-2

Please get them from here: Releases · manjaro-kernels/linux610 · GitHub