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 505429 - crash in Network Manager: trying to connect to 'ot...
crash in Network Manager: trying to connect to 'ot...
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-12-24 14:05 UTC by leos.za
Modified: 2007-12-26 10:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description leos.za 2007-12-24 14:05:59 UTC 
What were you doing when the application crashed?
trying to connect to 'other wireless networks', just clicked on the button	


Distribution: Gentoo Base System release 1.12.10
Gnome Release: 2.18.1 2007-05-04 (Gentoo)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-sabayon #1 SMP Wed Aug 1 22:48:31 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Human-Graphite
Icon Theme: Tango

Memory status: size: 409985024 vsize: 409985024 resident: 80646144 share: 69206016 rss: 80646144 rss_rlim: 18446744073709551615
CPU usage: start_time: 1198498984 rtime: 490 utime: 443 stime: 47 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 "/lib/libthread_db.so.1".
(no debugging symbols found)
0x00002af564b20b0f in waitpid () from /lib/libpthread.so.0

+ Trace 182923

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 ??
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 gtk_combo_box_set_model
    from /usr/lib/libgtk-x11-2.0.so.0
  • #4 wso_wpa_eap_new
  • #5 wsm_set_capabilities
  • #6 nma_other_network_dialog_run
  • #7 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #8 ??
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #11 gtk_widget_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 gtk_menu_shell_activate_item
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #16 ??
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #19 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #23 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #24 ??
    from /usr/lib/libglib-2.0.so.0
  • #25 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #26 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 main 


----------- .xsession-errors ---------------------
(gnome-panel:9329): Wnck-WARNING **: Unhandled action type (nil)
(gnome-panel:9329): Wnck-WARNING **: Unhandled action type (nil)
(emerald:9487): Wnck-WARNING **: Unhandled action type (nil)
(emerald:9487): Wnck-WARNING **: Unhandled action type (nil)
(gnome-panel:9329): Wnck-WARNING **: Unhandled action type (nil)
(gnome-panel:9329): Wnck-WARNING **: Unhandled action type (nil)
(emerald:9487): Wnck-WARNING **: Unhandled action type (nil)
(emerald:9487): Wnck-WARNING **: Unhandled action type (nil)
--------------------------------------------------
Comment 1 Teppo Turtiainen 2007-12-26 10:30:10 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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