Bugzilla – Bug 602531
Network settings does not start
Last modified: 2010-05-06 18:54:23 UTC
Created attachment 359234 [details] network configure User-Agent: Mozilla/5.0 (X11; U; Linux i686; ro; rv:1.9.2.4) Gecko/20100417 SUSE/3.6.4-1.1 Firefox/3.6.4 When accessing Network Settings via Yast nothing happens. Reproducible: Always Steps to Reproduce: 1.Start Yast 2.Click on network devices 3.Click on network settings Actual Results: nothing happens Expected Results: should open a window to configure network
Oprea, this problem was reported in bug #600576 and should be fixed in yast2-network-2.19.25. Can you please confirm that you have this version installed and, if not, install it from Factory and retest? Thanks.
I got the same result on a 64 bit system. I updated the rpm but still got the same result. # rpm -ivhU yast2-network-2.19.25-82.1.x86_64.rpm warning: yast2-network-2.19.25-82.1.x86_64.rpm: Header V3 DSA/SHA1 Signature, key ID 61e7d06c: NOKEY Preparing... ########################################### [100%] 1:yast2-network ########################################### [100%] My rpm listing for yast is # rpm -qa | grep -i yast2 | sort autoyast2-installation-2.19.5-1.7.noarch patterns-openSUSE-yast2_basis-11.3-11.5.x86_64 patterns-openSUSE-yast2_install_wf-11.3-11.5.x86_64 yast2-2.19.13-1.1.x86_64 yast2-add-on-2.18.3-4.2.noarch yast2-apparmor-2.19.0-2.2.noarch yast2-backup-2.19.0-2.2.noarch yast2-bootloader-2.19.12-1.2.x86_64 yast2-branding-openSUSE-2.18.0-4.2.noarch yast2-control-center-2.19.1-2.4.x86_64 yast2-control-center-qt-2.19.1-2.4.x86_64 yast2-core-2.19.2-2.13.x86_64 yast2-country-2.19.13-2.1.x86_64 yast2-country-data-2.19.13-2.1.x86_64 yast2-dbus-client-2.18.0-4.4.x86_64 yast2-firewall-2.19.0-2.3.noarch yast2-hardware-detection-2.17.1-4.14.x86_64 yast2-http-server-2.19.0-2.9.noarch yast2-inetd-2.17.3-5.3.noarch yast2-installation-2.19.6-1.2.noarch yast2-irda-2.19.1-2.3.noarch yast2-iscsi-client-2.19.4-1.1.noarch yast2-kerberos-client-2.19.0-2.2.noarch yast2-ldap-2.17.3-11.4.x86_64 yast2-ldap-client-2.19.1-1.2.noarch yast2-libyui-2.19.0-2.5.x86_64 yast2-mail-2.18.5-1.1.noarch yast2-metapackage-handler-0.8.10-2.3.noarch yast2-mouse-2.18.2-4.2.x86_64 yast2-ncurses-2.19.4-1.1.x86_64 yast2-ncurses-pkg-2.19.0-2.5.x86_64 yast2-network-2.19.25-82.1.x86_64 yast2-nfs-client-2.19.2-1.2.noarch yast2-nfs-common-2.18.1-4.2.noarch yast2-nis-client-2.18.2-4.6.x86_64 yast2-ntp-client-2.18.1-2.1.noarch yast2-online-update-2.19.2-2.2.noarch yast2-online-update-frontend-2.19.2-2.2.noarch yast2-packager-2.19.6-1.2.x86_64 yast2-packager-webpin-2.19.6-1.2.x86_64 yast2-pam-2.19.1-2.2.noarch yast2-perl-bindings-2.19.1-2.4.x86_64 yast2-pkg-bindings-2.19.1-1.2.x86_64 yast2-printer-2.19.9-1.1.x86_64 yast2-qt-2.19.1-1.2.x86_64 yast2-qt-graph-2.19.0-1.5.x86_64 yast2-qt-pkg-2.19.2-1.1.x86_64 yast2-registration-2.18.3-3.2.noarch yast2-registration-branding-openSUSE-2.18.3-3.2.noarch yast2-repair-2.18.3-3.10.noarch yast2-restore-2.19.0-2.2.noarch yast2-runlevel-2.19.0-2.2.noarch yast2-samba-client-2.19.5-1.5.noarch yast2-samba-server-2.18.3-2.2.noarch yast2-scanner-2.19.2-1.3.x86_64 yast2-security-2.19.1-2.2.noarch yast2-slp-2.16.0-85.4.x86_64 yast2-sound-2.19.1-2.4.x86_64 yast2-storage-2.19.12-1.2.x86_64 yast2-sudo-2.18.2-4.2.noarch yast2-sysconfig-2.17.0-58.2.noarch yast2-theme-openSUSE-2.19.0-2.2.noarch yast2-theme-openSUSE-Oxygen-2.19.0-2.2.noarch yast2-trans-en_US-2.19.0-6.1.noarch yast2-trans-stats-2.19.0-1.3.noarch yast2-transfer-2.18.0-5.5.x86_64 yast2-tune-2.18.1-4.2.x86_64 yast2-tv-2.19.3-1.14.noarch yast2-update-2.19.1-1.1.x86_64 yast2-users-2.19.13-1.2.x86_64 yast2-vm-2.16.10-5.3.x86_64 yast2-x11-2.18.0-4.2.noarch yast2-xml-2.16.1-58.5.x86_64 yast2-ycp-ui-bindings-2.18.5-4.5.x86_64
Glenn, you're right. The fixed version hasn't reached Factory yet. It's available in OBS' YaST development project: http://download.opensuse.org/repositories/YaST:/Head/openSUSE_Factory/
I've tested it here and I'm now confident this is a duplicate of bug #600576. You can wait for the fix to reach Factory or use the packages from the URL in comment #3. And thanks for taking the time to report the problem! *** This bug has been marked as a duplicate of bug 600576 ***
After update to yast2-network-2.19.25 is ok now, Thanks!