|
Bugzilla – Full Text Bug Listing |
| Summary: | Yast2 doesn't display some package summaries | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Kang-Jin Lee <lee> |
| Component: | YaST2 | Assignee: | Jiri Srain <jsrain> |
| Status: | RESOLVED WONTFIX | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Minor | ||
| Priority: | P5 - None | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | SuSE Linux 10.0 | ||
| Whiteboard: | |||
| Found By: | Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | Screenshot of yast2 with missing package descriptions/summary | ||
|
Description
Kang-Jin Lee
2005-10-20 09:11:46 UTC
Please have a look at http://www.opensuse.org/Submit_a_bug#Reporting_a_Bug All SUSE Linux OSS bugs should go into the product SUSE LINUX 10.0 or newer, because SUSE Linux is based on the SUSE Linux OSS code base. Always choose the right product when reporting a bug could you please give an example? works here. please add also /var/log/y2log after trying that again. Which Version of 10.0, which language are you using? *** Bug 128604 has been marked as a duplicate of this bug. *** /etc/SuSE-release says: SUSE LINUX 10.0 (X86-64) OSS VERSION = 10.0 Language: German Here is a piece of logfile on a x86_64 machine: 2005-10-15 16:29:30 <2> bee(7691) [packagemanager] ULPackagesParser.cc(fromCache):378 Share package '3ddiag 0.728 2 ppc' not found 2005-10-15 16:29:30 <2> bee(7691) [packagemanager] ULPackagesParser.cc(fromCache):378 Share package '3dto3d 3.5 22 ppc' not found 2005-10-15 16:29:30 <2> bee(7691) [packagemanager] ULPackagesParser.cc(fromCache):378 Share package '855resolution 0.4 3 ppc' not found Please attach the whole logfile and name an example-package which does not work correctly. Created attachment 55790 [details]
Screenshot of yast2 with missing package descriptions/summary
This is a screenshot of yast2 showing the missing package descriptions and summaries. This should be reproduceable with just a few clicks, but if you have trouble to reproduce the problem, then it must be something wrong with my system rather than a bug. So, if yast2 on your x86_64 testsystem doesn't look like the provided screenshot, please close the bug.
I guess this is a x86_64-specific problem. Jiri: Is it possible for you to check this out? I goofed up the initial bug report but isn't the "Hardware" flag not to report architecture specific problems? I see this problem on x86_64. On i586 it works as expected. As this is happening on 10.0, I'll just close this bug WONTFIX now. Please feel free to retest on 10.1 >= beta9 and reopen in case this problem persists. (I haven't seen it with my recent installation tests.) You forgot to mark the bug as WONTFIX ;-) |