Bugzilla – Bug 304822
gtk_widget_size_allocate error in YAST modules
Last modified: 2007-11-18 02:10:03 UTC
Created attachment 159969 [details] y2log When using different YAST modules errors like below appear : (gtk:4443): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with 0 and height -42 It's particullary annoyning for module like "network" which quits before saving the settings. So network cannot be config.
But I see here that configuration was written: 2007-08-27 11:30:59 <1> linux-g07h(6681) [YCP] NetworkDevices.ycp:640 Writing configuration 2007-08-27 11:30:59 <1> linux-g07h(6681) [YCP] NetworkDevices.ycp:646 OriginalDevs=$["eth":$["0":$["BOOTPROTO":"dhcp", "BROADCAST":"", "ETHTOOL_OPTIONS":"", "IPADDR":"", "MTU":"", "NAME":"ASUSTeK Ethernet controller", "NETMASK":"", "NETWORK":"", "REMOTE_IPADDR":"", "STARTMODE":"auto", "USERCONTROL":"no"], "1":$["BOOTPROTO":"dhcp", "BROADCAST":"", "ETHTOOL_OPTIONS":"", "IFPLUGD_PRIORITY":"10", "IPADDR":"", "MTU":"", "NAME":"", "NETMASK":"", "NETWORK":"", "REMOTE_IPADDR":"", "STARTMODE":"auto", "USERCONTROL":"yes", "WIRELESS_AP":"", "WIRELESS_AUTH_MODE":"open", "WIRELESS_BITRATE":"auto", "WIRELESS_CA_CERT":"", "WIRELESS_CHANNEL":"", "WIRELESS_CLIENT_CERT":"", "WIRELESS_CLIENT_KEY":"", "WIRELESS_CLIENT_KEY_PASSWORD":"", "WIRELESS_DEFAULT_KEY":"0", "WIRELESS_EAP_AUTH":"", "WIRELESS_EAP_MODE":"", "WIRELESS_ESSID":"", "WIRELESS_FREQUENCY":"", "WIRELESS_KEY":"", "WIRELESS_KEY_0":"", "WIRELESS_KEY_1":"", "WIRELESS_KEY_2":"", "WIRELESS_KEY_3":"", "WIRELESS_KEY_LENGTH":"128", "WIRELESS_MODE":"Managed", "WIRELESS_NICK":"", "WIRELESS_NWID":"", "WIRELESS_PEAP_VERSION":"", "WIRELESS_POWER":"yes", "WIRELESS_WPA_ANONID":"", "WIRELESS_WPA_IDENTITY":"", "WIRELESS_WPA_PASSWORD":"", "WIRELESS_WPA_PSK":""]]] 2007-08-27 11:30:59 <1> linux-g07h(6681) [YCP] NetworkDevices.ycp:647 Devs=$["eth":$["0":$["BOOTPROTO":"dhcp", "BROADCAST":"", "ETHTOOL_OPTIONS":"", "IPADDR":"", "MTU":"", "NAME":"ASUSTeK Ethernet controller", "NETMASK":"", "NETWORK":"", "REMOTE_IPADDR":"", "STARTMODE":"auto", "USERCONTROL":"no"], "1":$["BOOTPROTO":"static", "BROADCAST":"", "ETHTOOL_OPTIONS":"", "IPADDR":"192.168.0.101", "MTU":"", "NAME":"", "NETMASK":"255.255.255.0", "NETWORK":"", "REMOTE_IPADDR":"", "STARTMODE":"auto", "USERCONTROL":"yes", "WIRELESS_AP":"", "WIRELESS_AUTH_MODE":"open", "WIRELESS_BITRATE":"auto", "WIRELESS_CA_CERT":"", "WIRELESS_CHANNEL":"", "WIRELESS_CLIENT_CERT":"", "WIRELESS_CLIENT_KEY":"", "WIRELESS_CLIENT_KEY_PASSWORD":"", "WIRELESS_DEFAULT_KEY":"0", "WIRELESS_EAP_AUTH":"", "WIRELESS_EAP_MODE":"", "WIRELESS_ESSID":"", "WIRELESS_FREQUENCY":"", "WIRELESS_KEY":"", "WIRELESS_KEY_0":"", "WIRELESS_KEY_1":"", "WIRELESS_KEY_2":"", "WIRELESS_KEY_3":"", "WIRELESS_KEY_LENGTH":"128", "WIRELESS_MODE":"Managed", "WIRELESS_NICK":"", "WIRELESS_NWID":"", "WIRELESS_PEAP_VERSION":"", "WIRELESS_POWER":"yes", "WIRELESS_WPA_ANONID":"", "WIRELESS_WPA_IDENTITY":"", "WIRELESS_WPA_PASSWORD":"", "WIRELESS_WPA_PSK":"", "_aliases":$[]]]] 2007-08-27 11:30:59 <1> linux-g07h(6681) [YCP] NetworkDevices.ycp:656 Deleted=[] 2007-08-27 11:30:59 <1> linux-g07h(6681) [YCP] NetworkConfig.ycp:160 Writing configuration
I've got two network cards : one LAN and one WIFI. "ASUSTeK Ethernet controller" is the LAN one. I can't see the wifi in this log and it's this card I try to config. For example : by default firewall blocks all with the wifi card, if I put this option on "external zone" and quit. If I restart YAST-network just after, firewall is again on block all...
Finally you're right. With new fFctory's YAST modules, some network settings are saved. But the "Firewall zone" setting can't be changed. And my wifi card doesn't appear in the network applet (gnome).
It's the same problem with KDE, card is in YAST2-network (in which I can't change the "firewall zone" settings) but not in Knetworkmanager.
Perret - that is a console warning; not a failure. If you remove the yast2-gtk package - can you configure your settings ? if not, this is a core network tool bug.
Don't have anymore error message with beta 3. But I've got another problem with NM crash : Bug 307910 I think we can now close this bug.
I'm not seeing this either in openSUSE 10.3 Beta 3.