Bug 360211 – Refreshing (F5) while Nautilus is Showing / Crashes

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 360211 - Refreshing (F5) while Nautilus is Showing / Crashes


Summary:	Refreshing (F5) while Nautilus is Showing / Crashes


Status:	RESOLVED DUPLICATE of bug 348161

Product:	nautilus-cd-burner
Classification:	Deprecated
Component:	cd-burner
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus CD Burner Maintainers
QA Contact:	Nautilus CD Burner Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-10-06 16:16 UTC by Stu Hood
Modified:	2006-10-06 23:10 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description Stu Hood 2006-10-06 16:16:27 UTC

What were you doing when the application crashed?
1. Start with no ~/.hidden file
2. Open a Nautilus window, pointing to /
3. Create/save a ~/.hidden file with the following contents (ignore the tabs):
	/dev/
	/boot/
	/proc/
	/mnt/
4. Hit 'Refresh' in the Nautilus window
5. crash


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 80400384 vsize: 0 resident: 80400384 share: 0 rss: 26316800 rss_rlim: 0
CPU usage: start_time: 1160151065 rtime: 0 utime: 291 stime: 0 cutime:274 cstime: 0 timeout: 17 it_real_value: 0 frequency: 0

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)
[Thread debugging using libthread_db enabled]
[New Thread -1227110736 (LWP 6696)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 74941

Thread 1 (Thread -1227110736 (LWP 6696))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 g_type_check_instance_cast
from /usr/lib/libgobject-2.0.so.0
#5 fm_directory_view_bump_zoom_level
#6 nautilus_file_ref
#7 nautilus_icon_container_request_update_all
#8 fm_directory_view_bump_zoom_level
#9 fm_directory_view_supports_zooming
#10 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#11 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#15 nautilus_file_get_uri
#16 nautilus_file_get_uri
#17 nautilus_directory_async_state_changed
#18 gnome_vfs_job_get_count
from /usr/lib/libgnomevfs-2.so.0
#19 ??
#20 ??
#21 ??
#22 ??
from /usr/lib/libgthread-2.0.so.0
#23 ??
#24 ??
from /usr/lib/libglib-2.0.so.0
#25 ??
#26 g_slice_alloc
from /usr/lib/libglib-2.0.so.0
#27 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#28 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#29 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#30 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#31 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#32 POA_Nautilus_MetafileMonitor__init
#33 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#34 ??
#0 __kernel_vsyscall

Comment 1 Stu Hood 2006-10-06 16:22:35 UTC

Alright, it is a complete coincidence that this happened after I created the .hidden file... I tried to reproduce with/without the .hidden file, and it has nothing to do with those steps, so please _disregard_ them.

Instead, it simply happens every time I hit F5 while Nautilus is showing the / directory. I tried a few others, but only / seems to crash it.

Comment 2 Karsten Bräckelmann 2006-10-06 16:23:53 UTC

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 348161 ***

Comment 3 Stu Hood 2006-10-06 16:31:01 UTC

I need to stop using Bug-Buddy until they add some dup detection... sigh.

Thanks Karsten.

Comment 4 Karsten Bräckelmann 2006-10-06 23:10:51 UTC

My pleasure. And don't worry about the dupe. :)