|
Bugzilla – Full Text Bug Listing |
| Summary: | starting repository manager from online update crashes yast2 | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.0 | Reporter: | Carl Troein <ctroein> |
| Component: | YaST2 | Assignee: | Jiří Suchomel <jsuchome> |
| Status: | RESOLVED INVALID | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | yli |
| Version: | Factory | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 11.0 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
screenshot_SLED11
/var/log/YaST2 |
||
|
Description
Carl Troein
2008-05-11 15:38:04 UTC
you are running factory. Could you give the exact version of the involved packages? Just execute: rpm -qa 'yast2-*' I think I still have the same versions as on the beta 1 DVD for x86_64. I added the factory repo primarily to resolve some dependency issue (which in turn might've been caused by some 3rd party repo - I wish I remembered). carl@davies:~/src/ostreo/tocmodel> cat /etc/SuSE-release openSUSE 11.0 (X86-64) Beta1 VERSION = 11.0 carl@davies:~/src/ostreo/tocmodel> rpm -qa 'yast2-*' yast2-libyui-2.16.45-2 yast2-xml-2.16.0-45 yast2-perl-bindings-2.16.6-4 yast2-apparmor-2.16.1-9 yast2-x11-2.15.11-120 yast2-fingerprint-reader-2.16.7-4 yast2-restore-2.16.2-4 yast2-metapackage-handler-0.8.3-2 yast2-profile-manager-2.16.1-4 yast2-theme-openSUSE-Oxygen-2.16.21-2 yast2-ncurses-pkg-2.16.6-11 yast2-pam-2.16.1-12 yast2-irda-2.16.1-4 yast2-runlevel-2.16.3-4 yast2-online-update-2.16.11-4 yast2-users-2.16.27-2 yast2-core-2.16.48-2 yast2-nfs-client-2.16.1-4 yast2-ntp-client-2.16.7-6 yast2-scanner-2.16.5-3 yast2-support-2.15.4-12 yast2-bootloader-2.16.10-2 yast2-kerberos-client-2.16.10-4 yast2-security-2.16.0-4 yast2-backup-2.16.4-4 yast2-network-2.16.38-4 yast2-sudo-2.16.1-4 yast2-printer-2.16.14-3 yast2-qt-2.16.41-4 yast2-country-data-2.16.17-4 yast2-theme-openSUSE-2.16.21-2 yast2-storage-lib-2.16.18-3 yast2-ycp-ui-bindings-2.16.45-2 yast2-transfer-2.16.1-55 yast2-hardware-detection-2.16.1-31 yast2-update-2.16.6-4 yast2-mouse-2.16.1-4 yast2-storage-2.16.18-3 yast2-sysconfig-2.16.0-6 yast2-tv-2.16.4-7 yast2-tune-2.16.1-9 yast2-repair-2.16.8-4 yast2-iscsi-client-2.16.9-4 yast2-online-update-frontend-2.16.11-4 yast2-mail-2.16.1-4 yast2-control-center-qt-2.16.0-40 yast2-registration-2.16.1-24 yast2-trans-stats-2.15.0-74 yast2-ncurses-2.16.24-4 yast2-slp-2.16.0-4 yast2-sound-2.16.8-4 yast2-ldap-2.16.0-31 yast2-nis-client-2.16.2-4 yast2-packager-2.16.34-4 yast2-ldap-client-2.16.13-4 yast2-qt-pkg-2.16.36-4 yast2-instserver-2.16.3-4 yast2-pkg-bindings-2.16.28-5 yast2-firewall-2.16.2-4 yast2-country-2.16.17-4 yast2-installation-2.16.37-2 yast2-add-on-2.16.3-4 yast2-inetd-2.16.0-4 yast2-control-center-2.16.0-40 yast2-trans-en_US-2.16.2-8 Please next time remove NEEDINFO status by selecting "This comment/atachment provides ..." checkbox after supplying needed information. Jiri, since the link to repo manager is now only optional, please, check if it is offered in online update (I don't think it should really be there). It is not there in current version Created attachment 255137 [details]
screenshot_SLED11
I found a similar bug on SLED 11 beta5 x86_64, please refer the attached screenshot.
You could fellow below steps to reproduce this bug:
1) Install SLED 11 on a clean machine;
2) Login GNOME with root user;
3) Go to "YaST>Software>Online Update Configuration", the "Online Update Configuration" windows should be launched properly;
4) Select "Edit Software Repositories" item from "Advanced" check down list;
Actual result:
An "Accessing the Package Management Failed" warning popup;
Expected result:
The "Configured Software Repositories - YaST" windows should popup properly.
Created attachment 255138 [details]
/var/log/YaST2
Because I am not the reporter of bug 389163, so I haven’t changed the status of it. If you need, I could report a new bug for this issue. Please file a separate bug report (In reply to comment #9 from Jiri Suchomel) > Please file a separate bug report > Thanks for your reply, I have reported bug 449011 separately. BTW, maybe the bug 389163 should be closed, because it has been fixed over a year. :-) |