update conflict - users

RE: update conflict

einar.hjortdal — Tue, 26 May 2026 22:42:39 +0000

Moving .config worked. Unfortunately I have to pick and restore some directories within it. But I guess this case is closed. Thank you for the support

RE: update conflict

Silvan — Tue, 26 May 2026 22:20:13 +0000

Package updates do not touch user settings directly, but a major KDE or Qt update can make existing configuration files incompatible with the new version — the application then reads an old config it no longer understands and crashes. The relevant directories are: ~/.cache/ — safe to wipe entirely, it is always regenerated ~/.config/ — KDE and Qt configuration files ~/.local/share/ — KDE local data (including KWallet) Start with ~/.cache/ alone, as it sometimes resolves issues without losing any settings. If crashes persist, move ~/.config/ and ~/.local/share/ aside (rename, do not delete) and KDE will recreate them from scratch on next login.

RE: update conflict

einar.hjortdal — Tue, 26 May 2026 22:18:21 +0000

Actually, I just remembered that this morning, the older version of plasma was working fine with this home directory. And the first time these issues appeared was when the system updated to the latest plasma packages. Therefore, the new plasma version must not like whatever is contained in these user settings that are perfectly fine with older versions of plasma.

RE: update conflict

einar.hjortdal — Tue, 26 May 2026 21:56:08 +0000

You were correct, the new user does not have these issues. I did not suspect user settings because I did not change any. Because I did not change any, I don't know which is causing the issues. Are you aware of any setting being touched by the packages at update? I doubt they touch user settings though... Just what happened? 🤔 I could even wipe them all, if I knew which directories to wipe

RE: update conflict

Silvan — Tue, 26 May 2026 21:34:14 +0000

Looking at the Calamares log, the installation kept the existing home directory, so all previous KDE/KWallet configuration files were preserved — including any corrupted settings. This is very likely the cause of the persistent crashes. Please test with a new user account to confirm: sudo useradd -m testuser && sudo passwd testuser Log out and log in as testuser. If everything works there, the problem lies in the configuration files in your home directory.

RE: update conflict

einar.hjortdal — Tue, 26 May 2026 20:30:10 +0000

Thank you for looking into this issue. I have now installed openmamba using the new livecd image. The app menu does work correctly now in the live environment. At the end of the install process, calamares fails to unmount the partitions, but I don't think this causes the issues I am experiencing. Here is the calamares log file: https://termbin.com/0bax I am experiencing the same crashes right in the first boot. I have not updated nor installed any packages. I have not run dnf at all. Please advise what to do in order to debug the situation.

RE: update conflict

Silvan — Tue, 26 May 2026 16:19:48 +0000

Checks on the livecd ISO image revealed that due to a bug in the images creation scripts all the recently published iso images were indeed the same image creared two months ago. So the livecd ISO image has been fixed today and the other fixed ISO images will be released within the next two days. Please note that the fixed livecd image has the same name and date of the one released last night so make sure you have downloaded it after the date of this post comment or check the MD5 reported on the site. Contextually it has been confirmed that the bug in the application menu was caused by the absence of the plasma5support package and this has been fixed for new ISO images. No other general problems have been reproduced, including the calamares installer which completed installation tests without crashing. For any problem that would persist it is required to report after trying the flow based on the fixed live ISO images. Thank you for reporting.

RE: update conflict

einar.hjortdal — Tue, 26 May 2026 08:30:21 +0000

I have managed to find an old livecd image from june 2025, and I have installed it. I have not installed nor updated any package yet. I could update each package until the problem occurs again, so that we would know which package causes it. Would this help? What packages should I upgrade and in what order? Do you have suspicions?

RE: update conflict

einar.hjortdal — Tue, 26 May 2026 06:42:33 +0000

I believe the AI is misleading you: I have removed nvidia_470 and nothing changed, except for even worse performance, because of course now everything is cpu rendered


glxinfo | grep "OpenGL renderer"
OpenGL renderer string: llvmpipe (LLVM 22.1.5, 256 bits)

RE: update conflict

Silvan — Mon, 25 May 2026 23:24:15 +0000

After a closer look, the ICU library conflict we found (multiple versions of libicuuc loaded via the hfstospell → libxml++ chain) is a packaging issue we will fix, but it is probably not the cause of your crashes — otherwise other users with the same packages would also be affected. What is unique to your system is the NVIDIA GTX 780 with the legacy nvidia_470 driver. This is a very old driver (Kepler architecture, 2014) and Qt6 6.11 is a very recent release. The crashes happen consistently during rendering (scrolling), and the segfault is inside libQt6Core during X11 rendering operations. This is consistent with a Qt6 6.11 / nvidia_470 driver incompatibility, where Qt uses a GLX code path that the old driver does not handle correctly. This would also explain why Edge and VSCode work fine (they have their own graphics stack) and why other users do not see this issue. Unfortunately there is no easy fix on our side for a proprietary legacy driver issue. A few things worth trying: 1. Force software rendering for Qt6 to see if that makes the crashes disappear: QT_XCB_GL_INTEGRATION=none kate -n 2. If that helps, you can make it permanent for all Qt6 apps: echo "export QT_XCB_GL_INTEGRATION=none" >> ~/.profile 3. Alternatively, try with the nouveau open-source driver if that is an option for you.