Bug 430140 – crash in Open Folder: Trying write a DVD 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 430140 - crash in Open Folder: Trying write a DVD with ...


Summary:	crash in Open Folder: Trying write a DVD 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-04-15 23:25 UTC by stein.gustavo
Modified:	2007-04-16 15:04 UTC

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

Description stein.gustavo 2007-04-15 23:25:57 UTC

What were you doing when the application crashed?
Trying write a DVD with UDF format.


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

Memory status: size: 116334592 vsize: 0 resident: 116334592 share: 0 rss: 29360128 rss_rlim: 0
CPU usage: start_time: 1176678949 rtime: 0 utime: 332 stime: 0 cutime:303 cstime: 0 timeout: 29 it_real_value: 0 frequency: 0

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 -1227299152 (LWP 21453)]
[New Thread -1279263840 (LWP 22185)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 128092

Thread 2 (Thread -1279263840 (LWP 22185))

#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 __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 rsvg_error_get_type
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_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_render_cairo_sub
from /usr/lib/librsvg-2.so.2
#32 rsvg_handle_get_pixbuf_sub
from /usr/lib/librsvg-2.so.2
#33 rsvg_handle_get_pixbuf
from /usr/lib/librsvg-2.so.2
#34 fill_info
from /usr/lib/gtk-2.0/2.10.0/loaders/svg_loader.so
#35 ??
#36 ??

Comment 1 palfrey 2007-04-16 15:04:25 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 ***