Bug 375454 – crash in CD/DVD Creator: I was using the file bro...

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 375454 - crash in CD/DVD Creator: I was using the file bro...


Summary:	crash in CD/DVD Creator: I was using the file bro...


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:	2006-11-15 09:13 UTC by jeremyakozan
Modified:	2006-11-15 22:42 UTC

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

Description jeremyakozan 2006-11-15 09:13:22 UTC

What were you doing when the application crashed?
I was using the file browser.  I didnt run CD/DVD creator or navigate to the CD/DVD vreator folder.  Other apps running included Totem Movie Player, RhythmBox, FireFox, and I had just closed Gimp.  I'm also using Beryl.


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

Memory status: size: 219643904 vsize: 219643904 resident: 27480064 share: 15953920 rss: 27480064 rss_rlim: -1
CPU usage: start_time: 1163560856 rtime: 7418 utime: 6296 stime: 1122 cutime:122 cstime: 34 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47803483568672 (LWP 4673)]
[New Thread 1073875280 (LWP 29913)]
(no debugging symbols found)
0x00002b7a1a4c57f6 in poll () from /lib/libc.so.6

+ Trace 86609

Thread 2 (Thread 1073875280 (LWP 29913))

#0 waitpid
from /lib/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#2 <signal handler called>
#3 raise
from /lib/libc.so.6
#4 abort
from /lib/libc.so.6
#5 __assert_fail
from /lib/libc.so.6
#6 cairo_ft_scaled_font_unlock_face
from /usr/lib/libcairo.so.2
#7 cairo_ft_scaled_font_lock_face
from /usr/lib/libcairo.so.2
#8 script_engine_init
from /usr/lib/pango/1.5.0/modules/pango-basic-fc.so
#9 pango_shape
from /usr/lib/libpango-1.0.so.0
#10 pango_layout_set_width
from /usr/lib/libpango-1.0.so.0
#11 pango_layout_iter_get_char_extents
from /usr/lib/libpango-1.0.so.0
#12 pango_layout_iter_get_char_extents
from /usr/lib/libpango-1.0.so.0
#13 pango_layout_iter_get_char_extents
from /usr/lib/libpango-1.0.so.0
#14 pango_layout_get_pixel_extents
from /usr/lib/libpango-1.0.so.0
#15 pango_layout_get_pixel_size
from /usr/lib/libpango-1.0.so.0
#16 rsvg_handle_new_from_data
from /usr/lib/librsvg-2.so.2
#17 rsvg_handle_new_from_data
from /usr/lib/librsvg-2.so.2
#18 rsvg_handle_new_from_data
from /usr/lib/librsvg-2.so.2
#19 rsvg_handle_new_from_data
from /usr/lib/librsvg-2.so.2
#20 rsvg_handle_new_from_data
from /usr/lib/librsvg-2.so.2
#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_render_cairo_sub
from /usr/lib/librsvg-2.so.2
#26 rsvg_handle_get_pixbuf_sub
from /usr/lib/librsvg-2.so.2
#27 fill_info
from /usr/lib/gtk-2.0/2.10.0/loaders/svg_loader.so
#28 gdk_pixbuf_loader_close
from /usr/lib/libgdk_pixbuf-2.0.so.0
#29 gnome_gdk_pixbuf_new_from_uri_at_scale
from /usr/lib/libgnomeui-2.so.0
#30 gnome_thumbnail_factory_generate_thumbnail
from /usr/lib/libgnomeui-2.so.0
#31 nautilus_marshal_BOOLEAN__POINTER
#32 start_thread
from /lib/libpthread.so.0
#33 clone
from /lib/libc.so.6
#34 ??

Comment 1 Christian Kirbach 2006-11-15 22:42:43 UTC

crash in cairo

2Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 357939 ***