After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 440659 - crash in Network Manager: Clicked 'Connect to othe...
crash in Network Manager: Clicked 'Connect to othe...
Status: RESOLVED DUPLICATE of bug 435036
Product: NetworkManager
Classification: Platform
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2007-05-23 10:25 UTC by bug-buddy
Modified: 2007-06-25 18:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description bug-buddy 2007-05-23 10:25:38 UTC 
What were you doing when the application crashed?
Clicked 'Connect to other Wireless Networks' in the NetworkManager menu


Distribution: Fedora release 6.93 (Rawhide)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3142.fc7 #1 SMP Mon May 7 21:07:42 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: Bluecurve

Memory status: size: 472031232 vsize: 472031232 resident: 15368192 share: 10739712 rss: 15368192 rss_rlim: 18446744073709551615
CPU usage: start_time: 1179612447 rtime: 76 utime: 49 stime: 27 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nm-applet'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
0x00000032dd60d82f in msgrcv () from /lib64/libpthread.so.0

+ Trace 135659

  • #0 msgrcv
    from /lib64/libpthread.so.0
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 g_free
    from /usr/lib64/libgnomeui-2.so.0
  • #5 <signal handler called>
  • #6 gtk_combo_box_get_model
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #7 ??
  • #8 ??
  • #9 wso_wpa_eap_new
  • #10 wsm_set_capabilities
  • #11 nma_other_network_dialog_run
  • #12 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #13 g_free
    from /lib64/libgobject-2.0.so.0
  • #14 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #15 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #16 g_free
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #17 ?? 


----------- .xsession-errors ---------------------
warning: Cannot initialize thread debugging library: unknown thread_db error '22'
warning: Cannot initialize thread debugging library: unknown thread_db error '22'
warning: Cannot initialize thread debugging library: unknown thread_db error '22'
warning: Cannot initialize thread debugging library: unknown thread_db error '22'
warning: Cannot initialize thread debugging library: unknown thread_db error '22'
warning: Cannot initialize thread debugging library: unknown thread_db error '22'
warning: Cannot initialize thread debugging library: unknown thread_db error '22'
warning: Cannot initialize thread debugging library: unknown thread_db error '22'
--------------------------------------------------
Comment 1 bug-buddy 2007-05-23 23:42:37 UTC 
let's see if this pops up again. I have done the following since the crash:
  - installed the debuginfo package to make the next trace more useful
  - cleaned out a lot of i386 packages which were installed alongside the x86_64 packages (I'm using FC devel and some dependency seems to have pulled em in)

If there is no update to this bug in a month, you can close as it has then not happened again.
Comment 2 Christopher Aillon 2007-06-04 19:38:47 UTC 
Out of curiosity are you using an Intel 3945 card with the iwlwifi driver?
Comment 3 bug-buddy 2007-06-25 18:16:19 UTC 
Yes it's a 3945 and IIRC Fdevel uses iwlwifi by default. (cant't be 100% sure as current rawhide kernels do not have it)
Comment 4 Christopher Aillon 2007-06-25 18:21:28 UTC 
Okay.  I think this was fixed by bug 435036.
Comment 5 Christopher Aillon 2007-06-25 18:21:51 UTC 

*** This bug has been marked as a duplicate of 435036 ***