Bug 467784 – crash in Open Folder: Unmounting an usb memory...

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 467784 - crash in Open Folder: Unmounting an usb memory...


Summary:	crash in Open Folder: Unmounting an usb memory...


Status:	RESOLVED DUPLICATE of bug 425157

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.18.x
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-08-17 20:03 UTC by yunta_gohan
Modified:	2007-08-23 19:04 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description yunta_gohan 2007-08-17 20:03:33 UTC

Version: 2.18.3

What were you doing when the application crashed?
Unmounting an usb memory stick (pqi,256Mb)


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Xfce-redmondxp
Icon Theme: Gion

Memory status: size: 97079296 vsize: 97079296 resident: 34615296 share: 22212608 rss: 34615296 rss_rlim: 4294967295
CPU usage: start_time: 1187376324 rtime: 1340 utime: 955 stime: 385 cutime:0 cstime: 14 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208641824 (LWP 2509)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 156005

Thread 1 (Thread -1208641824 (LWP 2509))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/libc.so.6
#6 abort
from /lib/libc.so.6
#7 g_logv
from /lib/libglib-2.0.so.0
#8 g_log
from /lib/libglib-2.0.so.0
#9 g_assert_warning
from /lib/libglib-2.0.so.0
#10 nautilus_connect_background_to_file_metadata
#11 ??
#12 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#13 ??
from /lib/libgobject-2.0.so.0
#14 g_closure_invoke
from /lib/libgobject-2.0.so.0
#15 ??
from /lib/libgobject-2.0.so.0
#16 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#17 g_signal_emit
from /lib/libgobject-2.0.so.0
#18 fm_directory_view_begin_loading
#19 ??
#20 ??
#21 ??
#22 ??
from /lib/libglib-2.0.so.0
#23 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#24 ??
from /lib/libglib-2.0.so.0
#25 g_main_loop_run
from /lib/libglib-2.0.so.0
#26 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#27 main
#0 __kernel_vsyscall



----------- .xsession-errors (14 sec old) ---------------------
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
closing
closing
closing
--- Hash table keys for warning below:
--> file:///root
(nautilus:2950): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
** (nautilus:2509): WARNING **: destroyed file still being monitored
** ERROR **: file nautilus-directory-background.c: line 621 (nautilus_connect_background_to_file_metadata): assertion failed: (NAUTILUS_IS_FILE (old_file))
aborting...
closing
--------------------------------------------------

Comment 1 Susana 2007-08-23 19:04:03 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 425157 ***