Bug 369868 – crash in Computer: I was trying to click on...

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 369868 - crash in Computer: I was trying to click on...


Summary:	crash in Computer: I was trying to click on...


Status:	RESOLVED DUPLICATE of bug 351713

Product:	nautilus
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-11-03 07:47 UTC by james.whitaker
Modified:	2006-11-03 10:34 UTC

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

Description james.whitaker 2006-11-03 07:47:23 UTC

What were you doing when the application crashed?
I was trying to click on the windows network icon to look around the windows network.  It froze.  Eventually this bug report thing popped up.


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 126943232 vsize: 0 resident: 126943232 share: 0 rss: 16998400 rss_rlim: 0
CPU usage: start_time: 1162539741 rtime: 0 utime: 284 stime: 0 cutime:234 cstime: 0 timeout: 50 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208244528 (LWP 3294)]
(no debugging symbols found)
0x00551402 in __kernel_vsyscall ()

+ Trace 82244

Thread 1 (Thread -1208244528 (LWP 3294))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/i686/nosegneg/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 nautilus_directory_async_state_changed
#5 nautilus_file_get_uri
#6 nautilus_file_get_uri
#7 nautilus_file_has_volume
#8 nautilus_icon_container_request_update_all
#9 fm_directory_view_bump_zoom_level
#10 nautilus_file_ref
#11 nautilus_file_ref
#12 fm_directory_view_bump_zoom_level
#13 nautilus_marshal_VOID__OBJECT_OBJECT
#14 g_value_set_static_boxed
from /lib/libgobject-2.0.so.0
#15 g_closure_invoke
from /lib/libgobject-2.0.so.0
#16 g_signal_override_class_closure
from /lib/libgobject-2.0.so.0
#17 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#18 g_signal_emit
from /lib/libgobject-2.0.so.0
#19 fm_directory_view_bump_zoom_level
#20 g_source_get_current_time
from /lib/libglib-2.0.so.0
#21 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#22 g_main_context_check
from /lib/libglib-2.0.so.0
#23 g_main_loop_run
from /lib/libglib-2.0.so.0
#24 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#25 POA_Nautilus_MetafileMonitor__init
#26 __libc_start_main
from /lib/i686/nosegneg/libc.so.6
#27 g_cclosure_marshal_VOID__ENUM
#0 __kernel_vsyscall

Comment 1 André Klapper 2006-11-03 10:34:54 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 351713 ***