GNOME Bugzilla – Bug 371656
crash in Networking: I selected System -> Adm...
Last modified: 2007-12-26 02:37:29 UTC
Version: 2.15.5 What were you doing when the application crashed? I selected System -> Administration -> Networking. I have a VPN connection using the PPTP tools open to my employers network. This started happening after upgrading the following packages: Commit Log for Sat Nov 4 03:12:54 2006 Upgraded the following packages: libimlib2 (1.2.1-2ubuntu1) to 1.2.1-2ubuntu1.1 linux-restricted-modules-2.6.17-10-generic (2.6.17.5-11) to 2.6.17.6-1 linux-restricted-modules-common (2.6.17.5-11) to 2.6.17.6-1 Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 115699712 vsize: 115699712 resident: 13869056 share: 9261056 rss: 13869056 rss_rlim: -1 CPU usage: start_time: 1162838902 rtime: 52 utime: 49 stime: 3 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/network-admin' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 47727766494080 (LWP 16950)] (no debugging symbols found) 0x00002b687b09feb5 in waitpid () from /lib/libpthread.so.0
+ Trace 83700
Thread 1 (Thread 47727766494080 (LWP 16950))
Created attachment 76107 [details] gdb session of crash This attachment contains the output from running gdb after installing the debug version of glib2 and reproducing the crash. Crash does not occur if network-admin is run using sudo.
*** Bug 371657 has been marked as a duplicate of this bug. ***
PPTP VPN connection is not a factor. The crash occurs with the PPP connection turned off.
*** Bug 364457 has been marked as a duplicate of this bug. ***
*** Bug 373464 has been marked as a duplicate of this bug. ***
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!
Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 115916800 vsize: 115916800 resident: 14090240 share: 9244672 rss: 14090240 rss_rlim: -1 CPU usage: start_time: 1163684270 rtime: 54 utime: 51 stime: 3 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/network-admin' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 47498764598144 (LWP 5784)] 0x00002b3329765eb5 in waitpid () from /lib/libpthread.so.0
+ Trace 86934
Thread 1 (Thread 47498764598144 (LWP 5784))
*** Bug 379048 has been marked as a duplicate of this bug. ***
*** Bug 387350 has been marked as a duplicate of this bug. ***
*** Bug 389729 has been marked as a duplicate of this bug. ***
*** Bug 405721 has been marked as a duplicate of this bug. ***
Thanks for taking the time to report this bug. However, you are using a version that is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use. By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME. Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME.