Bug 406399 – crash in File Browser: unmount FireWire drive w...

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 406399 - crash in File Browser: unmount FireWire drive w...


Summary:	crash in File Browser: unmount FireWire drive w...


Status:	RESOLVED DUPLICATE of bug 348651

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:	2007-02-10 14:37 UTC by mart.verburg
Modified:	2007-02-10 21:00 UTC

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

Description mart.verburg 2007-02-10 14:37:35 UTC

What were you doing when the application crashed?
unmount FireWire drive while searching for files on internal disk


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

Memory status: size: 150237184 vsize: 0 resident: 150237184 share: 0 rss: 37097472 rss_rlim: 0
CPU usage: start_time: 1171113380 rtime: 0 utime: 13684 stime: 0 cutime:9473 cstime: 0 timeout: 4211 it_real_value: 0 frequency: 119

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 -1226586448 (LWP 4760)]
[New Thread -1406018656 (LWP 7697)]
[New Thread -1254949984 (LWP 5331)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 109532

Thread 1 (Thread -1226586448 (LWP 4760))

#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_str_hash
from /usr/lib/libglib-2.0.so.0
#5 g_hash_table_lookup
from /usr/lib/libglib-2.0.so.0
#6 nautilus_file_get_uri
#7 nautilus_file_get_uri
#8 nautilus_directory_async_state_changed
#9 nautilus_directory_async_state_changed
#10 nautilus_directory_async_state_changed
#11 g_hash_table_foreach
from /usr/lib/libglib-2.0.so.0
#12 nautilus_directory_ref
#13 nautilus_directory_ref
#14 nautilus_marshal_BOOLEAN__POINTER
#15 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#16 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#17 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#18 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#19 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#20 POA_Nautilus_MetafileMonitor__init
#21 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#22 ??
#0 __kernel_vsyscall

Comment 1 Christian Kirbach 2007-02-10 21:00:01 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 348651 ***