GNOME Bugzilla – Bug 320230
"create archive" sometimes crashes nautilus
Last modified: 2006-04-24 09:42:44 UTC
Steps to reproduce: 1. go to a certain folder on my hard disk (contains many images) 2. select several images, right click 3. choose "create archive" after that it crashes. Stack trace: (stacktrace is from bug-buddy) Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (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 -1226164000 (LWP 9417)] [New Thread -1238381648 (LWP 9429)] [New Thread -1235190864 (LWP 9426)] [New Thread -1234924624 (LWP 9425)] [New Thread -1234654288 (LWP 9424)] [New Thread -1233728592 (LWP 9423)] [New Thread -1227822160 (LWP 9418)] (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) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 63792
Thread 1 (Thread -1226164000 (LWP 9417))
Other information: The crash happens before the "create archive" dialog even shows up. I think it's in the code to get the selected files in nautilus, but of course it's just a guess. The crash is reproducable if I go in a certain directory and select the last 14-18 files. the browser is in "browse" mode (not spacial), single-click. I'm avalaible if you need more info. this is ubuntu breezy. I can't seem to be able to reproduce it 100% everytime but from my tests I have the feeling the following is true: If I select just one file in that folder, no crash. What's very interesting for you surely is that, if I manage to display the "create archive" once in that folder (like select only one file) then when i select the files that would make it crash, it doesn't crash anymore. in other words: - kill nautilus, start nautilus, go in that folder, select the files, create archive, crash - kill nautilus, start nautilus, go in that folder, select only one file, create archive, dialog shows, close it, select the files that make it crash, create archive NO CRASH.
*** Bug 320229 has been marked as a duplicate of this bug. ***
Backtrace was generated from '/opt/jhbuild/bin/nautilus' Using host libthread_db library "/lib/tls/libthread_db.so.1". `shared object read from target memory' has disappeared; keeping its symbols. [Thread debugging using libthread_db enabled] [New Thread -1226352960 (LWP 17811)] [New Thread -1248101456 (LWP 17867)] [New Thread -1246205008 (LWP 17824)] [New Thread -1245783120 (LWP 17823)] [New Thread -1239528528 (LWP 17814)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 63796
Thread 1 (Thread -1226352960 (LWP 17811))
Can confirm this for Gnome 2.12 Ubuntu 5.10/AMD64
Maybe you could also post your stack trace?
Created attachment 54676 [details] Backtrace crashed Nautilus
I attached a stack trace which I created with gdb. Bug-buddy does not work for me, see bug 321296
*** Bug 321418 has been marked as a duplicate of this bug. ***
*** Bug 322676 has been marked as a duplicate of this bug. ***
*** Bug 323182 has been marked as a duplicate of this bug. ***
Fixed on both branches: 2005-12-10 Martin Wehner <martin.wehner@gmail.com> * src/file-manager/fm-directory-view.c: (extension_action_slow_mime_types_ready_callback), (extension_action_callback), (add_extension_action_for_files): Keep the original action refed till its activation callback is done. Prevents the callback data from being freed prematurely. Fixes #320230.
*** Bug 318620 has been marked as a duplicate of this bug. ***
*** Bug 323939 has been marked as a duplicate of this bug. ***
*** Bug 325580 has been marked as a duplicate of this bug. ***
*** Bug 326762 has been marked as a duplicate of this bug. ***
*** Bug 326834 has been marked as a duplicate of this bug. ***
Hi! After reporting a duplicate of this bug, I now discover the status is "resolved". I am using Ubuntu 5.10 "Breezy Badger" with Gnome 2.12.1, as I see others reporting this bug also do. Do you guys have any idea how I could possibly benefit from the resolution of this bug? Will Ubuntu post an update for Breezy? Should I download something from another source, or from Gnome? I'm kind of new to reporting bugs and trying to fix problems. The last bug I encoutered didn't bother me as much as this one. But in this case, I *really* need to make backups of my home directory. Pointers, anyone?
(In reply to comment #16) > Do you guys have any idea how I could possibly benefit from the resolution of > this bug? Will Ubuntu post an update for Breezy? Should I download something > from another source, or from Gnome? Crasher with easy fix available are usually fixed to Ubuntu stable distributions when known to be an issue for users and known by the maintainer of the package. Commenting on the distribution bug (if there is one open) to point that you face the bug or opening a new bug is a good start to get the bug fixed. I'm working on GNOME for Ubuntu and will upload a package with the patch within monday so no need to bother bugging on the distribution for that one :)
I just experienced this crash today as well. I'm fully up to date. When will this be fixed? What version?
Laran Evans: What version do you have?
(In reply to comment #19) > Laran Evans: What version do you have? > libgnome2-0: 2.12.0.1-0ubuntu1 nautilus: 2.12.1-0ubuntu1 Are those the libraries you meant?
For Ubuntu it's fixed with nautilus 2.12.1-0ubuntu1.2 from breezy-updates source
*** Bug 322488 has been marked as a duplicate of this bug. ***
*** Bug 322922 has been marked as a duplicate of this bug. ***
Hi guys! I got the update a few days ago, through regular Ubuntu updates. I now have nautilus 2.12.1-0ubuntu1.1 and everything works like a charm. Thank you so much for the quick response!!
Created attachment 58559 [details] backtrace
I'm also using 2.12.1-0ubuntu1.1, but I encounter this bug anyway. I've created an attachment with the backtrace from the bug buddy. The behaviour can be reproduced over and over again with the same folder
i'm also using breezy, and i didn't get that fix from breezy-updates. i'm wondering if it was well pushed? i'm getting some other changes from breezy-updates so my computer is well configured.
*** Bug 330186 has been marked as a duplicate of this bug. ***
*** Bug 329469 has been marked as a duplicate of this bug. ***
*** Bug 332397 has been marked as a duplicate of this bug. ***
*** Bug 332542 has been marked as a duplicate of this bug. ***
*** Bug 332540 has been marked as a duplicate of this bug. ***
I've approved Sebastien's upload of nautilus 2.12.1-0ubuntu1.2 to breezy-updates, so those of you running Ubuntu 5.10 should see it show up for upgrade soon. Sorry for the delay.
*** Bug 335616 has been marked as a duplicate of this bug. ***
*** Bug 335065 has been marked as a duplicate of this bug. ***
*** Bug 337736 has been marked as a duplicate of this bug. ***
*** Bug 339519 has been marked as a duplicate of this bug. ***