Bug 390678 – crash in CD/DVD Creator: zip

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 390678 - crash in CD/DVD Creator: zip


Summary:	crash in CD/DVD Creator: zip


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-29 14:31 UTC by information
Modified:	2006-12-29 17:13 UTC

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

Description information 2006-12-29 14:31:09 UTC

What were you doing when the application crashed?
zip


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

Memory status: size: 116023296 vsize: 0 resident: 116023296 share: 0 rss: 35250176 rss_rlim: 0
CPU usage: start_time: 1167386278 rtime: 0 utime: 1572 stime: 0 cutime:1413 cstime: 0 timeout: 159 it_real_value: 0 frequency: 24

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

+ Trace 97792

Thread 1 (Thread -1226971472 (LWP 5469))

#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 gtk_style_attach
from /usr/lib/libgtk-x11-2.0.so.0
#15 gtk_paint_layout
from /usr/lib/libgtk-x11-2.0.so.0
#16 gtk_cell_renderer_text_new
from /usr/lib/libgtk-x11-2.0.so.0
#17 gtk_cell_renderer_render
from /usr/lib/libgtk-x11-2.0.so.0
#18 gtk_tree_view_column_focus_cell
from /usr/lib/libgtk-x11-2.0.so.0
#19 _gtk_tree_view_column_cell_render
from /usr/lib/libgtk-x11-2.0.so.0
#20 _gtk_tree_view_column_autosize
from /usr/lib/libgtk-x11-2.0.so.0
#21 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#22 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#23 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#24 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#25 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#26 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#27 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#28 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#29 gdk_window_is_viewable
from /usr/lib/libgdk-x11-2.0.so.0
#30 gdk_window_process_all_updates
from /usr/lib/libgdk-x11-2.0.so.0
#31 gdk_window_process_all_updates
from /usr/lib/libgdk-x11-2.0.so.0
#32 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#33 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#34 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#35 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#36 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#37 POA_Nautilus_MetafileMonitor__init
#38 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#39 ??
#0 __kernel_vsyscall

Comment 1 Jens Granseuer 2006-12-29 17:13:46 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 ***