[Stable Update] 2025-02-16 - Kernels, Firefox, Qt, KDE Gear, GNOME

[jofi]

Regarding versions all packages are on current stable.

When i opened Pamac from the plasma tray because there was an update, it started up in the Updates tab. I did the update (a single AUR package). Afterwards i switched from the Updates tab (showing system is up to date) to the Browse tab and the window froze and crashed. Now when i opened Pamac again it came up in the Browse tab and then there was no issue switching between tabs and or search. It was a Wayland session using Plasma and Pamac gtk4.

Now since i knew i have the same AUR package on a different machine where i use LxQt with openbox so still X11, i tried the same thing. Open from the tray icon being on the Updates tab. But here i couldn’t reproduce the crash. The package versions are identical (only plasma tray icon isn’t installed). Hope this helps.

Hmm, i can’t reproduce it with “pamac-manager --update” though.

[QAZXSW]

This update introduces an error in the lgammaf_r function inside glibc.

Test code:

#include <iostream>
#include <cmath>

int main()
{
  int dsgngam;
  double dresult = lgamma_r (double (-1.0), &dsgngam);

  int fsgngam;
  float fresult = lgammaf_r (float (-1.0), &fsgngam);
  
  std::cout << "dresult = " << dresult << " dsgngam = " << dsgngam << '\n'
            << "fresult = " << fresult << " fsgngam = " << fsgngam << '\n' ;
}

With current gcc from the repositories:

$ g++ lgam.cc 

$ ./a.out 
dresult = inf dsgngam = 1
fresult = inf fsgngam = -1

With current clang from the repositories:

$ clang++ lgam.cc 

$ ./a.out 
dresult = inf dsgngam = 1
fresult = inf fsgngam = -1

Both dsgngam and fsgngam should be +1 for both gcc and clang but the float case gives -1 for both compilers.

The sign of the gamma function should only depend on the value of the input (-1) and not on whether it was float or double, but this version of glibc erroneously treats those datatypes differently and reports that one is positive and the other is negative.

This was working normally until the 2025-02-16 stable update, when it broke.

This discrepancy in turn results in unit test failures in downstream numerical software.

[RiCK-Man-jaro]

pamac-manager                                                                                                                                                                                     

(pamac-manager:2758): Adwaita-WARNING **: 12:01:45.697: Using GtkSettings:gtk-application-prefer-dark-theme with libadwaita is unsupported. Please use AdwStyleManager:color-scheme instead.
zsh: segmentation fault (core dumped)  pamac-manager

KDE Plasma 6.2.5
pamac-cli 11.7.3  -  libpamac 11.7.2
(pamac-manager) Pamac  11.7.2-2

Launching via menu or shortcut icon, the following errors are observed in notifications:

Launching Add/Remove Software
(Failed)
Remote peer disconnected

Launching Add/Remove Software
(Failed)
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. 

…

pamac-manager %U

This gets it running, and after closing, it can be launched from menu or shortcut icon. However, it will revert to not opening once again.
…
3/2/25: update to:

libpamac 11.7.3

Still crashing though.

[Gkirmathal]

Strange. On desktop decided to change to pamac-gtk3, my laptop uses it no issue with pamac-manager.

On desktop accidentally opened pamac-manager is sys tray, it opened on Browse and no segfault crash. Could search packages and use Browse.

As test I quit pamac-manager via tray update-notifier and restarted pamac-manager`. This immediately resulted in a the earlier segfault crash.

Tested the laptop by exiting pamac-manager via tray update-notifier and restarting it. It does not crash. So I swapped to gkt3 on desktop and will test after reboot.

Edit: swapping to pamac-gtk3 fixes the crashing on my desktop.

[ciacnorris]

On KDE+X11, after the last update Chromium browser freezes my computer and I have to hard reboot. This happens sometimes as soon as I run Chromium, sometimes after it has worked for a while.
I had not updated for a couple of months, so this may not be strictly related to the last update.

[luzpaz]

I spoke too soon? Not sure if this is an issue caused by update or a separate bug. I have an external HDMI screen that suddenly isn’t being recognized correctly (not showing proper resolution and missing a legit name… (it may have been triggered by connecting the HDMI at some random point in the boot sequence and triggered some edgecase bug?)

I tried removing configs like .local/share/kscreen/ and .config/kwinoutputconfig.json and rebooted in order to reset the display configs, and that didn’t work.

[Loacoon]

I confirm the Pamac crashing issue with the same error.
Another problem after this update, MPV won’t start saying that the SDL version is too old.

[Takakage]

For those few who have not yet updated, we could perhaps repeat the common advice to

1. Update regular repository packages first with
   • pamac update --no-aur
   • or
   • sudo pacman -Syu
2. Then, if needed, update AUR packages.

[ehhen]

About the fcitx issue.
I think you should add a comment here. I (ja_JP) have no problems at all, but I think the number of people using unnecessary languages ​​is overwhelming.

@philm

Additional Info

Python 3.13 info…

[nikgnomic]

@Takakage

we could perhaps repeat the common advice to

1. Update regular repository packages first
2. Then, if needed, update AUR packages.

Pamac GUI users can de-select AUR packages before updating repository packages
Or turn off option to update AUR packages in preferences and use Pamac CLI to build AUR packages
Or use CLI to update repository before building AUR packages

[Mirdarthos]

This is exactly what mumuh does for you. So here’s the link again:

GitHub - Mirdarthos/manjaro-update-helper: a Helper script for updating Manjaro.

[a-sassermann]

After this update firefox started to show GTK dialogs instead of KDE.

Had do set

GTK_USE_PORTAL=1

in /etc/environment.

This requires package xdg-desktop-portal-kde which has been installed 2 weeks ago.

I also faced the Keyboard issues due to fcitx5. Removed fcitx-* added german keyboard layout and chose no virtual keyboard. Now it seems to be ok.

[nl.smart]

Hi,

Issue on stable branch with pamac (stable 11.7.2-2.1), not possible to launch pamac.
I installed pamac (testing 11.7.2-3), no issue, pamac works on my stable branch laptop.

[beermad]

Regarding the fcitx issue, someone I think is a KDE dev did a bit of detective work and posted this explanation on Reddit.

SDL2 wrongly has fcitx5 set as a build dependency in the Arch package due to a packaging mistake (sdl3: fcitx5 is not needed as a make dependency (!1) · Merge requests · Arch Linux / Packaging / Packages / sdl3 · GitLab). Trying to compile the package will install fcitx5.

This was likely caused be the confusing SDL documentation on this (Remove unnecessary fcitx's devel package dependency in linux doc by wengxt · Pull Request #12372 · libsdl-org/SDL · GitHub). You don’t actually need fcitx5 to build SDL2.

The SDL2 package was replaced by a compatibility package and the original SDL2 was moved to the AUR (After update, keyboard layout settings now get reset at every restart - #2 by scotty65).

Packages being moved this way confuses pamac, even though the old package isn’t necessary anymore, it will still try to build it from source from the AUR because it doesn’t know yet that the package isn’t needed anymore. (Please make the upgrade process a two step process: First upgrade repo packages only, then upgrade AUR packages · Issue #488 · manjaro/pamac · GitHub).

So if a user had SDL2 installed, the AUR enabled, and did not use an automatic tool to clean build dependencies, a combination of minor flubs and weird interactions would lead to fcitx5 being randomly installed on people’s computers.

Plasma has nothing to do with it, we’re not involved here at all (except that we could do a better job of telling people that fcitx5 is active). We just get the blame in the end.

I’d be interested in people not on Manjaro where this happened though.