[Stable Update] 2025-02-04 - Kernels, KDE, XFCE, Mesa, Cosmic, Systemd

Having issue

conflicting files:
- /usr/lib/modules/6.1.120-1-rt47-MANJARO/extramodules/Module.symvers exists in both linux61-rt-broadcom-wl and linux61-rt-virtualbox-host-modules
- /usr/lib/modules/6.6.65-1-rt47-MANJARO/extramodules/Module.symvers exists in both linux66-rt-broadcom-wl and linux66-rt-virtualbox-host-modules

Edit: Fixed it, removed kernels and it worked fine.

I got

(30/37) Reloading GVFS config...
pkill: not a hex string: fffffffd7fc1feff
pkill: not a hex string: fffffffd7fc1eeff
pkill: not a hex string: fffffffd7fc1feff
pkill: not a hex string: fffffffd7fc1feff
pkill: not a hex string: fffffffd7fc1feff
pkill: not a hex string: fffffffd7fc1feff
pkill: not a hex string: fffffffd7fc1feff
pkill: not a hex string: fffffffd7fc1feff
pkill: not a hex string: fffffffd7fc1feff
pkill: not a hex string: fffffffd7fc1feff
pkill: not a hex string: fffffffd7fc1feff
pkill: not a hex string: fffffffd7fc1feff
pkill: not a hex string: fffffffd7fc1feff
pkill: not a hex string: fffffffd7fc1feff
pkill: not a hex string: fffffffd7fc1feff
pkill: not a hex string: fffffffd7fc1feff
pkill: not a hex string: fffffffd7fc1feff
pkill: not a hex string: fffffffd7fc1feff
pkill: not a hex string: fffffffd7fc1feff
pkill: not a hex string: fffffffd7fc1feff
pkill: not a hex string: fffffffd7fc1feff
pkill: not a hex string: fffffffd7fc1feff
pkill: not a hex string: fffffffd7fc1feff
pkill: not a hex string: fffffffd7fc1feff
pkill: not a hex string: fffffffd7fc1feff
pkill: not a hex string: fffffffd7fc1feff
pkill: not a hex string: fffffffd7fc1feff
pkill: not a hex string: fffffffd7fc1feff
pkill: not a hex string: fffffffd7fc1feff
pkill: not a hex string: fffffffd7fc1feff
pkill: not a hex string: fffffffd7fc1feff
pkill: not a hex string: fffffffd7fc1feff
pkill: not a hex string: fffffffd7fc1feff

Is this something to worry about?

installing qemu-common (9.2.0-2) breaks dependency 'qemu-common=9.1.2-1' required by qemu-system-cris

I have tried

$ sudo pacman -R qemu-system-cris                                                                                                                                                  
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: removing qemu-system-cris breaks dependency 'qemu-system-cris=9.1.2-1' required by qemu-emulators-full

And then

sudo pacman -R qemu-emulators-full                                                                                                                                               1 ↵
checking dependencies...
:: libvirt optionally requires qemu-emulators-full: Support of additional QEMU architectures
:: qemu-base optionally requires qemu-emulators-full: for all system emulators
:: qemu-desktop optionally requires qemu-emulators-full: for all system emulators

Packages (1) qemu-emulators-full-9.1.2-1

Total Removed Size:  0,05 MiB

:: Do you want to remove these packages? [Y/n] 

So…

1 Like

Update went well but during the restart I noticed extreme graphical glitches in the bootloader when selecting between Manjaro and Windows but afterwards it was fine. First time I had that.

I seems that everything went well here (scaring… 1048 packages!).

More than this: the kernel 6.12.11 is able to suspend and resume correctly my PC.

The only nitpicking things (at least for now) is that with the 6.12 kernel my log is spammed by:

Feb 04 20:34:29 ramoth wpa_supplicant[1624]: wlp3s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-50 noise=9999 txrate=585000
Feb 04 20:34:31 ramoth wpa_supplicant[1624]: wlp3s0: Reject scan trigger since one is already pending

(this doesn’t happen with 6.6.74)

Thanks to the developers!

See this Garuda forum post for a nice explanation:


We can’t really answer this for you, since only you know if you have VMs emulating obscure architectures. If you do not have this need, then the answer to your unspoken question seems evident in the word “optionally”.

2 Likes

Have issue with updated :frowning:

Total download size: 3,1 GB
Total installed size: 135,5 MB
Total removed size: 162,3 MB

Edit build files : [e]
Apply transaction ? [e/y/N] y

Download of plasma-workspace-wallpapers (6.2.5-1) started
Download of plasma-workspace-wallpapers (6.2.5-1) finished
Download of linux515 (5.15.177-1) started
Download of linux66 (6.6.74-1) finished
Download of breeze (6.2.5-1) started
621,0 MB/3,1 GB About 3 minutes remaining[1]    26038 terminated  pamac upgrade

╰─> echo $?                                                                                                                                                                                                                                                                                                                                                
143

And that’s all…

UPD: tried to refresh mirrors

Sounds like the same issue as mirto.

I’m also experiencing it. Both GUI pamac-manager or the command-line pamac upgrade --download-only start downloading just fine, and after a while they crash with the message terminated and with exit code 143. Meanwhile, pamac-daemon continues running in the background, apparently downloading more packages. It’s using about 150% CPU, while dbus-broker and trans_run2|pacmac-daemon are using about 25%~35% each.

I’ve tried rebooting, at least twice, and it still happens. I’ll try later changing the mirrors.

1 Like

Yes, you are right, my message was not clear as to what I meant to say…

I have actually removed the conflicting packages, all ok, no problem.

But, isn’t it strange to have conflicting packages in the official repos?
That is what i was wondering about…

I think the answer to that question is “yes”. See

1 Like

All good apparently with minor inconveniences. I’m getting this so far when I try xflock4:

xflock4
Error: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method “Lock”

1 Like

Conflicting libprotobuf error due to clementine being built from the AUR. Removed clementine, install went through, then rebuilt clementine.

People who have issues with pamac on updating, may use pacman to get the updated libpamac. We hope to have fixed some known issues with those updates on future updates when using pamac.

3 Likes

UPDATE: I found my solution on another post and was able to update my primary laptop as well. Thank you Manjaro Team!!! Awesome OS!

Updated my older laptop and newest desktop both without any issues.

Went to update my primary laptop and in the manjaro GUI, I am not seeing the update shield (either red or white). When I try and update from the terminal (sudo pacman -Syu) I see the following…

:: Synchronizing package databases...
 core is up to date
 extra is up to date
 multilib is up to date
:: Starting full system upgrade...
error: could not read db 'extra' (Damaged tar archive)
error: could not read db 'extra' (Damaged tar archive)
error: could not read db 'extra' (Damaged tar archive)

Any suggestions? Thank you

UPDATE: I found my solution on another post and was able to update my primary laptop as well. Thank you Manjaro Team!!! Awesome OS!

2 Likes

Input Remapper is failing to open after this update, but I haven’t had time to look into it at all yet. I’ll try and figure it out this week if it doesn’t resolve itself.

Well, after pamac upgrade --download-only, I left the pamac-daemon running in background. Many minutes later, it finished all the downloads. (I noticed because I was observing the network traffic.)

Then, pamac upgrade worked correctly. Apparently it was breaking while downloading, but it works fine afterwards.

1 Like

I do most of my larger updates with pacman via Konsole or TTY, but my 70+ parents exclusively use pamac-gtk3, so I’d like to ask for some clarification on how I can help them (hopefully without having to drive hours to fully update them via pacman instead).

I took a look at what pamac files I have installed…

pacman -Qq | grep pamac                                                                                                   
libpamac
libpamac-flatpak-plugin
pamac-cli
pamac-gtk3
pamac-tray-icon-plasma

and a quick compare to what was listed in the pamac GUI to be installed yielded that all of the above packages have updates; except the GUI pamac-gtk3.

So will sudo pacman -S libpamac be enough, or should (minimally) the CLI (which I assume the GUI wraps) be installed as well? sudo pacman -S pamac-cli libpamac

Also, has anyone tried this as a “workaround” for the issue and had success?

1 Like

you could setup some like Remmina to have remote access to the PC for special tasks. Else there is Octopi, which uses pacman to install packages and is a GUI. Pamac has an option to download packages first before an update is made. You could pre-select that. Based on the reports it breaks on download process and a later restart of the UI make it work.

For sure we have to monitor that issue and fix it in upcoming releases of libpamac and pamac-cli.

Thank You for the reply @philm, I’ve looked at tools like Remmina before, but they require port forwarding and not as simple a teamviewer. Unfortunately teamviewer has flagged me as “not private use” when supporting them and refuses to connect.

I like the octopi idea though, so I’ll definitely look into that.

There is also AnyDesk from Germany, which is more user-friendly in that regard. TeamViewer is very restrictive lately. So I don’t recommend that one anymore.

4 Likes