GNOME Bugzilla – Bug 112223
crashes when viewing an image and renaming it in a terminal
Last modified: 2005-07-15 11:27:21 UTC
1. view an image in nautilus ( double-click on it, not thumbnails ). 2. rename that image in a terminal 3. see nautilus window dissapear ( crash ) Using red hat linux 9.
Thanks for the bug report. Without a stack trace from the crash it's very hard to determine what caused the crash. Please see http://bugzilla.gnome.org/getting-traces.cgi for more information about getting a useful stack trace. Added keyword GNOMEVER2.2.
I don't have nautilus compiled with debugging symbols. Plus, when launched with strace ( or gdb ), it will exit normally when the window is displayed. This is 100% reproductible on a redhat 9 system, as described above.
I can't reproduce with 2.4.0. Can you still reproduce it, Marius?
Yes, nautilus 2.4.0 on fedora core test 2. I've tried with a .txt file (view as text in nautilus), the same problem. So might have something to do with nautilus-fam integration. Should I report this to Red Hat?
Still seeing this when I rename a file and then press "Update" in the nautilus window. It's not crashing, just closing the window.
Marking this up based on Kjartan's comment. I can't duplicate ATM, though; am asking #bugs to look at duplicating it.
Closing, only one person has reported this bug, i believe Kjartan is referring to a new bug in nautilus.
What's the point in closing it? It's there in 2.5.x latest too. Renaming a file which is shown by the image collection view makes it crash/error out when pressing ctrl+r two times. I get an error dialog and after that I can press ctrl+r again to get the images back.
Program received signal SIGTRAP, Trace/breakpoint trap.
+ Trace 44429
Thread NaN (LWP 31403)
We should probably move this to eog.
Just tested this on current eog and nautilus and it's still an issue. Here's my stack trace. Backtrace was generated from '/home/mike-unstable/sys-gnome-cvs/bin/nautilus' Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -150904704 (LWP 2096)] [New Thread 15719344 (LWP 8325)] [Thread debugging using libthread_db enabled] [New Thread -150904704 (LWP 2096)] [New Thread 15719344 (LWP 8325)] [Thread debugging using libthread_db enabled] [New Thread -150904704 (LWP 2096)] [New Thread 15719344 (LWP 8325)] [New Thread 13437872 (LWP 2104)] [New Thread 9878448 (LWP 2103)] [New Thread 123120560 (LWP 2097)] 0x00507402 in ?? ()
+ Trace 50584
Thread 1 (Thread -150904704 (LWP 2096))
i could not able to reproduce it on GNOME 2.9(head). It seems to be fixed.
Khasim: Martin and Luis were apparently not able to reproduce under previous versions, so it's hard to tell if it is fixed unless you were also able to get this bug with a previous version. Is that the case?
Yes you are right, i haven't tried with the previous version.
*** Bug 307556 has been marked as a duplicate of this bug. ***
Bug 310463 will for sure fix this. And if this bug still happens, then I would have seen it during the implementation for Bug 310463. Therefore I'm closing this one.