Bug 468045 – crash in Network Manager: nothing special was happ...

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 468045 - crash in Network Manager: nothing special was happ...


Summary:	crash in Network Manager: nothing special was happ...


Status:	RESOLVED DUPLICATE of bug 444319

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-08-18 21:14 UTC by ztt
Modified:	2007-08-24 18:44 UTC

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

Description ztt 2007-08-18 21:14:33 UTC

What were you doing when the application crashed?
nothing special was happening. th epc was very much idle.	


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

System: Linux 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 56360960 vsize: 56360960 resident: 27885568 share: 23007232 rss: 27885568 rss_rlim: 4294967295
CPU usage: start_time: 1187460353 rtime: 1613 utime: 1503 stime: 110 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 -1208494368 (LWP 2515)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 156217

Thread 1 (Thread -1208494368 (LWP 2515))

#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 (21 sec old) ---------------------
eth1      Interface doesn't support scanning.
eth1: error fetching interface information: Device not found
eth1      No such device
eth1      Interface doesn't support scanning.
eth1: error fetching interface information: Device not found
eth1      No such device
/usr/lib/python2.5/site-packages/pirut/Progress.py:162: GtkWarning: gtk_progress_set_percentage: assertion `percentage >= 0 && percentage <= 1.0' failed
  self.pbar.set_fraction(fract)
process 2515: 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-08-24 18:44:57 UTC


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