https://bugs.kde.org/show_bug.cgi?id=516036
Bug ID: 516036
Summary: Discover can't update system packages because of unmet
dependencies
Classification: Applications
Product: Discover
Version First 6.5.5
Reported In:
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Updates
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
Target Milestone: ---
Created attachment 189615
--> https://bugs.kde.org/attachment.cgi?id=189615&action=edit
Discover - error message screenshot
SUMMARY
Discover can't apply system updates because some packages have "unmet
dependencies".
STEPS TO REPRODUCE
1. Open discover and try to apply system updates
(As this problem is maybe just limited to my system, I try to help out with
this as best as I can)
OBSERVED RESULT
Discover does error out because some packages have "unmet dependencies"
EXPECTED RESULT
Discover applies system updates. Right now 408 packages are waiting to be
updated and it seems like just a hand full of dependencies are the problem.
Those dependencies could be in heavy use and be the center of the problem for
all packages, but if not I would expect Discover to try to update all packages
that could be updated.
SOFTWARE/OS VERSIONS
Discover:
- Version 6.5.5
System:
- Operating System: KDE neon User Edition
- KDE Plasma Version: 6.5.5
- KDE Frameworks Version: 6.22.0
- Qt Version: 6.10.1
- Kernel Version: 6.14.0-37-generic (64-bit)
- Graphics Platform: Wayland
ERROR MESSAGE
<html>Auflösung der Abhängigkeit fehlgeschlagen:<br/><br/>The following
packages have unmet dependencies:
libgwengui-qt6-79t64: Beschädigt: libgwengui-qt5-79 (<
5.14.1-1~bpo13+2+24.04+noble+release+build12)
Beschädigt: libgwengui-qt5-79t64 (<
5.14.1-1~bpo13+2+24.04+noble+release+build12) but 5.10.2-2.1build4 is to be
installed
Beschädigt: libgwengui-qt6-79 (<
5.14.1-1~bpo13+2+24.04+noble+release+build12)
</html>
ADDITIONAL INFORMATION
This problem is maybe connected to bug 515150:
https://bugs.kde.org/show_bug.cgi?id=515150
I'm not sure if something like this exists or is even possible, but I suggest
Discover to have some kind of 'safe mode' (or if something like this exists
expose it to the average user on update failure).
This 'safe mode' could handle problems like this and resolve them.
I try to approach this from a completely non-tech user side of view ('ordinary
user'). This 'ordinary user' would be fine with using a GUI to update, but does
not know who to or want to interact with the command line.
The problem here could probably be fixed via the command line and just force
some updates, but how would such an 'ordinary user' handle this?
--
You are receiving this mail because:
You are watching all bug changes.
