GNOME Bugzilla – Bug 373581
crash in Networking: Attempting to configure ...
Last modified: 2007-12-26 02:37:12 UTC
Version: 2.15.5 What were you doing when the application crashed? Attempting to configure a wireless network connection. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 13254656 vsize: 0 resident: 37707776 share: 0 rss: 37707776 rss_rlim: 0 CPU usage: start_time: 159 rtime: 0 utime: 1163092260 stime: 0 cutime:156 cstime: 0 timeout: 142 it_real_value: 0 frequency: 14 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 805543248 (LWP 4134)] (no debugging symbols found) 0x0eb43334 in __waitpid_nocancel () from /lib/libpthread.so.0
+ Trace 85197
Thread 1 (Thread 805543248 (LWP 4134))
*** Bug 373583 has been marked as a duplicate of this bug. ***
*** Bug 373582 has been marked as a duplicate of this bug. ***
Pango?
*** Bug 373599 has been marked as a duplicate of this bug. ***
*** Bug 379935 has been marked as a duplicate of this bug. ***
Apparently what's happening is that two size request signals are being run from two threads, and trying to size the same label, they hit a re-entrancy problem in PangoLayout. PangoLayout is not thread-safe, and will not be. So, someone else should be fixed here.
I have some more info on 379935 (filed as a duplicate of 373581). If I start network-admin with "sudo network-admin", it opens up just fine. If I start it from the gnome menu, it crashes.
*** Bug 383411 has been marked as a duplicate of this bug. ***
*** Bug 388440 has been marked as a duplicate of this bug. ***
*** Bug 390752 has been marked as a duplicate of this bug. ***
*** Bug 407802 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.