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 475816 - crash in Network Manager: booting the system
crash in Network Manager: booting the system
Status: RESOLVED DUPLICATE of bug 444319
Product: NetworkManager
Classification: Platform
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2007-09-11 12:04 UTC by viswanaths
Modified: 2007-10-06 17:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description viswanaths 2007-09-11 12:04:51 UTC 
What were you doing when the application crashed?
booting the system


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

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: OSX

Memory status: size: 48369664 vsize: 48369664 resident: 10022912 share: 8454144 rss: 10022912 rss_rlim: 4294967295
CPU usage: start_time: 1189512240 rtime: 11 utime: 9 stime: 2 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 -1208314144 (LWP 3474)]
(no debugging symbols found)
0x00b31402 in __kernel_vsyscall ()

+ Trace 162050

Thread 1 (Thread -1208314144 (LWP 3474))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 g_free
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 g_free
    from /lib/libdbus-1.so.3
  • #8 g_free
    from /lib/libdbus-1.so.3
  • #9 dbus_message_new_method_call
    from /lib/libdbus-1.so.3
  • #10 nma_dbus_device_update_one_network
  • #11 ??
  • #12 g_free
    from /lib/libdbus-1.so.3
  • #13 g_free
    from /lib/libdbus-1.so.3
  • #14 dbus_connection_dispatch
    from /lib/libdbus-1.so.3
  • #15 g_free
    from /usr/lib/libdbus-glib-1.so.2
  • #16 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #17 g_free
    from /lib/libglib-2.0.so.0
  • #18 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #19 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (9 sec old) ---------------------
localuser:visu being added to access control list
SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/3329
process 3474: arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file dbus-message.c line 1074.
This is normally a bug in some application using the D-Bus library.
  D-Bus not built with -rdynamic so unable to print a backtrace
--------------------------------------------------
Comment 1 Susana 2007-10-06 17:23:54 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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