Bug 238579

Summary: Cannot select packages, blank dialog
Product: [openSUSE] openSUSE 10.2 Reporter: Aaron Williams <aaronw>
Component: InstallationAssignee: Ladislav Slezák <lslezak>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Blocker    
Priority: P5 - None    
Version: Final   
Target Milestone: ---   
Hardware: 64bit   
OS: Linux   
Whiteboard:
Found By: Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Output of conflicts.txt

Description Aaron Williams 2007-01-25 06:59:49 UTC 
After resolving conflicts, the installer shows a blank "Dependency Conflicts" dialog with "OK -- Try Again", "Expert" and "Cancel" buttons on the bottom.  Expert lets me save the conflicts.txt file, which contains 3 blank lines.  I cannot continue the installation because if I click "OK -- Try Again" I just get the same empty dialog.  I had really hoped Novell had fixed their package management after the 10.1 fiasco, but sadly it now looks worse than ever.

Note that this is booting off of the SuSE DVD I bought and I am upgrading from SuSE 10.1 on an X86-64 platform.

I cannot continue the install process until this is resolved.  At this point I am so fed up with Novell's package management that I'm ready to completely dump every SuSE system I maintain.
Comment 1 Cyril Hrubis 2007-01-25 14:42:28 UTC 
Please attach y2logs from this installation. If you are in doubt please follow:

http://en.opensuse.org/Bugs/YaST


Thanks!
Comment 2 Aaron Williams 2007-01-25 15:25:39 UTC 
Created attachment 115102 [details]
Output of conflicts.txt
Comment 3 Aaron Williams 2007-01-25 15:40:51 UTC 
Can't attach y2logs.tgz since it is too large.  I put it at http://www.doofus.org/aaronw/y2logs.tgz
Comment 4 Cyril Hrubis 2007-01-26 10:54:45 UTC 
Next time after aswering question or attaching logs please change bug status from needinfo to assigned, it makes searching for answered bugs easier.
Comment 5 Ladislav Slezák 2007-01-26 15:28:08 UTC 

*** This bug has been marked as a duplicate of bug 225218 ***