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 433905 - crash in CD/DVD Creator: browsing my filesystem
crash in CD/DVD Creator: browsing my filesystem
Status: RESOLVED DUPLICATE of bug 364620
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-04-27 16:32 UTC by gripepe
Modified: 2007-04-28 07:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description gripepe 2007-04-27 16:32:46 UTC 
What were you doing when the application crashed?
browsing my filesystem


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

Memory status: size: 95432704 vsize: 0 resident: 95432704 share: 0 rss: 33390592 rss_rlim: 0
CPU usage: start_time: 1177686932 rtime: 0 utime: 2042 stime: 0 cutime:1818 cstime: 0 timeout: 224 it_real_value: 0 frequency: 157

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 -1226955088 (LWP 5176)]
[New Thread -1247028320 (LWP 9197)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 130922

Thread 2 (Thread -1247028320 (LWP 9197))

  • #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 FcFreeTypeCharIndex
    from /usr/lib/libfontconfig.so.1
  • #5 pango_fc_font_lock_face
    from /usr/lib/libpangoft2-1.0.so.0
  • #6 pango_fc_font_get_glyph
    from /usr/lib/libpangoft2-1.0.so.0
  • #7 script_engine_init
    from /usr/lib/pango/1.5.0/modules/pango-hangul-fc.so
  • #8 script_engine_init
    from /usr/lib/pango/1.5.0/modules/pango-hangul-fc.so
  • #9 pango_coverage_new
    from /usr/lib/libpango-1.0.so.0
  • #10 pango_shape
    from /usr/lib/libpango-1.0.so.0
  • #11 pango_layout_set_width
    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_iter_get_char_extents
    from /usr/lib/libpango-1.0.so.0
  • #15 pango_fc_font_create_metrics_for_context
    from /usr/lib/libpangoft2-1.0.so.0
  • #16 pango_cairo_fc_font_get_type
    from /usr/lib/libpangocairo-1.0.so.0
  • #17 pango_font_get_metrics
    from /usr/lib/libpango-1.0.so.0
  • #18 pango_layout_line_get_extents
    from /usr/lib/libpango-1.0.so.0
  • #19 pango_layout_line_get_pixel_extents
    from /usr/lib/libpango-1.0.so.0
  • #20 pango_layout_iter_get_char_extents
    from /usr/lib/libpango-1.0.so.0
  • #21 pango_layout_get_pixel_extents
    from /usr/lib/libpango-1.0.so.0
  • #22 pango_layout_get_pixel_size
    from /usr/lib/libpango-1.0.so.0
  • #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_render_cairo_sub
    from /usr/lib/librsvg-2.so.2
  • #30 rsvg_handle_get_pixbuf_sub
    from /usr/lib/librsvg-2.so.2
  • #31 rsvg_handle_get_pixbuf
    from /usr/lib/librsvg-2.so.2
  • #32 fill_info
    from /usr/lib/gtk-2.0/2.10.0/loaders/svg_loader.so
  • #33 ??
  • #34 ?? 






Comment 1


Pascal Terjan





          2007-04-28 07:03:24 UTC
        



Thanks 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 364620 ***