Bug 496968

Summary:	Installing a program breaks Neon, cannot start any apps
Product:	[KDE Neon] neon	Reporter:	David Nemeskey <nemeskey.david>
Component:	general	Assignee:	Neon Bugs <neon-bugs-null>
Status:	REPORTED ---
Severity:	normal	CC:	carlosd.kde, john.kizer, jr, neon-bugs-null
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Neon
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description David Nemeskey 2024-12-03 01:22:15 UTC

SUMMARY
If the system is not fully updated, it can happen that installing a program breaks the system.

STEPS TO REPRODUCE
1. Do not update Neon for a time
2. Install a program (in my case, it was the KDE Partition Manager)
3. Observe the below:

OBSERVED RESULT
The program is installed correctly, but then it cannot be started, nor can any other KDE-based (Qt-based?) program on the system. Apparently this is because the newly installed program is linked against a newer version of a library than what was available on the system, and this causes a conflict. I couldn't figure out which library / version to uninstall / reinstall and how. Updating the system solves the problem.

EXPECTED RESULT
The system / Discover / etc. should not allow the installation of programs that link to conflicting library versions.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon 6.2
KDE Plasma Version: 6.2.3
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.0

ADDITIONAL INFORMATION
The above versions are the versions *after* the update; obviously, the error happened before. However, I have experienced this issue with various versions of KDE Neon, so it is a problem inherent in how Neon / KDE handles updates, and not tied to a particular version.

Comment 1 David Nemeskey 2024-12-03 01:23:52 UTC

(Obviously, I could only update the system from a TTY, since no KDE programs could be started. I did not restart the system for fear of not being able to log in.)

Comment 2 John Kizer 2024-12-13 07:09:52 UTC

Hi - just to check, in your step 2 to reproduce, how was KDE Partition Manager installed? (Discover, pkcon, apt, etc.)

Thanks!

Comment 3 David Nemeskey 2024-12-19 11:07:02 UTC

(In reply to John Kizer from comment #2)
> Hi - just to check, in your step 2 to reproduce, how was KDE Partition
> Manager installed? (Discover, pkcon, apt, etc.)
> 
> Thanks!

Discover. apt would have handled the dependencies correctly, I reckon.

Comment 4 John Kizer 2024-12-19 19:18:27 UTC

Thanks, and do you have any error messages - from either starting the program that didn't work from the terminal, or from journalctl - that might help indicate a specific component that's throwing an error?

Comment 5 David Nemeskey 2025-01-01 13:21:58 UTC

Sorry, journalctl starts from Dec 12. Also, since I couldn't start Konsole, I couldn't get console error output at the time...