[Stable Update] 2024-12-06 - Systemd, Qt 6.8.1, Mesa, Gstreamer, Wireplumber

[Randomname123]

Hello everyone! I tried rebuilding the python thingies but this happens…

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

Output:

python-contextlib2
python-manjaro-sdk

Then:

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

Output:

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
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
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
Error: target not found: python-manjaro-sdk
Error: target not found: python-contextlib2

Any tips, suggestions or magic spells to fix this?

[Yochanan]

@Autolycus

error: failed to commit transaction (conflicting files)

Just for posterity…

Warning: Generally avoid using the --overwrite switch. See System maintenance#Avoid certain pacman commands.

– pacman - ArchWiki

[Yochanan]

@Randomname123

python-contextlib2
python-manjaro-sdk

Those packages were dropped from the repos long ago and nothing requires them. Remove them.

[Autolycus]

I already updated using the suggested --overwrite command. Am I good, or do I need to do something else?

Thanks!

[Yochanan]

If that worked, then you should be good to go. I just wanted to mention the above for informational purposes.

[philm]

I will fix those gamescope plus file conflicts in an update. Thanks for letting me know.

[continue-revolution]

I sleeped my PC and reinitiated, then the screen started to be covered with noise. Noise disappear after restart. Not present in previous versions

[WalterNeff]

sometime during the last update (or the 11/30 update)
my apparmor whitelist file (for samba) got renamed with a
.pacsave extension. This broke one of my shares.
I forgot about this apparmor stuff for samba
Until I read my own post from 2022…when I first had the problem.
It’s a drive mounted at /mnt that I (occasionally) connect to an old Win7 box.
the /home shares (2) work fine. Just thought I’d mention it.

[Hal9000]

MPV on Intel Meteor-Lake, vaapi hardware acceleration fails.

Addendum
Second test on Intel Alder-Lake System. No problems, no segfault, the older architecture is not affected.

[vo/gpu] Loading hwdec drivers for format: 'vaapi'
[vo/gpu] Loading hwdec driver 'vaapi'
[vo/gpu/vaapi] Using EGL dmabuf interop via GL_EXT_EGL_image_storage
[vo/gpu/vaapi] Trying to open a x11 VA display...
[vo/gpu/vaapi] Trying to open a wayland VA display...
[vo/gpu/vaapi/vaapi] libva: VA-API version 1.22.0
[vo/gpu/vaapi/vaapi] libva: Trying to open /usr/lib/dri/iHD_drv_video.so
[vo/gpu/vaapi/vaapi] libva: Found init function __vaDriverInit_1_22
[vo/gpu/vaapi/vaapi] libva: va_openDriver() returns 0
[vo/gpu/vaapi/vaapi] Initialized VAAPI: version 1.22
[vo/gpu/vaapi] Going to probe surface formats (may log bogus errors)...
[statusline] AV: 00:00:09 / 02:07:46 (0%) A-V:  0.000zsh: segmentation fault (core dumped)  mpv -v RO.mkv

dmesg

[10390.847895] vo[17938]: segfault at 79f5fcd39 ip 000079f62cf84a68 sp 000079f6363b80b0 error 4 in iHD_drv_video.so[584a68,79f62ca1e000+985000] likely on CPU 3 (core 12, socket 0)
[10390.847903] Code: 8b 03 48 8b 38 48 85 ff 74 0e be 28 02 00 00 ff 15 4d be d2 01 48 8b 03 48 c7 00 00 00 00 00 31 c0 e9 a3 00 00 00 0f 1f 40 00 <4c> 8b a9 b0 00 00 00 31 c0 4d 85 ed 74 34 4c 89 ef ff 15 39 bf d2

[scotty65]

@WalterNeff

sometime during the last update (or the 11/30 update)
my apparmor whitelist file (for samba) got renamed with a
.pacsave extension. This broke one of my shares.

The reason why Manjaro users should always run

pacdiff -s

or

DIFFPROG=meld pacdiff -s

after updates.

The above commands require having the pacman-contrib & meld packages installed on your system.

manjaro-pacnew-checker is also available from the repos - I believe it automatically runs a check for .pacnew & .pacsave files after system updates.

Note that these files should always be inspected first before merging/deleting/replacing. Full instructions for dealing with .pacnew & .pacsave files can be viewed at:

System Maintenance

[thwright]

Continuing the discussion from [Stable Update] 2024-11-30 - Kernels, Plasma, GNOME, COSMIC, LXQT, SYSTEMD:

@Kjplay

Would begin with checking if /usr/lib/qt6/QtWebEngineProcess is executable. [2787:2787:1203/161719.326285:FATAL:zygote_host_impl_linux.cc(201)] seems like an error from QtWebEngine which should not prevent Plasma from running.

Arey you on X11 or Wayland? Can you check kwin logs?

@philm

@purplemunchies and @thwright can you both do the following steps on your PC and try to boot into 6.12 kernel again. Most likely early KMS might be needed with newer kernels as @fonic pointed out. Step one is not needed as we enable that by default now.

I found that the issue was the KDE Dictionary widget. Something with the widget’s mere existence on the panel is causing the Desktop to crash.

[deemon]

This update, and previous also (30nov), on updating, turned all my monitors to maximum brightness. Last time I thought it’s something to do with plasma getting version bump. But this time it’s not the case…

also previous update made mpv stutter/stop_playback randomly every 3-10minutes for ~1 second and then continue like nothing happened…

[Aragorn]

@thwright

I found that the issue was the KDE Dictionary widget. Something with the widget’s mere existence on the panel is causing the Desktop to crash.

I seriously doubt that, because I too have that widget on one of my panels.

What is more likely is that the configuration file got corrupted, and by removing the widget, a new and correct copy of the file was written to your ~/.config.

[philm]

@deemon

This update, and previous also (30nov), on updating, turned all my monitors to maximum brightness.

There was an update on how Plasma 6.2 will handle brightness: Brightness controls for all your displays - KDE Blogs

[hmcezar]

Update went well, and everything apparently works.
However, after the update Tilix is crashing every time I try to activate a conda environment (GNOME Terminal works fine).

This is what is logged:

[ 1845.461248] tilix[18031]: segfault at 9 ip 00007fac33ea0d98 sp 00007ffc6b63daa0 error 4 in libgobject-2.0.so.0.8200.2[7fac33e6b000+38000] likely on CPU 4 (core 0, socket 0)

[Telcoced]

Hello,

Strange behaviour today: Pamac suggested 4 updates for

• pamac-tray-icon-plasma
• zsh-theme-powerlevel10k
• ckbcomp
• tlpui

All of them are listed as coming from AUR, but no updates possible, in fact.
I tried to remove most of them, obviously I lost my Pamac tray icon ^^
For ckbcomp, it would be a bad idea to remove it as its a dependency of manjaro-settings-manager.

I tried to update my database, as well as my mirrors, with no changes after that.

Anyone encountering same problem?

[BG405]

All four of those are in the extra repo I’d suggest installing those using pacman, unless that’s what you already tried?

suco pacman -Rns <package>

to remove them first and then try reinstalling (-Syu option).

Maybe try different mirrors e.g. Germany?

[Telcoced]

@Telcoced

pamac-tray-icon-plasma

Thanks for your answer. It was related to my database, had to do

sudo rm /var/lib/pacman/sync/*
sudo pacman-mirrors -g

Everything is back, had to reinstall what I removed and voilaaaa.

[Fabitanker]

Since moving to 6.13 kernel some days ago (and moving to the nnn file manager) i experienced some CPU soft locks. (in the logs)
This will hang the entire system, no mouse movement, no keyboard light activity and TTY also not showing.
Running Intel 13600KF (Raptor lake)
Almost always with the system pretty much idle but heavy I/O activities to a USB thumb drive.
Could this be related to 6.13?
I moved back to 6.12 for now.

[philm]

6.13 is a release candidate kernel for now. It may have some regressions and should not been used for production systems.