Bug 380942 – crash in Computer: open nautilus

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 380942 - crash in Computer: open nautilus


Summary:	crash in Computer: open nautilus


Status:	RESOLVED DUPLICATE of bug 362370

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-30 16:20 UTC by mukitti
Modified:	2006-11-30 18:28 UTC

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

Description mukitti 2006-11-30 16:20:18 UTC

What were you doing when the application crashed?
open nautilus	


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

Memory status: size: 87085056 vsize: 0 resident: 87085056 share: 0 rss: 32022528 rss_rlim: 0
CPU usage: start_time: 1164899943 rtime: 0 utime: 1365 stime: 0 cutime:1178 cstime: 0 timeout: 187 it_real_value: 0 frequency: 297

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

+ Trace 90582

Thread 1 (Thread -1226484048 (LWP 4701))

#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 __kernel_vsyscall
#5 raise
from /lib/tls/i686/cmov/libc.so.6
#6 abort
from /lib/tls/i686/cmov/libc.so.6
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#10 pango_layout_iter_get_char_extents
from /usr/lib/libpango-1.0.so.0
#11 pango_layout_iter_get_char_extents
from /usr/lib/libpango-1.0.so.0
#12 nautilus_undo_transaction_unregister_object
#13 nautilus_undo_transaction_unregister_object
#14 nautilus_undo_transaction_unregister_object
#15 nautilus_undo_transaction_unregister_object
#16 eel_canvas_item_get_bounds
from /usr/lib/libeel-2.so.2
#17 nautilus_file_ref
#18 nautilus_file_ref
#19 nautilus_file_ref
#20 fm_directory_view_bump_zoom_level
#21 nautilus_undo_transaction_unregister_object
#22 POA_Nautilus_MetafileMonitor__init
#23 nautilus_undo_transaction_unregister_object
#24 fm_directory_view_bump_zoom_level
#25 fm_directory_view_bump_zoom_level
#26 g_source_get_current_time
from /usr/lib/libglib-2.0.so.0
#27 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#28 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#29 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#30 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#31 POA_Nautilus_MetafileMonitor__init
#32 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#33 ??
#0 __kernel_vsyscall

Comment 1 Germán Poo-Caamaño 2006-11-30 18:28:56 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 362370 ***