After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 137027 - browser window closes on clicking 'Up' from deleted directory
browser window closes on clicking 'Up' from deleted directory
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: general
2.13.x
Other All
: High normal
: 2.14.x
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 138278 156283 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-03-12 23:57 UTC by dschabus
Modified: 2006-02-27 14:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description dschabus 2004-03-12 23:57:51 UTC
hm, i couldn't find a better summary, sorry.

here's what i do: i open some folder in nautilus to display its contents. 
then i delete this folder from the command line (rm -rf foo/). nautilus of 
course still displays the contents of the folder, but when i hit the 
"back", the "up" or the "refresh" button, it crashes.
the latter creates an error message before crashing:

"foo" couldn't be found. Perhaps it has recently been deleted.

but with "back" or "up" nautilus just silently dissapears.

i hope this is a useful bug report,
greets from austria,
dietmar
Comment 1 Martin Wehner 2004-03-13 00:39:26 UTC
Hi Dietmar, 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.

Also, exactly which version of Nautilus 2.4.x (0,1,2) are you using?
Comment 2 dschabus 2004-03-13 10:47:21 UTC
I'm using Nautilus 2.4.1

Here's a stack trace I got using both bug-buddy and GDB:

Thread 7 (Thread 81926 (LWP 1725))

  • #0 sigsuspend
    from /lib/libc.so.6
  • #1 __pthread_wait_for_restart_signal
    from /lib/libpthread.so.0
  • #2 pthread_cond_wait
    from /lib/libpthread.
  • #3 thread_entry
    from /usr/lib/libgnomevfs-2.so.0
  • #4 g_thread_create_proxy
    from /usr/lib/libglib-2.0.
  • #5 pthread_start_thread
    from /lib/libpthread.so.0

Thread 6 (Thread 65541 (LWP 1724))

  • #0 sigsuspend
    from /lib/libc.so.6
  • #1 __pthread_wait_for_restart_signal
    from /lib/libpthread.so.0
  • #2 pthread_cond_wait
    from /lib/libpthread.
  • #3 thread_entry
    from /usr/lib/libgnomevfs-2.so.0
  • #4 g_thread_create_proxy
    from /usr/lib/libglib-2.0.
  • #5 pthread_start_thread
    from /lib/libpthread.so.0

Thread 5 (Thread 49156 (LWP 1721))

  • #0 sigsuspend
    from /lib/libc.so.6
  • #1 __pthread_wait_for_restart_signal
    from /lib/libpthread.so.0
  • #2 pthread_cond_wait
    from /lib/libpthread.
  • #3 thread_entry
    from /usr/lib/libgnomevfs-2.so.0
  • #4 g_thread_create_proxy
    from /usr/lib/libglib-2.0.
  • #5 pthread_start_thread
    from /lib/libpthread.so.0

Thread 4 (Thread 32771 (LWP 1720))

  • #0 sigsuspend
    from /lib/libc.so.6
  • #1 __pthread_wait_for_restart_signal
    from /lib/libpthread.so.0
  • #2 pthread_cond_wait
    from /lib/libpthread.
  • #3 thread_entry
    from /usr/lib/libgnomevfs-2.so.0
  • #4 g_thread_create_proxy
    from /usr/lib/libglib-2.0.
  • #5 pthread_start_thread
    from /lib/libpthread.so.0

Thread 3 (Thread 16386 (LWP 1719))

  • #0 sigsuspend
    from /lib/libc.so.6
  • #1 __pthread_wait_for_restart_signal
    from /lib/libpthread.so.0
  • #2 pthread_cond_wait
    from /lib/libpthread.
  • #3 thread_entry
    from /usr/lib/libgnomevfs-2.so.0
  • #4 g_thread_create_proxy
    from /usr/lib/libglib-2.0.
  • #5 pthread_start_thread
    from /lib/libpthread.so.0

hth
Comment 3 dschabus 2004-03-13 10:54:37 UTC
Ah, I forgot to say that I produced the crash that time using the 
refresh button, since that's the only way to produce an error message. 
The process number isn't included there, but I got it from System 
Monitor. (gdb nautilus 1711)
Comment 4 Bart Martens 2004-03-20 19:08:31 UTC
Also reported at Fedora bugzilla.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=118797

I see this happen with nautilus-2.4.0-7 on Fedora Core 1 and with
nautilus 2.4.2-2 on Debian sarge.

It's quite easy to reproduce. Have nautilus point to a directory. Then
mv the parent directory away. Then push the up button in nautilus.

I would lower priority/severity to normal/normal or lower.
Comment 5 Alexander Larsson 2004-03-26 15:40:46 UTC
It removes the window for me in HEAD, but doesn't actually crash.
Comment 6 dschabus 2004-03-27 18:43:52 UTC
hm well, perhaps "crash" was the wrong word, the process does stay alive for me 
as well.
but still, if you call it "removes the window", it's still a bug.
Comment 7 Alexander Larsson 2004-03-30 08:03:56 UTC
*** Bug 138278 has been marked as a duplicate of this bug. ***
Comment 8 Matthew Gatto 2004-10-29 06:41:00 UTC
It doesn't crash on HEAD for me, the browser window does close though after 'Up'
or 'Back' from the deleted directory.
Comment 9 Matthew Gatto 2004-10-29 06:41:53 UTC
*** Bug 156283 has been marked as a duplicate of this bug. ***
Comment 10 Andreas Volz 2005-10-14 06:32:29 UTC
I've this _bug_ too. I know it didn't crash, but for many people it behaves like
a crash. I (and many others) use nautilus in browser-mode with only one single
window open. Then I use famd, so I don't need to press a Up or Back key. Simply
stay in the directory and delete it from a shell should be enough to close the
window.

I think the correct behaviour should be to walk up the directory tree until a
directory exists. Or the browser should jump to /home/$user. I don't know which
is better.

For example if I stay in a mounted directory and unmount this from a shell,
Nautilus behave like I expect it. The browser jumps tp /home/$user. So please if
this isn't too much mork, please fix it for next version. Or if you don't like
it, please explain why. But this bug is nearly one year old and nothing happens.
Comment 11 Christian Neumair 2006-02-26 11:37:45 UTC
Still reproducible with Nautilus 2.13.
Comment 12 Christian Neumair 2006-02-26 12:33:28 UTC
Proposed patch:
http://mail.gnome.org/archives/nautilus-list/2006-February/msg00121.html
Comment 13 Alexander Larsson 2006-02-27 14:53:07 UTC
fixed.