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 517594 - crash in Network Manager:
crash in Network Manager:
Status: RESOLVED DUPLICATE of bug 399292
Product: NetworkManager
Classification: Platform
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2008-02-20 03:04 UTC by pascal.calarco
Modified: 2008-02-20 16:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description pascal.calarco 2008-02-20 03:04:44 UTC 
What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 145838080 vsize: 145838080 resident: 54657024 share: 52682752 rss: 54657024 rss_rlim: 4294967295
CPU usage: start_time: 1203476328 rtime: 22 utime: 18 stime: 4 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 -1208355104 (LWP 2898)]
(no debugging symbols found)
0x00ad7402 in __kernel_vsyscall ()

+ Trace 189815

Thread 1 (Thread -1208355104 (LWP 2898))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 ??
    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 ??
    from /lib/libdbus-1.so.3
  • #8 ??
    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 ??
    from /lib/libdbus-1.so.3
  • #13 ??
    from /lib/libdbus-1.so.3
  • #14 dbus_connection_dispatch
    from /lib/libdbus-1.so.3
  • #15 ??
    from /usr/lib/libdbus-glib-1.so.2
  • #16 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #17 ??
    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 (6 sec old) ---------------------
Nautilus-Share-Message: REFRESHING SHARES
Nautilus-Share-Message: ------------------------------------------
Nautilus-Share-Message: spawn arg "net"
Nautilus-Share-Message: spawn arg "usershare"
Nautilus-Share-Message: spawn arg "info"
Nautilus-Share-Message: end of spawn args; SPAWNING
Nautilus-Share-Message: returned from spawn: SUCCESS: 
Nautilus-Share-Message: exit code 255
Nautilus-Share-Message: ------------------------------------------
Nautilus-Share-Message: Called "net usershare info" but it failed: 'net usershare' returned error 255: net usershare: usershares are currently disabled
process 2898: 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 Dan Williams 2008-02-20 16:02:57 UTC 

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