GNOME Bugzilla – Bug 438550
crash in Open Folder:
Last modified: 2007-05-15 13:46:10 UTC
Version: 2.16.2 What were you doing when the application crashed? Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.20-1.2925.fc6 #1 SMP Sat Mar 10 19:15:16 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled Memory status: size: 121843712 vsize: 0 resident: 121843712 share: 0 rss: 21278720 rss_rlim: 0 CPU usage: start_time: 1179223127 rtime: 0 utime: 19 stime: 0 cutime:18 cstime: 0 timeout: 1 it_real_value: 0 frequency: 0 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 -1208177920 (LWP 3026)] (no debugging symbols found) 0x00cef402 in __kernel_vsyscall ()
+ Trace 134254
Thread 1 (Thread -1208177920 (LWP 3026))
----------- .xsession-errors --------------------- The overwriting error message was: File not found compiz: Failed to load slide: /home/stefano/Documents/Personale/Immagini/fedotra1.png winscard_clnt.c:320:SCardEstablishContextTH() Cannot open public shared file: /var/run/pcscd.pub Introspect error: The name edu.duke.linux.yum was not provided by any .service files Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. Debug: Loading Beagle.Util.Conf+IndexingConfig from indexing.xml compiz: pixmap 0xc00051 can't be bound to texture Debug: Loading Beagle.Util.Conf+DaemonConfig from daemon.xml Debug: Loading Beagle.Util.Conf+SearchingConfig from searching.xml ** (bug-buddy:2974): WARNING **: Impossibile caricare l'icona per Apri cartella Error: Indexing secure https:// URIs is not secure! ** (bug-buddy:3039): WARNING **: Impossibile caricare l'icona per Apri cartella --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find *** This bug has been marked as a duplicate of 363289 ***