Bug 436554 – crash in Network Manager: Trying to start NetworkM...

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 436554 - crash in Network Manager: Trying to start NetworkM...


Summary:	crash in Network Manager: Trying to start NetworkM...


Status:	RESOLVED DUPLICATE of bug 436553

Product:	NetworkManager
Classification:	Platform
Component:	general
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Dan Williams
QA Contact:	Dan Williams

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-05-07 10:42 UTC by mcl
Modified:	2007-05-08 19:41 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description mcl 2007-05-07 10:42:52 UTC

What were you doing when the application crashed?
Trying to start NetworkManager manually.


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.3116.fc7 #1 SMP Thu Apr 26 10:36:44 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10299905
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 72552448 vsize: 72552448 resident: 13570048 share: 10723328 rss: 13570048 rss_rlim: 4294967295
CPU usage: start_time: 1178455937 rtime: 30 utime: 21 stime: 9 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 -1208449312 (LWP 4226)]
(no debugging symbols found)
0x00a85402 in __kernel_vsyscall ()

+ Trace 132854

Thread 1 (Thread -1208449312 (LWP 4226))

#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 ---------------------
** (nm-applet:4226): WARNING **: <WARN>  nma_dbus_update_devices_cb(): dbus returned an error.
  (org.freedesktop.DBus.Error.NoReply) Message did not receive a reply (timeout by message bus)
** (nm-applet:4226): WARNING **: <WARN>  nma_dbus_nm_state_cb(): dbus returned an error.
  (org.freedesktop.DBus.Error.NoReply) Message did not receive a reply (timeout by message bus)
process 4226: 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-05-08 19:41:45 UTC


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