GNOME Bugzilla – Bug 512729
crash in Home Folder:
Last modified: 2008-01-29 09:27:43 UTC
What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 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: 122593280 vsize: 122593280 resident: 25960448 share: 17870848 rss: 25960448 rss_rlim: 4294967295 CPU usage: start_time: 1201582773 rtime: 3105 utime: 2708 stime: 397 cutime:0 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (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 -1208211744 (LWP 2678)] [New Thread -1270879344 (LWP 5070)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 187160
Thread 2 (Thread -1270879344 (LWP 5070))
----------- .xsession-errors (11 sec old) --------------------- JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] CalDAV Eplugin starting up ... ** (evolution:4191): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:4191): DEBUG: mailto URL program: evolution libnm_glib_nm_state_cb: dbus returned an error. (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] (nautilus:2678): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x45d6e)! --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 454799 ***