[Stable Update] 2025-05-14 - Kernels, Firefox, Thunderbird, Mesa, Plasma, LibreOffice, QEMU

Announcements Stable Updates
22

Preparing…
Synchronizing package databases…
Error: restricting filesystem access failed because landlock is not supported by the kernel!
Warning: installing libxml2 (2.14.2-2) breaks dependency ‘libxml2.so=2-64’ required by rest
Add rest to remove
Failed to prepare transaction:
could not satisfy dependencies:

  • removing rest breaks dependency ‘rest’ required by lib32-rest
    Resolving dependencies…
    Checking inter-conflicts…
    Failed to prepare transaction:
    could not satisfy dependencies:
  • removing rest breaks dependency ‘rest’ required by lib32-rest

Any ideas on this one ? Thanks

1 Like
23

It appears your mirror(s) are not in sync. Update your mirror list and try again.

EDIT: Actually, rest and lib32-rest were dropped from the repos and nothing requires them. They can be safely removed

1 Like
25

Hint: It was never there to begin with. :wink:
Setting ZSH as the default shell is set by Calamares during installation which adds it to /etc/shells. The same thing happens if one changes their default shell to something else; i.e, Fish, etc.

So if I reinstall the whole distro, should I change to bash after installation?

26

Not sure what happened exactly but I was letting the update run in the background since it was taking longer than usual, and suddenly when the process was just about done (possibly fully finished) I got logged out and dumped back to the login screen with no warning. (KDE Plasma).

27

Are you sure it was effectively the login screen (sddm) and not the screen locker (kscreenlocker)?

Many people tend to get the two mixed up because they look very much alike.

28

It was the login screen. I know because I have different backgrounds for the two. Additionally my second monitor is vertical/sideways, and on the login screen that side is always the wrong orientation.

29

Well, in that case, your Plasma session probably crashed, which, although not everyone will experience that, is no surprise, really.

This Stable Update contained an update to Plasma itself, from 6.3.4 to 6.3.5 — see the first post of the thread. So the shared libraries that were going to be updated were in use while they were being overwritten.

I know nobody wants to hear it, but the safest way to apply a bundled update — especially if it involves your desktop environment — is to run it from the command line in a tty while completely logged out of the GUI environment. See… :point_down:

4 Likes
30

I’ll keep that in mind in the future. In any case, I rebooted and my system is fine.

31

3 posts were split to a new topic: Libxml2 dependency issue preventing update

33

Hi ! In my original /etc/hosts I have some additional entries like :

::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

Should I keep this ip6 stuff ?

1 Like
34

hi,

sure why not ? just looked on my debian vm and the entries you mentioned are there
the .pacnew is default, you can always add your hostname like this
your ip name host with domain hostname
example 192.whatever hostname.local.domain hostname

The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

checked my /etc/hosts and this should be sufficient
127.0.0.1 localhost
::1 localhost
127.0.1.1 your hostname.domain your hostname

2 Likes
35

Remove rest and its lib: https://bbs.archlinux.org/viewtopic.php?id=305276

1 Like
36

Only if you don’t mind the fact that you may have to re-learn some things you do in a terminal, as they do have some syntactical differences. Though if you don’ use the terminal extensively this may not matter to you.

37

passwd.pacnew

WHAT? :upside_down_face:

1 Like
38

Flawless update for me and thanks a lot for the warning concerning the pacnew-files!
Side note: After the update I was now able to build the current rstudio-desktop 2025.05.0 from AUR again. Before the manjaro update, compiling it was crashing with a segmentation fault at some point.

1 Like
39

Could someone please explain step by step what I should do after the update?

I understand it like this, finish the update, then change to /etc and delete the passwd.pacnew and shells.pacnew.
Is that correct?

40

yes indeed hopefully people do not copy it directly to the existing version.
Root only :yum: in /etc/passwd.pacnew.

imho people should read first what’s in .pacnew files

41

I did and it made me just not apply any of them. Because it’s so weird to even get these (except for shells maybe)

If files like these get a pacnew, I feel like it should be explained in the OP

42

Problem with updating a friend of mine and I are having:

❯ sudo pacman -Syu
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 multilib is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing libxml2 (2.14.2-2) breaks dependency 'libxml2.so=2-64' required by electron32
:: installing libxml2 (2.14.2-2) breaks dependency 'libxml2.so=2-64' required by electron33

We already tried resetting Pacman-mirrors with sudo pacman-mirrors --country all --api --protocols all --set-branch stable && sudo pacman -Syu

Still same problem… Any ideas what to do?

43

Remove the 2 AUR packages that are blocking the update:

sudo pacman -R electron32 electron33

Then run the update:

sudo pacman -Syu
2 Likes