GNOME Bugzilla – Bug 449076
crash in Network Manager: I was reading a blog in ...
Last modified: 2007-06-21 06:03:40 UTC
What were you doing when the application crashed? I was reading a blog in Thunderbird, at the time the crash came, Rhythmbox was changing the mp3 that was being played. 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: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 43479040 vsize: 43479040 resident: 24150016 share: 21528576 rss: 24150016 rss_rlim: 4294967295 CPU usage: start_time: 1182249810 rtime: 19 utime: 16 stime: 3 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 -1208469792 (LWP 2931)] (no debugging symbols found) 0x00e4d402 in __kernel_vsyscall ()
+ Trace 142110
Thread 1 (Thread -1208469792 (LWP 2931))
----------- .xsession-errors --------------------- localuser:alan being added to access control list SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2781 error getting update info: Cannot open/read repomd.xml file for repository: fedora ** Message: <info> You are now connected to the wired network. ** Message: <info> You are now connected to the wireless network 'al'. process 2931: 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 --------------------------------------------------
I didn't mention in the original report that I may have been scrolling with the touch pad at the time of the crash also.
*** This bug has been marked as a duplicate of 444842 ***