GNOME Bugzilla – Bug 328235
nautilus-2.13.4 crashes when opening a desktop sub-folder that contains a jpeg
Last modified: 2006-01-24 17:37:49 UTC
nautilus-2.13.4 crashes when opening a desktop sub-folder that contains a jpeg. [GARNOME-2.13.5] Experiment #1 ---------------- * open Home folder on desktop * open subfolder containing jpeg - see "clock" icon - wait for thumbnail image - boom Experiment #2 ------------- * open Home folder on desktop * drag subfolder containing jpeg to desktop * open that folder - all is well Below is a backtrace, for what it's worth, from Experiment #1 -Joseph ===================================================================== Backtrace was generated from '/usr/local/src/GNOME/2.13/garnome-2.13.x/libexec/<unknown>' Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 807804928 (LWP 6058)] [New Thread 810296544 (LWP 6067)] [Thread debugging using libthread_db enabled] [New Thread 807804928 (LWP 6058)] [New Thread 810296544 (LWP 6067)] [Thread debugging using libthread_db enabled] [New Thread 807804928 (LWP 6058)] [New Thread 810296544 (LWP 6067)] [New Thread 810165472 (LWP 6060)] 0x301cb158 in ___newselect_nocancel () from /lib/tls/libc.so.6
+ Trace 65504
Thread 3 (Thread 810165472 (LWP 6060))
Thanks for the bug report. perhaps a duplicate of Bug 327323 ? anyways the stack trace looks incomplete Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Christian, This bug does appear to be a duplicate of 327323. A problem associated with working on a large body of code like GARNOME is the complexity of the package dependencies. One often bows to expediency and engages in the dangerous practice of uninstalling an old version of a single package and installing a new version of that package rather than rebuilding the entire suite. Sometimes you get away with it, other times not. Since I reported this bug, I have updated libgtop, gnome-volume-manager, and gcalctool as well as the mono suite. As far as I can tell, none of these should directly effect nautilus, although the GARNOME mono suite will rebuild dbus and gmime, which was updated a few days earlier. So what has happened??? The problem has "gone away"... It would be prudent to rebuild GARNOME completely to see if the problem resurfaces. That process takes a couple of days on my system. I will probably wait until the weekend since I am expecting more package updates to appear in the next few days. I will report back after a clean rebuild. -Joseph
reopen if this happens again and does not appear to be a duplicate *** This bug has been marked as a duplicate of 327323 ***