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 369145 - crash in CD/DVD Creator: Just opening a folder co...
crash in CD/DVD Creator: Just opening a folder co...
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-01 23:35 UTC by e-user
Modified: 2006-11-02 18:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description e-user 2006-11-01 23:35:20 UTC 
What were you doing when the application crashed?
Just opening a folder containing different images, also an svg. Maybe a gstreamer problem.


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 495964160 vsize: 495964160 resident: 39137280 share: 21483520 rss: 39137280 rss_rlim: -1
CPU usage: start_time: 1162406088 rtime: 4407 utime: 3915 stime: 492 cutime:188 cstime: 80 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496369120 (LWP 2756)]
[New Thread 1084365120 (LWP 7348)]
(no debugging symbols found)
0x00000037fa6c4b56 in poll () from /lib64/libc.so.6

+ Trace 81669

Thread 2 (Thread 1084365120 (LWP 7348))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 cairo_restore
    from /usr/lib64/libcairo.so.2
  • #4 pango_cairo_show_glyph_string
    from /usr/lib64/libpangocairo-1.0.so.0
  • #5 pango_renderer_draw_glyphs
    from /usr/lib64/libpango-1.0.so.0
  • #6 pango_renderer_draw_layout_line
    from /usr/lib64/libpango-1.0.so.0
  • #7 pango_renderer_draw_layout
    from /usr/lib64/libpango-1.0.so.0
  • #8 pango_cairo_show_error_underline
    from /usr/lib64/libpangocairo-1.0.so.0
  • #9 rsvg_error_get_type
    from /usr/lib64/librsvg-2.so.2
  • #10 rsvg_handle_new_from_data
    from /usr/lib64/librsvg-2.so.2
  • #11 rsvg_handle_new_from_data
    from /usr/lib64/librsvg-2.so.2
  • #12 rsvg_handle_new_from_data
    from /usr/lib64/librsvg-2.so.2
  • #13 rsvg_handle_new_from_data
    from /usr/lib64/librsvg-2.so.2
  • #14 rsvg_handle_new_from_data
    from /usr/lib64/librsvg-2.so.2
  • #15 rsvg_handle_new_from_data
    from /usr/lib64/librsvg-2.so.2
  • #16 rsvg_handle_new_from_data
    from /usr/lib64/librsvg-2.so.2
  • #17 rsvg_handle_new_from_data
    from /usr/lib64/librsvg-2.so.2
  • #18 rsvg_handle_new_from_data
    from /usr/lib64/librsvg-2.so.2
  • #19 rsvg_handle_new_from_data
    from /usr/lib64/librsvg-2.so.2
  • #20 rsvg_handle_new_from_data
    from /usr/lib64/librsvg-2.so.2
  • #21 rsvg_handle_new_from_data
    from /usr/lib64/librsvg-2.so.2
  • #22 rsvg_handle_new_from_data
    from /usr/lib64/librsvg-2.so.2
  • #23 rsvg_handle_render_cairo_sub
    from /usr/lib64/librsvg-2.so.2
  • #24 rsvg_handle_get_pixbuf_sub
    from /usr/lib64/librsvg-2.so.2
  • #25 fill_info
    from /usr/lib64/gtk-2.0/2.10.0/loaders/svg_loader.so
  • #26 gdk_pixbuf_loader_close
    from /usr/lib64/libgdk_pixbuf-2.0.so.0
  • #27 gnome_gdk_pixbuf_new_from_uri_at_scale
    from /usr/lib64/libgnomeui-2.so.0
  • #28 gnome_thumbnail_factory_generate_thumbnail
    from /usr/lib64/libgnomeui-2.so.0
  • #29 nautilus_marshal_BOOLEAN__POINTER
  • #30 start_thread
    from /lib64/libpthread.so.0
  • #31 clone
    from /lib64/libc.so.6
  • #32 ?? 






Comment 1


Behdad Esfahbod





          2006-11-01 23:37:54 UTC
        



Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
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 356666 ***






Comment 2


Behdad Esfahbod





          2006-11-02 18:32:24 UTC
        




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