What were you doing when the application crashed?
I had accidentally removed the network manager icon from the panel at the top of the screen. When I tried to put back the icon, I couldn't figure out how to do it and tried some "remedies" I found on the internet. Since, I'm new at Linux, I obviously did something wrong and crashed 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: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 44904448 vsize: 44904448 resident: 15593472 share: 11628544 rss: 15593472 rss_rlim: 4294967295
CPU usage: start_time: 1188088253 rtime: 84 utime: 74 stime: 10 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 -1208944928 (LWP 3671)]
(no debugging symbols found)
0x00882402 in __kernel_vsyscall ()

+ Trace 157921

----------- .xsession-errors (139 sec old) ---------------------
    follow_name_owner_changes=follow_name_owner_changes)
  File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 230, in __init__
    _dbus_bindings.UInt32(0))
  File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 169, in __call__
    reply_message = self._connection.send_message_with_reply_and_block(message, timeout)
dbus.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name edu.duke.linux.yum was not provided by any .service files
** Message: <info>  You are now connected to the wireless network 'Tortoise'.
FATAL: Module md not found.
Probing for video card:   Intel Corporation 82865G Integrated Graphics Controller
Starting graphical installation...
Loading /lib/kbd/keymaps/i386/qwerty/us.map.gz
process 3671: 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
--------------------------------------------------