GNOME Bugzilla – Bug 318620
Nautilus craches in folders with jpg images
Last modified: 2005-12-10 17:53:26 UTC
From: Jon Gunnar Rue <jonrue@start.no> To: submit@bugs.gnome.org X-Mailer: bug-buddy 2.12.1 Subject: Nautilus craches in folders with jpg images Distribution: Ubuntu 5.10 (breezy) Package: nautilus Severity: Normal Version: GNOME2.12.1 2.12.1 Gnome-Distributor: Ubuntu Synopsis: Nautilus craches in folders with jpg images Bugzilla-Product: nautilus Bugzilla-Component: general Bugzilla-Version: 2.12.1 BugBuddy-GnomeVersion: 2.0 (2.12.0) Description: Description of the crash: Nautilus craches in folders with jpg images.In this case I opened a folder with a lot of images, very slow to open. Steps to reproduce the crash: 1. Open a folder with a lot of jpg images. 2. Mark all images. 3. Try to make a archive out of them. Expected Results: A zipped file How often does this happen? Every time for me. Additional Information: Every icon on the desktop is gone, only backgroung image visible. Everything is redrawn after the crash. Debugging Information: 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) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912597444288 (LWP 9582)] [New Thread 1074805088 (LWP 9628)] [New Thread 1074538848 (LWP 9627)] [New Thread 1074272608 (LWP 9626)] [New Thread 1074006368 (LWP 9618)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0x00002aaaacc070ca in waitpid () from /lib/libpthread.so.0
+ Trace 63489
Thread 5 (Thread 1074006368 (LWP 9618))
#7866 ------- Bug moved to this database by unknown@gnome.bugs 2005-10-11 22:22 UTC ------- Bugreport had an attachment. This cannot be imported to Bugzilla. Contact bugmaster@gnome.org if you are willing to write a patch for this. Description has been limited to 524288 bytes Unknown version 2.12.1 in product nautilus. Setting version to "2.12.x". The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@gnome.bugs. Previous reporter was jonrue@start.no.
Thanks for the bug report. 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.
Then I have tried every suggested way from http://live.gnome.org/GettingTraces to get those debugging symbols. The only thing I am able to get is this: (gdb) thread apply all bt
+ Trace 63504
Thread 6 (Thread 1074006368 (LWP 10846))
Did you also follow http://live.gnome.org/GettingTraces/DistroSpecificInstructions ?
Is this better then? Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 46912597444288 (LWP 17710)] [New Thread 1074805088 (LWP 17714)] [New Thread 1074538848 (LWP 17713)] [New Thread 1074272608 (LWP 17712)] [New Thread 1074006368 (LWP 17711)] 0x00002aaaacc070ca in waitpid () from /lib/libpthread.so.0
+ Trace 63506
Thread 5 (Thread 1074006368 (LWP 17711))
Thanks for your verbose stack trace! Looks like an extension badness. What nautilus extensions do you have installed? You can find it out by removing Nautilus from the GNOME session, and then running Nautilus from a terminal like NAUTILUS_DEBUG=1 nautilus
Removing nautilus? Do you mean to stop it? I have tried to start nautilus with NAUTILUS_DEBUG=1 nautilus but that does not give me any feedback. Sorry if I'm missing something but I'm not so used to this debugging process.
> Removing nautilus? Do you mean to stop it? Exactly. If you don't stop Nautilus before running it with NAUTILUS_DEBUG set to 1, running the nautilus binary will control the running Nautilus instance. Therefore, you'll have to run "gnome-session-properties" (can also be accessed through the preferences menu) and remove Nautilus from the "Current Session".
OK. Thanks for the info. When I did this the archive command actually worked in the first directory I tried, but crashed in the next. This is the output on the command line. jon@home:~$ NAUTILUS_DEBUG=1 nautilus FRArchive::action_started: 1 Variable "selection" is not available. Variable "file" is not available. Variable "handle" is not available. Variable "data" is not available. Variable "self" is not available. Variable "argc" is not available. Variable "self" is not available. /usr/share/bug-buddy/gdb-cmd:2: Error in sourced command file: Variable "some_ready" is not available.
Reassigning to file-roller, which provides the archive functionality.
Updating bug status.
changed product to nautilus
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 320230 ***