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 433675 - crash in Network Manager:
crash in Network Manager:
Status: RESOLVED DUPLICATE of bug 436553
Product: NetworkManager
Classification: Platform
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Dan Williams
Dan Williams
: 437779 437975 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-04-26 19:09 UTC by Thilo
Modified: 2007-11-15 22:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Thilo 2007-04-26 19:09:58 UTC 
What were you doing when the application crashed?



Distribution: Unknown
Gnome Release: 2.18.0 2007-03-12 (Foresight Linux)
BugBuddy Version: 2.18.0

System: Linux 2.6.20.4-1.smp.gcc3.4.x86.i686 #1 SMP Sat Mar 24 16:24:13 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Foresight
Icon Theme: Tango

Memory status: size: 33058816 vsize: 33058816 resident: 6070272 share: 3964928 rss: 6070272 rss_rlim: 4294967295
CPU usage: start_time: 1177573558 rtime: 710 utime: 476 stime: 234 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)
[Thread debugging using libthread_db enabled]
[New Thread -1226295616 (LWP 3112)]
(no debugging symbols found)
0xb7f6f410 in ?? ()

+ Trace 130751

  • #0 ??
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #5 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #6 <signal handler called>
  • #7 dbus_g_method_return_error
    from /usr/lib/libdbus-glib-1.so.2
  • #8 g_slist_find_custom
    from /usr/lib/libglib-2.0.so.0
  • #9 dbus_g_proxy_get_type
    from /usr/lib/libdbus-glib-1.so.2
  • #10 dbus_connection_dispatch
    from /usr/lib/libdbus-1.so.3
  • #11 dbus_g_message_get_message
    from /usr/lib/libdbus-glib-1.so.2
  • #12 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #13 g_main_context_acquire
    from /usr/lib/libglib-2.0.so.0
  • #14 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #15 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 main 

Thread 1 (Thread -1226295616 (LWP 3112)):
#-1 0xb7f6f410 in ?? ()
No symbol table info available.
#-1 0xb7f6f410 in ?? ()


----------- .xsession-errors ---------------------
GTK Accessibility Module initialized
Bonobo accessibility support initialized
Bonobo accessibility support initialized
GTK Accessibility Module initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
Bonobo accessibility support initialized
Backtrace limit of 200 exceeded
/usr/share/bug-buddy/gdb-cmd:3: Error in sourced command file:
Backtrace limit of 200 exceeded
Backtrace limit of 200 exceeded
Backtrace limit of 200 exceeded
/usr/share/bug-buddy/gdb-cmd:3: Error in sourced command file:
Backtrace limit of 200 exceeded
Backtrace limit of 200 exceeded
--------------------------------------------------
Comment 1 Susana 2007-05-12 12:33:49 UTC 
*** Bug 437779 has been marked as a duplicate of this bug. ***
Comment 2 tama 2007-06-04 15:38:39 UTC 
Hi, looking into the stack trace (call #7) I'd say this bug belong to dbus in http://bugzilla.freedesktop.org/
There are also a number of bugs that are likely to be duplicates of this one: http://bugzilla.gnome.org/dupfinder/simple-dup-finder.cgi?id=433675&comment_id=0&limit=10
I don't know though if bugs in different products and versions can be called duplicates just by looking into the stack trace. Anyway, it seems dbus is the cause of them all.
Comment 3 Susana 2007-10-06 17:36:42 UTC 
*** Bug 437975 has been marked as a duplicate of this bug. ***
Comment 4 Dan Williams 2007-11-15 22:27:27 UTC 

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