Bug 382132 – crash in CD/DVD Creator: Browsing the current acc...

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 382132 - crash in CD/DVD Creator: Browsing the current acc...


Summary:	crash in CD/DVD Creator: Browsing the current acc...


Status:	RESOLVED DUPLICATE of bug 356666

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-12-04 04:40 UTC by Devaraj Aran
Modified:	2006-12-05 01:26 UTC

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

Description Devaraj Aran 2006-12-04 04:40:37 UTC

What were you doing when the application crashed?
Browsing the current account's home directory in "File Browser." I was using the navigation button to go up a directory level.


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

Memory status: size: 80846848 vsize: 0 resident: 80846848 share: 0 rss: 26468352 rss_rlim: 0
CPU usage: start_time: 1165207145 rtime: 0 utime: 229 stime: 0 cutime:189 cstime: 0 timeout: 40 it_real_value: 0 frequency: 110

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

+ Trace 91443

Thread 1 (Thread -1226414416 (LWP 8878))

#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 cairo_restore
from /usr/lib/libcairo.so.2
#5 pango_cairo_show_glyph_string
from /usr/lib/libpangocairo-1.0.so.0
#6 pango_renderer_draw_glyphs
from /usr/lib/libpango-1.0.so.0
#7 pango_cairo_renderer_get_type
from /usr/lib/libpangocairo-1.0.so.0
#8 gdk_draw_layout_line
from /usr/lib/libgdk-x11-2.0.so.0
#9 pango_renderer_draw_glyphs
from /usr/lib/libpango-1.0.so.0
#10 pango_renderer_draw_layout_line
from /usr/lib/libpango-1.0.so.0
#11 pango_renderer_draw_layout
from /usr/lib/libpango-1.0.so.0
#12 gdk_draw_layout_with_colors
from /usr/lib/libgdk-x11-2.0.so.0
#13 gdk_draw_layout
from /usr/lib/libgdk-x11-2.0.so.0
#14 nautilus_undo_transaction_unregister_object
#15 nautilus_undo_transaction_unregister_object
#16 eel_canvas_item_move
from /usr/lib/libeel-2.so.2
#17 eel_canvas_item_show
from /usr/lib/libeel-2.so.2
#18 nautilus_icon_container_request_update_all
#19 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#20 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#21 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#22 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#23 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#24 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#25 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#26 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#27 gdk_window_is_viewable
from /usr/lib/libgdk-x11-2.0.so.0
#28 gdk_window_process_all_updates
from /usr/lib/libgdk-x11-2.0.so.0
#29 gdk_window_process_all_updates
from /usr/lib/libgdk-x11-2.0.so.0
#30 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#31 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#32 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#33 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#34 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#35 POA_Nautilus_MetafileMonitor__init
#36 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#37 ??
#0 __kernel_vsyscall

Comment 1 André Klapper 2006-12-05 01:26:49 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 356666 ***