|
Bugzilla – Full Text Bug Listing |
| Summary: | "Die Design-Datei /opt/kde3/share/apps/kdm/themes/SUSE kann nicht geöffnet werden" | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Christian Boltz <suse-beta> |
| Component: | Update Problems | Assignee: | Ludwig Nussel <lnussel> |
| Status: | VERIFIED FIXED | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | lnussel |
| Version: | Beta 1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | y2logs | ||
|
Description
Christian Boltz
2005-08-14 14:27:57 UTC
no idea what you did. the path is part of the package kdebase3-SUSE - is that version 10.0? I had the same behavior updating 9.3 => 10.0 Beta1. (Update in the running system) kdebase3-SUSE was not updated. I do not know why. After rpm -Uhv kdebase3-SUSE-10.0-xxxx.rpm and reboot everything works fine. It was not even installed :-( It must be an update problem - it is installed on my 9.3 installation (which I cloned before updating to 10.0) and IIRC YaST showed me that kdebase3-SuSE will be uninstalled while installing the update to 10.0 beta1. I installed the package manually with rpm -Uhv - now it works. So this is no longer a KDE problem - but maybe a upgrade bug. Decide yourself ;-) (Unfortunately I don't have the YaST logs from installation :-( ) I'm afraid without these yast logs we're doomed here. Without knowing the reason yast2 decided to deinstall it, there is nothing to do here. I was able to reproduce the problem and have y2logs now :-)
After solving several conflicts, I ended up with the following:
#### YaST2 conflicts list - generated 2005-08-17 20:04:15 ####
Konflikt mit hwinfo 11.9-2
Benötigt von:
3ddiag benötigt libhd.so.11
kdebase3-SuSE benötigt libhd.so.11
sax2 benötigt libhd.so.11
sax2-tools benötigt libhd.so.11
yast2-core benötigt libhd.so.11
sax2-libsax benötigt libhd.so.11
Konflikt mit:
hotplugctl benötigt libhd.so.10
Konfliktlösung:
( ) hwinfo nicht aktualisieren
( ) Alle 2 Pakete löschen, mit denen der Konflikt besteht
hotplugctl löschen
kdebase3-SuSE löschen
( ) Alle 67 entsprechenden Pakete löschen
3ddiag löschen
kdebase3-SuSE löschen
sax2 löschen
sax2-tools löschen
yast2-core löschen
yast2-vm nicht installieren
yast2-country löschen
yast2-firewall löschen
Weitere 59...
( ) Diesen Konflikt ignorieren und ein inkonsistentes
System riskieren
#### YaST2 conflicts list END ###
Created attachment 46369 [details]
y2logs
hotplugctl seems to be an outdated package. I wonder why yast wants to delete kdebase3-SUSE in both cases though comment #5 looks like a severly broken system but not a generic bug in the update. It's an error in the solver. kdebase3-SuSE-9.3 requires hotplugctl. The solver upgrades hwinfo first, discovers that it would break hotplugctl. It then tries to upgrade hotplugctl which is not possible. Therefore it puts it into the remove-to-solve-conflict list. Since removing hotplugctl would break kdebase3-SuSE it puts that into the list as well. The solver does not see at this point that kdebase3-SuSE is scheduled for update which would solve the conflic. So there are actually two different kdebase3-SuSE involved, the one in remove-to-solve conflict is version 9.3, the one in remove-referers is 10.0. Both map back to the same PMSelectable so clicking the solution to uninstall the 9.3 version results in not installing the 10.0 version either of course. The solution would be to pass down the candidates set to the remove_package function. Theoretically trivial but I'm not sure about possible side effects as it's a function called from many places. fixed in svn I just have the time for a round of VERIFIED - works as expected now (10.0 final). Thanks ;-) and have a good New Year! |