Bug 400126 – crash in CD/DVD Creator: Hit up to a folder with ...

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 400126 - crash in CD/DVD Creator: Hit up to a folder with ...


Summary:	crash in CD/DVD Creator: Hit up to a folder with ...


Status:	RESOLVED DUPLICATE of bug 357939

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-01-24 09:34 UTC by astronouth7303
Modified:	2007-01-24 13:39 UTC

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

Description astronouth7303 2007-01-24 09:34:42 UTC

What were you doing when the application crashed?
Hit up to a folder with lots of SVGs


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

Memory status: size: 217665536 vsize: 0 resident: 217665536 share: 0 rss: 56377344 rss_rlim: 0
CPU usage: start_time: 1169624788 rtime: 0 utime: 19916 stime: 0 cutime:18626 cstime: 0 timeout: 1290 it_real_value: 0 frequency: 2

Backtrace was generated from '/usr/bin/nautilus'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1227401552 (LWP 27605)]
[New Thread -1271526496 (LWP 7867)]
[New Thread -1345352800 (LWP 28859)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 104804

Thread 2 (Thread -1271526496 (LWP 7867))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 libgnomeui_segv_handle
at gnome-ui-init.c line 874
#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 __assert_fail
from /lib/tls/i686/cmov/libc.so.6
#8 cairo_ft_scaled_font_unlock_face
from /usr/lib/libcairo.so.2
#9 cairo_ft_scaled_font_lock_face
from /usr/lib/libcairo.so.2
#10 pango_cairo_fc_font_get_type
from /usr/lib/libpangocairo-1.0.so.0
#11 pango_fc_font_lock_face
from /usr/lib/libpangoft2-1.0.so.0
#12 script_engine_init
from /usr/lib/pango/1.5.0/modules/pango-basic-fc.so
#13 pango_coverage_new
from /usr/lib/libpango-1.0.so.0
#14 pango_shape
from /usr/lib/libpango-1.0.so.0
#15 pango_layout_set_width
from /usr/lib/libpango-1.0.so.0
#16 pango_layout_iter_get_char_extents
from /usr/lib/libpango-1.0.so.0
#17 pango_layout_iter_get_char_extents
from /usr/lib/libpango-1.0.so.0
#18 pango_layout_iter_get_char_extents
from /usr/lib/libpango-1.0.so.0
#19 pango_layout_get_pixel_extents
from /usr/lib/libpango-1.0.so.0
#20 pango_layout_get_pixel_size
from /usr/lib/libpango-1.0.so.0
#21 rsvg_handle_new_from_data
from /usr/lib/librsvg-2.so.2
#22 rsvg_handle_new_from_data
from /usr/lib/librsvg-2.so.2
#23 rsvg_handle_new_from_data
from /usr/lib/librsvg-2.so.2
#24 rsvg_handle_new_from_data
from /usr/lib/librsvg-2.so.2
#25 rsvg_handle_new_from_data
from /usr/lib/librsvg-2.so.2
#26 rsvg_handle_new_from_data
from /usr/lib/librsvg-2.so.2
#27 rsvg_handle_new_from_data
from /usr/lib/librsvg-2.so.2
#28 rsvg_handle_new_from_data
from /usr/lib/librsvg-2.so.2
#29 rsvg_handle_new_from_data
from /usr/lib/librsvg-2.so.2
#30 rsvg_handle_new_from_data
from /usr/lib/librsvg-2.so.2
#31 rsvg_handle_new_from_data
from /usr/lib/librsvg-2.so.2
#32 rsvg_handle_new_from_data
from /usr/lib/librsvg-2.so.2
#33 rsvg_handle_render_cairo_sub
from /usr/lib/librsvg-2.so.2
#34 rsvg_handle_get_pixbuf_sub
from /usr/lib/librsvg-2.so.2
#35 rsvg_handle_get_pixbuf
from /usr/lib/librsvg-2.so.2
#36 fill_info
from /usr/lib/gtk-2.0/2.10.0/loaders/svg_loader.so
#37 ??
#38 ??

Comment 1 Susana 2007-01-24 13:39:08 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 357939 ***