GNOME Bugzilla – Bug 114044
breaks redhat9 network settings.
Last modified: 2004-12-22 21:47:04 UTC
After opening g-s-t's network-admin (but without applying anything), I get this error when trying to open the regular RH9 network tool (neat). This is with the latest 0.26.1 tarball: Component: redhat-config-network Version: 1.2.3 Summary: TB /var/tmp/redhat-config-network-1.2.3-root/usr/share/redhat-config-network/netconfpkg/NCDeviceFactory.py:43:getDeviceClass:KeyError: Loopback Traceback (most recent call last):
+ Trace 37331
window = mainDialog() File "/var/tmp/redhat-config-network-1.2.3-root/usr/share/redhat-config-network/netconfpkg/gui/maindialog.py", line 168, in __init__ File "/var/tmp/redhat-config-network-1.2.3-root/usr/share/redhat-config-network/netconfpkg/gui/maindialog.py", line 239, in load File "/var/tmp/redhat-config-network-1.2.3-root/usr/share/redhat-config-network/netconfpkg/gui/maindialog.py", line 246, in loadDevices File "/var/tmp/redhat-config-network-1.2.3-root/usr/share/redhat-config-network/netconfpkg/NCDeviceList.py", line 218, in getDeviceList File "/var/tmp/redhat-config-network-1.2.3-root/usr/share/redhat-config-network/netconfpkg/NCDeviceList.py", line 109, in load File "/var/tmp/redhat-config-network-1.2.3-root/usr/share/redhat-config-network/netconfpkg/NCDeviceFactory.py", line 43, in getDeviceClass
I've tried and repaired this twice, so I'm pretty sure. Note that I get this error every time I close any g-s-t tool: ** ERROR **: file vte.c: line 6850 (vte_terminal_process_incoming): assertion failed: (_vte_buffer_length(terminal->pvt->incoming) > 0)
hi! finally yesterday night I could hunt the bug (sorry for not doing it before, I still had some exams left after Gu4dec), the patch was almost one liner, this evening as soon as I arrive home I'll commit the bugfix to the CVS :-) just a side note, why the hell does redhat9 store the loopback configuration in a different directory to the rest of the interfaces?? :-/
Great. Could you post the ChangeLog entry here when you close this bug. I would be interested to know what the problem was. These config files are very mysterious. We really need to document how the various distros work. But you will hear more about that in the 2.4 announcement... Well done.
I've just commited this :-P the full Changelog entry is: 2003-06-25 Carlos Garnacho Parro <garnacho@tuxerver.net> * network-conf.in, network.pl.in, platform.pl.in, runlevel-conf.in,service.pl.in, time-conf.in, users-conf.in: s/redhat\-9\.0/redhat\-9/, because it's in this way in /etc/redhat-release, there won't appear the distro selection window anymore in redhat9 :-P * network.pl.in: (gst_network_ensure_loopback_interface): removed loobpack in redhat9, it isn't really neccesary (I'm even thinking about removing loopback support at all in GST) and broke the redhat network tool. Fixes #114044 (gst_network_rh72_get_file): made it to create the interface filename with the "dev" tag instead of the "name" tag (for RH >=7.2) So I think that the redhat9 support is now fully enabled :-P regarding to the vte error, I plan to use forkpty stuff again and run only the backend as root, so we'll get rid of this error :-P (that on the other hand, I've never experienced :-/)