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

Erneuere flatpak (1:1.15.11-1 -> 1:1.15.12-1)...
Fehler: flatpak: Konnte /usr/share/polkit-1/actions/org.freedesktop.Flatpak.policy nicht entpacken (Truncated tar archive detected while reading data)
Fehler: flatpak: Fehler traten auf, während flatpak aktualisiert wurde
Fehler: flatpak: Konnte den Vorgang nicht durchführen
Vorgang konnte nicht abgeschlossen werden:
Vorgang abgebrochen

i have no flatpack and there is no package installed

I will do it. I’ve left a message there supporting your idea. If we could have more people doing the same we could avoid similar problems in the future.

1 Like

After the update I had an issue with Gnome having these giant black borders around certain apps. Default Light Theme (happened in dark theme too)

This fixed it https://www.reddit.com/r/gnome/comments/1fsf6wz/thick_black_borders_around_some_windows/

3 Likes
lib32-nvidia-utils 550.135-1
linux61-nvidia 550.135-2
linux612-nvidia 550.135-3
mhwd-nvidia 550.135-1
mhwd-nvidia-390xx 390.157-16
mhwd-nvidia-470xx 470.256.02-7
nvidia-prime 1.0-5
nvidia-settings 550.135-1
nvidia-utils 550.135-1

So far no problems.

I updated the intel machine. No issues, i followed the relevant for me points in the FAQ. One think though: i managed to restore the pamac aur functionality WITHOUT --dry-run. I do not quite get the idea of the dry run, the file is missing, it has to be written, and with root ownership. That will not happen with dry run, it needs a “wet” run.

1 Like

after update pamac-manager no longer starts:

Gdk-Message: 19:33:36.376: Error 71 (Protocol Error) dispatching to Wayland display.

EDIT: the GSK_RENDERER=ngl trick in /etc/environment works

Try this one:

And log out and log in again.

1 Like

Yeah, i was just trying that and it worked.
Thanks

How exactly do you recommend to voice up in the nvidia forum?

Should we point to our NVIDIA 550.135 driver that we use here?


@ KDE Users

Anyone else experience a Desktop icon position reset, after manually power off/on the Monitor under X11 + Nvidia?

No problem on my AMD Laptop and Wayland, when i use Monitor energy savings btw. so im not sure if this is related to X11 or the manual power off function from my PC Monitor.

:thinking:

already answered:

1 Like

can both be removed.

pulseaudio-ctl is not compatible with PipeWire and v86d not longer needed.

1 Like

Seems to work on kernel 6.12, albeit with the same glitches on X11 that have been present for each and every kernel version that came before (choppy KDE Plasma desktop animations, black/flickery windows after resuming from sleep/hibernation, etc.).

Is the “NVIDIA experience” any better when using Wayland?

Package list:

lib32-nvidia-utils 550.135-1
linux-nvidia-meta 6.11-1
linux611-nvidia 550.135-3
linux612-nvidia 550.135-3
linux66-nvidia 550.135-2
mhwd-nvidia 550.135-1
mhwd-nvidia-390xx 390.157-17
mhwd-nvidia-470xx 470.256.02-8
nvidia-settings 550.135-1
nvidia-utils 550.135-1

Kudos to the Manjaro team. You folks are absolutely amazing. Updates went perfect on my 2 laptops and my brand new beast machine that I just built.

Thank you for your continued awesomeness!

7 Likes

I had this issue as well, not sure why pacman displays the characters in the error message correctly but pamac does not. I would have assumed they used the same system character sets.

1 Like

KDE plasma desktop starts very slowly after the upgrade. I’m using AMD 7950 iGPU, not sure why mhwd-nvidia needs to be installed. It looks python-systemd and python-manjaro-sdk needs it.

Thanks for your help. No progress. I removed (pacman -R -d -d) v86d and mhwd, thinking I could re-install mhwd and that would resolve the dependency on v86d, but everything I’ve tried goes back to get something from AUR, and fails with the same ‘unresolvable package conflicts’ message and the same gibberish output.

At this point I’m not sure my system is still bootable, as the install command led to kernel building which also failed.

Any tips appreciated.

I think it is better to create own topic and start posting logs. Mwhd does not currently depend on v86d. Which means either your mirrors are not properly synced, or you have a bunch of packages not from the repos (like a development version of mwhd?), or maybe in a partial sync (manually downgraded mwhd?)

2 Likes

@weingeist: I could not reproduce your issue with the flatpak package you had. Truncated tar archive detected while reading data might lead to a broken mirror storage. You can try to redownload the file from a different mirror like:

sudo pacman -U https://mirror.easyname.at/manjaro/pool/overlay/flatpak-1:1.15.12-1-x86_64.pkg.tar.zst

@Kobold: only if you have problems with Nvidia drivers and Kernel 6.12. 550.135 driver should have all fixes. I just need to know if I can ship 24.2 release with 6.12 kernel or if I should fall back to 6.11 series. For 470xx and 390xx drivers I can rely on the comments found at AUR.

@lordgarmadon mhwd-nvidia is a small file which has a list of IDs of Nvidia hardware. It is part of the mhwd system Manjaro ships. The python packages you mentioned you may uninstall, as they are not of use anymore.

@nd3i As Teo already recommended, start a new support issue so we may help you better. Using -Rdd for v86d is not needed, as there is no dependency of it with packages we ship in our official repositories. Try to refresh your mirrorlist so you won’t face an partial or outdated mirror: sudo pacman-mirrors -c Global

1 Like

Ups i wasn’t really paying attention what i wrote there. :upside_down_face:

I meant How exactly do you recommend to voice up in the nvidia forum.

Im still using lts 6.6 but im probably switch soon, if 6.12 becomes really the next LTS Kernel.

https://www.kernel.org/category/releases.html

Still don’t show it.

Interesting to note is that the kernel.org page hasn’t been updated since 2024-08-06.

These seem a little more current:

1 Like