|
Bugzilla – Full Text Bug Listing |
| Summary: | Yast2 software management fails both in GUI and CLI(perhaps after update) | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.2 | Reporter: | Parameshwara Bhat <p.bhat> |
| Component: | YaST2 | Assignee: | E-mail List <yast2-maintainers> |
| Status: | VERIFIED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Major | ||
| Priority: | P5 - None | ||
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | openSUSE 11.2 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | YaST log file | ||
|
Description
Parameshwara Bhat
2010-05-09 20:20:27 UTC
*** Bug 604091 has been marked as a duplicate of this bug. *** *** Bug 604090 has been marked as a duplicate of this bug. *** Please attach YaST2 logs. It's actually helpful to attach them to (almost) every bug report for YaST. See http://en.opensuse.org/Bugs/YaST Please try also run Software Managment in text mode. try command "yast sw_single" (as root) I am sorry I was not able to follow up on my bug report. Now I am able to run software management both in gui and text mode normally.The yast versions have not changed as you can see below. pbhat@linux-9f6d:~> rpm -qa|grep yast yast2-registration-branding-openSUSE-2.18.0-2.4.noarch yast2-iscsi-client-2.18.6-2.2.noarch yast2-sudo-2.18.2-2.2.noarch yast2-qt-pkg-2.18.22-1.1.1.i586 yast2-branding-openSUSE-2.18.0-2.1.noarch yast2-nfs-client-2.18.0-2.2.noarch yast2-inetd-2.17.3-3.3.noarch yast2-x11-2.18.0-2.1.noarch yast2-firewall-2.18.1-1.1.2.noarch yast2-tune-2.18.1-2.2.i586 yast2-network-2.18.53-1.1.1.i586 autoyast2-installation-2.18.14-1.1.3.noarch yast2-profile-manager-2.18.2-2.2.i586 yast2-backup-2.18.5-0.1.1.noarch yast2-trans-en_US-2.18.1-16.19.1.noarch yast2-country-data-2.18.20-2.2.i586 yast2-xml-2.16.1-56.1.i586 yast2-ycp-ui-bindings-2.18.5-2.1.i586 yast2-perl-bindings-2.18.0-2.1.i586 yast2-hardware-detection-2.17.1-2.3.i586 yast2-scanner-2.18.0-2.2.i586 yast2-apparmor-2.18.4-1.1.1.noarch yast2-vm-2.16.10-3.1.i586 yast2-kerberos-client-2.18.3-2.2.noarch yast2-ncurses-2.18.11-0.1.1.i586 yast2-users-2.18.13-2.1.i586 yast2-samba-server-2.18.2-2.1.noarch yast2-ncurses-pkg-2.18.4-2.10.2.i586 yast2-slp-2.16.0-83.1.i586 yast2-2.18.25-2.5.i586 yast2-packager-2.18.13-1.1.3.i586 yast2-samba-client-2.18.3-2.2.noarch yast2-repair-2.18.3-2.4.noarch yast2-irda-2.18.2-0.1.1.noarch yast2-dbus-client-2.18.0-2.1.i586 yast2-runlevel-2.17.4-2.2.noarch yast2-ldap-2.17.3-9.1.i586 yast2-online-update-2.18.5-2.2.noarch yast2-update-2.18.6-2.3.i586 yast2-add-on-2.18.3-2.1.noarch yast2-metapackage-handler-0.8.10-0.1.1.noarch yast2-product-creator-2.18.11-2.2.noarch yast2-libyui-2.18.8-2.1.i586 yast2-theme-openSUSE-2.18.10-1.1.1.noarch yast2-nfs-common-2.18.1-2.2.noarch yast2-mouse-2.18.2-2.1.i586 yast2-printer-2.18.19-2.2.i586 yast2-nis-client-2.18.2-2.2.i586 yast2-registration-2.18.0-2.4.noarch yast2-online-update-frontend-2.18.5-2.2.noarch patterns-openSUSE-yast2_install_wf-11.3-1.1.1.i586 yast2-installation-2.18.33-1.1.2.noarch yast2-pam-2.18.1-0.1.1.noarch yast2-core-2.18.19-2.3.i586 yast2-theme-openSUSE-Oxygen-2.18.10-1.1.1.noarch yast2-transfer-2.18.0-3.1.i586 yast2-sysconfig-2.17.0-56.2.noarch yast2-ntp-client-2.18.0-3.2.noarch yast2-sound-2.18.4-1.1.2.1.i586 yast2-tv-2.18.4-2.8.noarch yast2-ldap-client-2.18.5-2.6.noarch yast2-bootloader-2.18.17-2.5.i586 patterns-openSUSE-kde4_yast-11.3-1.1.1.i586 yast2-control-center-2.18.12-1.1.1.i586 yast2-control-center-qt-2.18.12-1.1.1.i586 yast2-country-2.18.20-2.2.i586 yast2-restore-2.18.1-3.1.noarch yast2-mail-2.18.2-2.2.noarch patterns-openSUSE-yast2_basis-11.3-1.1.1.i586 yast2-add-on-creator-2.18.8-1.1.2.noarch yast2-packager-webpin-2.18.13-1.1.3.i586 yast2-qt-2.18.7-2.1.i586 yast2-trans-stats-2.15.0-122.2.noarch yast2-storage-2.18.19-2.3.i586 yast2-security-2.18.3-2.2.noarch yast2-qt-graph-2.18.4-4.1.i586 yast2-pkg-bindings-2.18.11-1.3.1.i586 But,I have a factory repository enabled.Could this be due to some Qt library issue? Will sending Yast logs for the period help you? Created attachment 366332 [details]
YaST log file
This contains log for the May 10 period when this problem happened.
The problem was in QT not in YaST. I found in log that there was problem with loading QT library used for UI in YaST. It is probably the result of previous update of QT library. Factory can includes the newest library for QT and it can happen that YaST is not build against the last QT library and it leads to troubles. It is not rule but it can happen. I am sorry for troubles. It seems that you have again working YaST and it means that troubles with QT library was solved. I appreciate your humility.But when one is using factory repo,breakages are expected.If using factory repo helps find bugs,I should like to do more. Thanks. |