12 posts were split to a new topic: Package manager discussion from stable updates thread
Update went smoothly, no hiccups at all.
My system started with XFCE, which I still have, but I later added KDE, which I use daily (click my avatar circle to see the other parameters of my system).
I was able to update. Although I had to use the reset button on my case because when I executed the reboot command my fans kept spinning but the peripherals turned off. I suspect is because of the issue I posted about on the last update topic where the commands and plasma menu for reboot and turn off didn’t fully work. The solution had been to log out and turn off on SDDM. I’ll report back if that’s still the case.
Update all went smoothly, just curious, is there a reason every time the update puts me up on 7.1.4 instead of the LTS? What are the main benefits of the 7.1.4 kernel? I’ve been using 6.18 LTS
You probably have the linux-meta package installed, which will replace any EOL kernels on your system which are no longer in the repos with the latest stable release kernel from the repos. So, if you had linux70 or linux619 installed on your system, then the linux-meta package would have removed them and added linux71 to your system.
linux-meta is not a required package. You can safely remove it from your system if you want to manage your installed kernels yourself.
5 Likes
this comes with new version fontconfig 2.18.2, alas i have the same problem as with 2.18.1: broken (monospace) fonts in vivaldi menu (chrome based browser).
downgraded back to 2.17.1 - all good again.
2 Likes
2 posts were split to a new topic: Deepin package conflicts on latest stable update
If you have both 7.1 and 6.18 installed, grub will by default boot the kernel with the highest version number. That’s just how grub was designed.
Also, the option used to exist to have grub save the last-booted entry, but this does not work if /boot is on btrfs, because grub cannot write to btrfs.
Well, you’d have to talk to The Man™ (@philm) about that. 
The reason why octopi doesn’t give you the full list of AUR packages is that it was designed to not DoS the AUR. pamac did do that, with as a result that Manjaro users with pamac got temporarily banned from the AUR.
The problem was then remedied by letting pamac use a local AUR cache instead.
4 Likes
I had a couple of small problems with this upgrade.
- wine applications (tested on GTA4) fail to capture mouse movements. however, they can capture mouse clicks. downgraded wine (11.13-1 → 11.12-1). I’m using compiz. I think it’s wayland related because I’ve been having this sort of problems ever since wayland was introduced about a couple of years ago. various apps fail to capture mouse clicks and/or movements and/or keyboard presses. most notably mate-screensaver and full-screen wine games.
- ffmpeg-libfdk_aac (AUR) was throwing some error because one of its dependencies updated. rebuilt ffmpeg-libfdk_aac.
The shut down issue continues to be present. I have to log out and then shut down from SDDM. The kernel I’m using is 7.1.4-1
So it cannot be a kernel issue but is instead a plasma issue, if you can shut down from ssdm (or tty very probably? - systemctl poweroff)
2 Likes
A post was split to a new topic: Suspend not working following Stable Update 2026-07-23
My Nvidia drivers had some catastrophic problems, and I couldn’t have any UI on startup.
Had to restore a Timeshift snapshot from before the update, and now I’m not sure what to exclude. I believe I need to keep Nvidia 580xx drivers, and nothing starting with a 6.
1 Like
This depends on the GPU. I do not have extensive experience with Nvidia and the only system I have with Nvidia is using the Intel/Nvidia 5070 combo.
If you are certain that your GPU runs with a single Nvidia GPU and you must use 580xx then you can instruct the system to use 580xx
mhwd -i pci video-nvidia-580xx
If your system is a laptop with a dual GPU then you can do the same with a hybrid driver - replace the {amd|intel} with either amd or intel based on your system.
mhwd -i pci video-hybrid-{amd|intel}-nvidia-580xx-prime
Another option is to cherry pick the driver for your kernel e.g. kernel 6.18 linux618-nvidia-580xx and install it using pamac or pacman
pamac install linux-nvidia-580xx
Optionally you can use the open driver
pamac install linux-nvidia-580xx-open
2 Likes
6 posts were split to a new topic: Why isn’t the latest official .ISO built with the current updates?
A post was split to a new topic: Unable to start Wayland session after last update
I am indeed running an Intel CPU and an Nvidia GPU combo. The GPU is an RTX 3060 Ti, to be exact. Not the newest in the world, but should still be actively supported, I think.
Also, on xfce, if that affects the process at all.
Before, in a previous big update, I had a boot problem, and I believe I commanded my system to stick with the 580xx driver. Maybe that old terminal command is now conflicting with the new big update.
I removed spectacle before i updated and evaded the bloat.
I replaced it with Flameshot.
1 Like
libffi dependency is still an issue:
sudo pacman -Syu
[sudo] пароль для rstanislav:
:: Обновление баз данных пакетов...
core is up to date
extra is up to date
multilib is up to date
:: Запускается полное обновление системы...
разрешение зависимостей...
проверка конфликтов...
ошибка: не удалось подготовить транзакцию (не удалось удовлетворить зависимости)
:: installing libffi (3.7.1-1) breaks dependency 'libffi=3.6.0' required by lib32-libffi
Update you mirror list, looks like an unsync’d mirror, both packages have been updated to 3.7.1-1 already.
1 Like