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 378405 - crash in Computer: Trying to open a SVG ima...
crash in Computer: Trying to open a SVG ima...
Status: RESOLVED DUPLICATE of bug 360691
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-11-23 07:38 UTC by wj32.64
Modified: 2006-11-23 12:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description wj32.64 2006-11-23 07:38:07 UTC 
What were you doing when the application crashed?
Trying to open a SVG image. Either I clicked the image once and it crashed or I double-clicked it...


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

Memory status: size: 131911680 vsize: 0 resident: 131911680 share: 0 rss: 45166592 rss_rlim: 0
CPU usage: start_time: 1164261721 rtime: 0 utime: 3358 stime: 0 cutime:3132 cstime: 0 timeout: 226 it_real_value: 0 frequency: 968

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 -1227004240 (LWP 4817)]
[New Thread -1286952032 (LWP 13400)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 88723

Thread 2 (Thread -1286952032 (LWP 13400))

  • #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_new_from_data
    from /usr/lib/librsvg-2.so.2
  • #19 rsvg_handle_render_cairo_sub
    from /usr/lib/librsvg-2.so.2
  • #20 rsvg_handle_get_pixbuf_sub
    from /usr/lib/librsvg-2.so.2
  • #21 rsvg_handle_get_pixbuf
    from /usr/lib/librsvg-2.so.2
  • #22 fill_info
    from /usr/lib/gtk-2.0/2.10.0/loaders/svg_loader.so
  • #23 ??
  • #24 ?? 






Comment 1


André Klapper





          2006-11-23 12:45:16 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 ***