Bugzilla – Bug 172115
Even when dependencies have been resolved in the package manager, it still presents the dialog for dependency errors and won't let me exit.
Last modified: 2007-09-04 08:44:15 UTC
I tried to upgrade to SUSE 10.1 from 10.0 with "SUSE-Linux-10.1-RC3-x86_64-mini.iso". When I used the package manager during the installation to manage which packages I wanted to add, remove, etc., it of course complained about dependency issues when I clicked on "Accept". I then made all of the appropriate selections to remove packages, add packages, ignore dependencies or whatnot to resolve all of the dependency errors. I then click on on the "Try Again" button. It tries again and then instead of showing a dialog that says that all the dependencies have been resolved and exiting the package manager, it instead shows the box for resolving dependency errors, only it's empty. Any time that I try and exit the package manager - other than canceling out of it - it shows the box complaining about dependency issues, even if there aren't any. The box is empty. But as I cannot exit the package manager until it is happy that all of the dependencies have been resolved, I can never successfully exit the package manager except by canceling out. If there are no dependency errors, the package manager needs to let me exit. Either there are dependency errors that it's not showing me, or it won't acknowledge that there are none left. At present, I cannot even install SUSE 10.1. I don't know if it matters or not, but I did add other repositories for the package manager to get packages from. It's possible that that's part of the problem, but either way, it needs to be fixed.
Please provide the yast log files.
Is this an installation from the factory tree? Do you have dependency errors due to dbus-1 packages?
WE had known bugs in the factory tree that are only now resolved. I'm downgrading this unless we get log files.
I did try to do the installation from the factory tree and I did have dependency errors with regards to dbus-1. However, the problem wasn't really that I had dependency errors. The problem was that after I had resolved or ignored them all, the package manager was still give me the dialog complaining about dependencies - only it was empty, so there was nothing that I could do to get it to exit without cancelling out and losing all the changes that I had made. Now, since I have no idea what would create this kind of problem, and honestly I have no clue what dbus-1 is, it's quite possible that the changes there will have done something. For that matter, the factory code in general is changing fast enough that maybe some other change has magically fixed it by now. Regardless, I'll try the install again tonight and see how it goes. I'll also get the log files for you if I can figure out how on earth to do that.... Thanks.
see http://en.opensuse.org/Bug_Reporting_FAQ#YaST on how to attach logs
Well, I once again attempted to update from 10.0 to 10.1, but this time, the package manager worked correctly. I have no clue why it worked this time and did not a few days ago. Presumably something was updated that fixed the problem. So, for the moment at least, it appears that this bug has been fixed. Unfortunately, either way, I was unable to get the log files for you because the update failed for other reasons. I was forced install 10.1 with a new installation instead. But regardless, this bug appears to have gone away now. So, unless someone else reports a similar problem you can probably consider it to be fixed - or at least irreproducable at the moment. Sorry if I wasted your time. Thanks for all you hard work.
Closing for now. Please reopen if it happens again.
I still have this problem in openSUSE 10.3 Beta 2 (current factory installation source from FTP mirrors). After solving many dependency problems during an update from openSUSE 10.2 the empty dependency dialog remains on screen. See attached screenshot.
Created attachment 161392 [details] empty dependency dialog in openSUSE 10.3 (factory)
I reopen this bug, because I think, that the bug still exists in openSUSE 10.3 (current factory).
Stefan, Stefan, for you ;-)
The UI displays that dependency dialog if zypp::getZYpp()->resolver()->resolvePool() returns 'false'. In that case, it populates the problems list with zypp::getZYpp()->resolver()->problems(). If there is an empty problems list, the resolvePool() call should not return 'false'. This problem description sounds like exactly that happened.
The reasons have been different to the inital (first) empty popup. The other reasons should be fixed too. *** This bug has been marked as a duplicate of bug 302496 ***