GNOME Bugzilla – Bug 377970
crash in Networking: Just open it!!!
Last modified: 2006-11-22 04:06:24 UTC
Version: 2.15.5 What were you doing when the application crashed? Just open it!!! Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 34033664 vsize: 0 resident: 34033664 share: 0 rss: 12447744 rss_rlim: 0 CPU usage: start_time: 1164126145 rtime: 0 utime: 41 stime: 0 cutime:38 cstime: 0 timeout: 3 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/network-admin' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1225767248 (LWP 5207)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 88390
Thread 1 (Thread -1225767248 (LWP 5207))
What happened prior: Yesterday I installed Samba, as per the instructions here: http://www.howtoforge.com/samba_setup_ubuntu_5.10 I did this without being connected to the network. Then I stopped the samba and winsd services because I don't want those interfering with my company network the next day at work. After that I plugged in the ethernet cable to my new ADSL router. I then wanted to switch to using DHCP which is when I first discovered the problem. The Networking window doesn't even come up, the Bug Buddy comes up right away. I then rebooted into Windows and verified that everything worked as usual hardware wise; was able to connect to and configure the ADSL router. THen unplugged the cable, but still I'm not able to open 'Networking'. Also the next day at the office, being connected to the network as usual, the Networking window crashes instantly. Chanchao / Chiang Mai / Thailand
WORKAROUND / (SOLUTION?) FOUND: Tracing back the things I did in the Samba install, I found what's causing Networking to crash. I updated my /etc/host file like this: ----- 127.0.0.1 localhost chan-laptop 127.0.1.1 chan-laptop 172.16.10.15 exchange 192.168.1.50 uan 192.168.1.51 fdg-server 192.168.1.52 demo # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts --------- I was testing the Samba PDC configuration for use on my home network which uses the 192.16.1.* range. My netowrk however was still set up for the company network that uses 172.16.10.* I entered some of the computer IP's I have at home, those are the 3 in the second group above. I guess Gnome 'Network' really doesn't like that. :) When I remove those entries it comes up as normal. NOTE: When I leave those 192.168.1.* hosts in there then Gnome network-admin DOES come up when run from the terminal as root. Are you guys all slapping yourselves on the forehead about my stupidity of entering hosts that are on a different network, or would I normally be allowed to define hosts that aren't always on the same network as I am? This is a laptop afterall. Cheers, Chanchao
*** Bug 377971 has been marked as a duplicate of this bug. ***
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 356180 *** *** This bug has been marked as a duplicate of 356180 ***