Bug 304822 - gtk_widget_size_allocate error in YAST modules
Summary: gtk_widget_size_allocate error in YAST modules
Status: RESOLVED FIXED
Alias: None
Product: openSUSE 10.3
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 2
Hardware: x86-64 openSUSE 10.3
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: Michael Meeks
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-27 12:57 UTC by Perret Florian
Modified: 2007-11-18 02:10 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
y2log (2.91 MB, text/plain)
2007-08-27 12:57 UTC, Perret Florian
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Perret Florian 2007-08-27 12:57:21 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.
Comment 1 Michal Zugec 2007-08-27 13:09:00 UTC
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
Comment 2 Perret Florian 2007-08-27 13:45:17 UTC
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...

Comment 3 Perret Florian 2007-08-28 06:47:47 UTC
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).
Comment 4 Perret Florian 2007-08-29 19:54:02 UTC
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.

Comment 5 Michael Meeks 2007-09-07 08:35:07 UTC
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.
Comment 6 Perret Florian 2007-09-07 09:10:10 UTC
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.
Comment 7 Boyd Timothy 2007-09-13 21:09:17 UTC
I'm not seeing this either in openSUSE 10.3 Beta 3.