Bug 172115

Summary:	Even when dependencies have been resolved in the package manager, it still presents the dialog for dependency errors and won't let me exit.
Product:	[openSUSE] openSUSE 10.3	Reporter:	Jonathan Davis <jmdavisProg>
Component:	Installation	Assignee:	Stefan Schubert <schubi>
Status:	RESOLVED DUPLICATE	QA Contact:	Stanislav Visnovsky <visnov>
Severity:	Critical
Priority:	P5 - None	CC:	aj, bjoernv, schubi, suse-beta
Version:	Beta 2
Target Milestone:	---
Hardware:	i386
OS:	openSUSE 10.3
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	empty dependency dialog in openSUSE 10.3 (factory)

Description Jonathan Davis 2006-05-03 07:15:13 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.

Comment 1 Andreas Jaeger 2006-05-03 08:55:07 UTC

Please provide the yast log files.

Comment 2 Andreas Jaeger 2006-05-03 08:55:38 UTC

Is this an installation from the factory tree?

Do you have dependency errors due to dbus-1 packages?

Comment 3 Andreas Jaeger 2006-05-03 17:10:44 UTC

WE had known bugs in the factory tree that are only now resolved.  I'm downgrading this unless we get log files.

Comment 4 Jonathan Davis 2006-05-03 18:30:12 UTC

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.

Comment 5 Klaus Kämpf 2006-05-03 19:12:34 UTC

see http://en.opensuse.org/Bug_Reporting_FAQ#YaST on how to attach logs

Comment 6 Jonathan Davis 2006-05-05 00:22:57 UTC

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.

Comment 7 Klaus Kämpf 2006-05-08 12:19:40 UTC

Closing for now. Please reopen if it happens again.

Comment 8 Björn Voigt 2007-09-02 22:14:52 UTC

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.

Comment 9 Björn Voigt 2007-09-02 22:17:17 UTC

Created attachment 161392 [details]
empty dependency dialog in openSUSE 10.3 (factory)

Comment 10 Björn Voigt 2007-09-02 22:18:20 UTC

I reopen this bug, because I think, that the bug still exists in openSUSE 10.3 (current factory).

Comment 11 Klaus Kämpf 2007-09-03 13:16:54 UTC

Stefan, Stefan, for you ;-)

Comment 12 Stefan Hundhammer 2007-09-03 14:03:23 UTC

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.

Comment 13 Stefan Schubert 2007-09-04 08:44:15 UTC

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 ***