GNOME Bugzilla – Bug 358994
crash in Networking: setting up wired connect...
Last modified: 2007-02-21 17:18:13 UTC
Version: 2.15.5 What were you doing when the application crashed? setting up wired connection - it doesn't keep the gateway address Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.0 2006-09-04 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 32583680 vsize: 0 resident: 32583680 share: 0 rss: 11714560 rss_rlim: 0 CPU usage: start_time: 1159795521 rtime: 0 utime: 28 stime: 0 cutime:27 cstime: 0 timeout: 1 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 -1225083216 (LWP 4905)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 74062
Thread 1 (Thread -1225083216 (LWP 4905))
*** Bug 358995 has been marked as a duplicate of this bug. ***
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Since reporting the problem initially, I've reinstalled edgy and I've been unable to reproduce the crash of network-admin app. The one problem it is still having if using the GUI it doesn't retain the gateway address after specifying a static IP. I've been configuring it with command line for IP, route and DNS. It accepts the address but after clicking OK and opening it up again - it is not staying set as the field is cleared afterwards.
what version of system-tools-backend do you use? That issue is supposed to be fixed with 1.9.7. If you upgrade, did you reboot or restart dbus since? Could you try with the new version after a dbus restart?
The machine was rebooted plenty of times after the last upgrade. Where is the version of system-tools-backend listed?
dpkg -l system-tools-backend
*** This bug has been marked as a duplicate of 356180 ***
*** Bug 401300 has been marked as a duplicate of this bug. ***
*** Bug 384374 has been marked as a duplicate of this bug. ***