Bug 409986 – Crach when connecting a USB-disk

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 409986 - Crach when connecting a USB-disk


Summary:	Crach when connecting a USB-disk


Status:	RESOLVED DUPLICATE of bug 368849

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-02-20 11:52 UTC by bugs
Modified:	2007-02-20 17:20 UTC

See Also:
GNOME target:	---
GNOME version:	2.13/2.14

Description bugs 2007-02-20 11:50:15 UTC

Distribution: Ubuntu 6.10 (edgy)
Package: nautilus
Severity: Normal
Version: GNOME2.14.3 unspecified
Gnome-Distributor: Ubuntu
Synopsis: Crach when connecting a USB-disk
Bugzilla-Product: nautilus
Bugzilla-Component: general
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
When i connected my USB-disk it used poped up a Errormessage and asked
if i wanted to restart nautilus.

Steps to reproduce the crash:
1. be logged in (not sure its needed)
2. connect the disk
(3. try to open your home dir or somthing else that use nautilus) to
reproduce the error

Expected Results:
i dont know if there is some automout or somthing, but i connected the
disk to copy over some files there

How often does this happen?
when i connect the disk
or other use of nautilus when disk is connected

Additional Information:



Debugging Information:

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 -1225647456 (LWP 6574)]
[New Thread -1227682912 (LWP 6575)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 112285

Thread 1 (Thread -1225647456 (LWP 6574))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 _gtk_menu_is_empty
from /usr/lib/libgtk-x11-2.0.so.0
#5 _gtk_menu_is_empty
from /usr/lib/libgtk-x11-2.0.so.0
#6 _gtk_menu_is_empty
from /usr/lib/libgtk-x11-2.0.so.0
#7 _gtk_menu_is_empty
from /usr/lib/libgtk-x11-2.0.so.0
#8 _gtk_menu_is_empty
from /usr/lib/libgtk-x11-2.0.so.0
#9 gtk_ui_manager_ensure_update
from /usr/lib/libgtk-x11-2.0.so.0
#10 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#11 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#12 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#13 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#14 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#15 POA_Nautilus_MetafileFactory__fini
#16 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#17 ??
#0 __kernel_vsyscall





------- Bug created by bug-buddy at 2007-02-20 11:52 -------

Comment 1 palfrey 2007-02-20 17:20:42 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 368849 ***