GNOME Bugzilla – Bug 515614
crash in Open Folder: I was tryiing to open th...
Last modified: 2008-02-10 21:28:08 UTC
Version: 2.18.3 What were you doing when the application crashed? I was tryiing to open the vodafone-connect-card-linux application 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.14-64.fc7 #1 SMP Sun Jan 20 23:54:08 EST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 80879616 vsize: 80879616 resident: 22364160 share: 18862080 rss: 22364160 rss_rlim: 4294967295 CPU usage: start_time: 1202669847 rtime: 19 utime: 18 stime: 1 cutime:0 cstime: 0 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 -1208826144 (LWP 3665)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 188748
Thread 1 (Thread -1208826144 (LWP 3665))
----------- .xsession-errors --------------------- localuser:root being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/3539 ** (nautilus:3665): WARNING **: /usr/lib/libgstbase-0.10.so.0: invalid ELF header Initializing nautilus-open-terminal extension ** (gnome-panel:3664): WARNING **: panel-applet-frame.c:1283: failed to load applet OAFIID:GNOME_MixerApplet: Failed to resolve, or extend '!prefs_key=/apps/panel/applets/mixer/prefs;background=none:;orient=down;size=x-small;locked_down=false (nautilus:3665): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. --------------------------------------------------
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 439977 ***