Bug 433644 – crash in Computer: Inserting pendrive... (m...

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 433644 - crash in Computer: Inserting pendrive... (m...


Summary:	crash in Computer: Inserting pendrive... (m...


Status:	RESOLVED DUPLICATE of bug 363417

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-04-26 16:46 UTC by gosrod
Modified:	2007-06-22 21:22 UTC

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

Description gosrod 2007-04-26 16:46:40 UTC

What were you doing when the application crashed?
Inserting pendrive... (manufacturer: Pentagram), and updatedownload has been in progres.


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

Memory status: size: 132907008 vsize: 0 resident: 132907008 share: 0 rss: 30351360 rss_rlim: 0
CPU usage: start_time: 1177601916 rtime: 0 utime: 1764 stime: 0 cutime:1220 cstime: 0 timeout: 544 it_real_value: 0 frequency: 99

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 -1226819920 (LWP 5798)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 130725

Thread 1 (Thread -1226819920 (LWP 5798))

#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
from /usr/lib/libgobject-2.0.so.0
#5 g_signal_handlers_disconnect_matched
from /usr/lib/libgobject-2.0.so.0
#6 fm_directory_view_bump_zoom_level
#7 fm_directory_view_bump_zoom_level
#8 g_object_unref
from /usr/lib/libgobject-2.0.so.0
#9 POA_Nautilus_MetafileMonitor__init
#10 POA_Nautilus_MetafileMonitor__init
#11 POA_Nautilus_MetafileMonitor__init
#12 POA_Nautilus_MetafileMonitor__init
#13 POA_Nautilus_MetafileMonitor__init
#14 nautilus_undo_transaction_unregister_object
#15 fm_directory_view_bump_zoom_level
#16 nautilus_clipboard_monitor_emit_changed
#17 nautilus_directory_async_state_changed
#18 nautilus_icon_container_request_update_all
#19 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#20 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#21 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#22 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#23 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#24 POA_Nautilus_MetafileMonitor__init
#25 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#26 ??
#0 __kernel_vsyscall

Comment 1 palfrey 2007-04-26 17:49:59 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot
to solve the problem, so it will be hard for the developers to fix that crash.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so.
Thanks in advance!

Comment 2 André Klapper 2007-06-22 21:22:55 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 363417 ***