GNOME Bugzilla – Bug 397478
crash in Networking: Just started it. Could b...
Last modified: 2007-01-18 23:57:30 UTC
Version: 2.15.5 What were you doing when the application crashed? Just started it. Could be that I was doing a Traceroute using Network Tools at the time? Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 33878016 vsize: 0 resident: 33878016 share: 0 rss: 11595776 rss_rlim: 0 CPU usage: start_time: 1169003267 rtime: 0 utime: 24 stime: 0 cutime:23 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 -1225988432 (LWP 9650)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 102849
Thread 1 (Thread -1225988432 (LWP 9650))
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Will do. Also remembered that network-admin started crashing every time I tried to run it just after I had assigned my configuration with it's own location. Will add the debugging symbols now and reproduce. BTW: Is there a good spot for a newbie to get started bug-fixing (I've got programming experience on MS C++, Java, PHP etc., but not gnome/linux).
Created attachment 80657 [details] Stacktrace of network-admin crash on startup including debugging symbols Had to build the package according to http://wiki.debian.org/HowToGetABacktrace as the -dbgsym packages at 'deb http://people.ubuntu.com/~pitti/ddebs edgy main universe' were out of date (ubuntu 2.15.5 ubuntu3 intstead of ubuntu4).
In case this tells you anything more, here's running network-admin through gdb: (gdb) run Starting program: /usr/bin/network-admin [Thread debugging using libthread_db enabled] [New Thread -1225398608 (LWP 31279)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1225398608 (LWP 31279)] IA__g_object_newv (object_type=135752048, n_parameters=1, parameters=0x829ed18) at gobject.c:856 856 gobject.c: No such file or directory. in gobject.c (gdb)
*** This bug has been marked as a duplicate of 360435 ***
Note: using the Simple Dup Finder with the new stack trace (attached), this was thought to be a dup of 359781, which is itself a dup of 359622, which is a dup of 360435, hence resolving this as a dup of 360435. Added note there about the stack trace with debug symbols.