Bug 449761 – crash in Network Manager: Pidigin was running. A c...

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 449761 - crash in Network Manager: Pidigin was running. A c...


Summary:	crash in Network Manager: Pidigin was running. A c...


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-06-21 11:29 UTC by mcl
Modified:	2007-06-23 02:32 UTC

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

Description mcl 2007-06-21 11:29:51 UTC

What were you doing when the application crashed?
Pidigin was running. A connection was established with a Netgear AP.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (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: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 64442368 vsize: 64442368 resident: 25612288 share: 20783104 rss: 25612288 rss_rlim: 4294967295
CPU usage: start_time: 1182421464 rtime: 326 utime: 303 stime: 23 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 -1208699168 (LWP 3601)]
(no debugging symbols found)
0x00667402 in __kernel_vsyscall ()

+ Trace 142651

Thread 1 (Thread -1208699168 (LWP 3601))

#0 __kernel_vsyscall
#1 waitpid
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:3601): 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:3601): 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)
** Message: <info>  You are now connected to the wireless network 'suckfizzle'.
process 3601: 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 Christopher Aillon 2007-06-23 02:32:28 UTC


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