Bug 388108 – crash in CD/DVD Creator:

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


Summary:	crash in CD/DVD Creator:


Status:	RESOLVED DUPLICATE of bug 360691

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-20 23:58 UTC by business
Modified:	2006-12-21 15:17 UTC

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

Description business 2006-12-20 23:58:28 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: 128528384 vsize: 0 resident: 128528384 share: 0 rss: 36777984 rss_rlim: 0
CPU usage: start_time: 1166649236 rtime: 0 utime: 1446 stime: 0 cutime:1332 cstime: 0 timeout: 114 it_real_value: 0 frequency: 60

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 -1226848592 (LWP 4803)]
[New Thread -1237701728 (LWP 11375)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 95832

Thread 2 (Thread -1237701728 (LWP 11375))

#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_renderer_draw_layout_line
from /usr/lib/libpango-1.0.so.0
#8 pango_renderer_draw_layout
from /usr/lib/libpango-1.0.so.0
#9 pango_cairo_show_error_underline
from /usr/lib/libpangocairo-1.0.so.0
#10 rsvg_error_get_type
from /usr/lib/librsvg-2.so.2
#11 rsvg_handle_new_from_data
from /usr/lib/librsvg-2.so.2
#12 rsvg_handle_new_from_data
from /usr/lib/librsvg-2.so.2
#13 rsvg_handle_new_from_data
from /usr/lib/librsvg-2.so.2
#14 rsvg_handle_new_from_data
from /usr/lib/librsvg-2.so.2
#15 rsvg_handle_new_from_data
from /usr/lib/librsvg-2.so.2
#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_render_cairo_sub
from /usr/lib/librsvg-2.so.2
#19 rsvg_handle_get_pixbuf_sub
from /usr/lib/librsvg-2.so.2
#20 rsvg_handle_get_pixbuf
from /usr/lib/librsvg-2.so.2
#21 fill_info
from /usr/lib/gtk-2.0/2.10.0/loaders/svg_loader.so
#22 ??
#23 ??

Comment 1 Susana 2006-12-21 15:17:18 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 360691 ***