GNOME Bugzilla – Bug 442829
crash in Computer:
Last modified: 2008-12-27 01:09:03 UTC
Version: 2.18.1 What were you doing when the application crashed? 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: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 39927808 vsize: 39927808 resident: 9703424 share: 7790592 rss: 9703424 rss_rlim: 4294967295 CPU usage: start_time: 1180685918 rtime: 9 utime: 7 stime: 2 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 -1208801568 (LWP 3862)] (no debugging symbols found) 0x009a8402 in __kernel_vsyscall ()
+ Trace 137181
Thread 1 (Thread -1208801568 (LWP 3862))
----------- .xsession-errors --------------------- deleting file /home/math/Desktop/test/gmp-4.2.1-35.i586.rpm deleting file /home/math/Desktop/test/gmp-devel-4.2.1-35.i586.rpm deleting file /home/math/Desktop/test/gsl-1.9-23.i586.rpm deleting file /home/math/Desktop/test/gsl-devel-1.9-23.i586.rpm flushing all words Finished indexing. Waiting for new events... File /home/math/nautilus-debug-log.txt has finished changing (trackerd:2953): Pango-WARNING **: pango_get_log_attrs: attrs_len should have been at least 114, but was 150. Expect corrupted memory. (trackerd:2953): Pango-WARNING **: pango_get_log_attrs: attrs_len should have been at least 114, but was 150. Expect corrupted memory. (trackerd:2953): Pango-WARNING **: pango_get_log_attrs: attrs_len should have been at least 667, but was 739. Expect corrupted memory. flushing all words Finished indexing. Waiting for new events... --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
*** Bug 442839 has been marked as a duplicate of this bug. ***
*** Bug 442872 has been marked as a duplicate of this bug. ***
*** Bug 443093 has been marked as a duplicate of this bug. ***
*** Bug 443855 has been marked as a duplicate of this bug. ***
*** Bug 444750 has been marked as a duplicate of this bug. ***
*** Bug 445562 has been marked as a duplicate of this bug. ***
This problem disappears as soon as Gnome 2.18.2 (FC7) is installed (I just updated to the current gnome version from the fc7 repository).
*** Bug 447401 has been marked as a duplicate of this bug. ***
*** Bug 452573 has been marked as a duplicate of this bug. ***
Sorry - I don't remember exactly what I was doing. It wasn't anything exotic - I was just poking around my files. However - the following may be relevant: Subsequently I found that Nautilus behaved very strangely. As I remember: * If you clicked on the 'Computer' item on the desktop, the list of 'device' names had %20 instead of space characters. * If you clicked on these, they did not open properly. * Help for Nautilus displayed pages of XML - not very useful. I used rpm to remove as many bits of Nautilus as I could conveniently (some bits wanted to remove lots of other packages). I then used rpm to put the bits back again. After that it seemed to work OK. My whole installation was originally FC6 and I updated it to F7 with a downloaded DVD image. I later had trouble with gnucash (see Bugzilla report 244431) I gathered from the feedback that after updating in the way I did, I should have run 'yum upgrade' - presumably to make sure all the old FC6 components were updated. I wonder if the Nautilus problem were due to a similar cause.
Re my previous message of 2007-06-30. I should have made it clearer that 'FC6' means Fedora Core 6 and 'F7' means Fedora 7. The Bugzilla report 244431 I mentioned was for the Fedora/Redhat Bugzilla system, not this gnome one. You can find that report at https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=244431
*** Bug 460972 has been marked as a duplicate of this bug. ***
*** Bug 460971 has been marked as a duplicate of this bug. ***
*** Bug 460970 has been marked as a duplicate of this bug. ***
*** Bug 460939 has been marked as a duplicate of this bug. ***
*** Bug 460981 has been marked as a duplicate of this bug. ***
*** Bug 460976 has been marked as a duplicate of this bug. ***
*** Bug 464149 has been marked as a duplicate of this bug. ***
*** Bug 468706 has been marked as a duplicate of this bug. ***
*** Bug 468702 has been marked as a duplicate of this bug. ***
*** Bug 467290 has been marked as a duplicate of this bug. ***
from bug 458054:
+ Trace 171556
*** Bug 451061 has been marked as a duplicate of this bug. ***
*** Bug 458054 has been marked as a duplicate of this bug. ***
*** Bug 469816 has been marked as a duplicate of this bug. ***
*** Bug 477384 has been marked as a duplicate of this bug. ***
*** Bug 479612 has been marked as a duplicate of this bug. ***
from bug 469816: (nautilus-file-management-properties:5562): Nautilus-Python-WARNING **: g_module_open libpython failed: libpython2.4.so: cannot open shared object file: No such file or directory Could not find platform independent libraries <prefix> Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>] 'import site' failed; use -v for traceback
*** Bug 491000 has been marked as a duplicate of this bug. ***
*** Bug 491001 has been marked as a duplicate of this bug. ***
*** Bug 506519 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 166672 ***
*** Bug 536501 has been marked as a duplicate of this bug. ***
*** Bug 536502 has been marked as a duplicate of this bug. ***
*** Bug 543364 has been marked as a duplicate of this bug. ***
*** Bug 565566 has been marked as a duplicate of this bug. ***