Bug 379161 – crash in Computer:

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 379161 - crash in Computer:


Summary:	crash in Computer:


Status:	RESOLVED DUPLICATE of bug 361093

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-25 15:11 UTC by pipichar
Modified:	2006-11-25 19:44 UTC

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

Description pipichar 2006-11-25 15:11:50 UTC

What were you doing when the application crashed?



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

Memory status: size: 100249600 vsize: 0 resident: 100249600 share: 0 rss: 36675584 rss_rlim: 0
CPU usage: start_time: 1164464764 rtime: 0 utime: 2754 stime: 0 cutime:2634 cstime: 0 timeout: 120 it_real_value: 0 frequency: 0

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

+ Trace 89278

Thread 1 (Thread -1226701136 (LWP 4223))

#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_undo_transaction_unregister_object
#18 nautilus_undo_transaction_unregister_object
#19 eel_canvas_item_request_update
from /usr/lib/libeel-2.so.2
#20 eel_canvas_root
from /usr/lib/libeel-2.so.2
#21 eel_canvas_item_request_update
from /usr/lib/libeel-2.so.2
#22 eel_canvas_c2w
from /usr/lib/libeel-2.so.2
#23 eel_canvas_set_scroll_region
from /usr/lib/libeel-2.so.2
#24 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#25 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#26 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#27 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#28 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#29 POA_Nautilus_MetafileMonitor__init
#30 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#31 ??
#0 __kernel_vsyscall

Comment 1 Jens Granseuer 2006-11-25 19:44:19 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 361093 ***