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 373812 - crash in CD/DVD Creator: I was viewing a folder, ...
crash in CD/DVD Creator: I was viewing a folder, ...
Status: RESOLVED DUPLICATE of bug 356666
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-11-11 12:33 UTC by vandeley.industries
Modified: 2006-11-12 11:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description vandeley.industries 2006-11-11 12:33:37 UTC
What were you doing when the application crashed?
I was viewing a folder, and I clicked on the "UP" button in the Nautilus taskbar to navigate up one level in the filesystem and the application crashed
-- I was also viewing DVB using gxine on the desktop at the same time, but this application continued working fine


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

Memory status: size: 220700672 vsize: 220700672 resident: 33624064 share: 21610496 rss: 33624064 rss_rlim: -1
CPU usage: start_time: 1163241310 rtime: 218 utime: 203 stime: 15 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47904182745632 (LWP 5360)]
[New Thread 1099053392 (LWP 13738)]
(no debugging symbols found)
0x00002b918c6fd7f6 in poll () from /lib/libc.so.6

Thread 2 (Thread 1099053392 (LWP 13738))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 cairo_restore
    from /usr/lib/libcairo.so.2
  • #4 pango_cairo_show_glyph_string
    from /usr/lib/libpangocairo-1.0.so.0
  • #5 pango_renderer_draw_glyphs
    from /usr/lib/libpango-1.0.so.0
  • #6 pango_renderer_draw_layout_line
    from /usr/lib/libpango-1.0.so.0
  • #7 pango_renderer_draw_layout
    from /usr/lib/libpango-1.0.so.0
  • #8 pango_cairo_show_error_underline
    from /usr/lib/libpangocairo-1.0.so.0
  • #9 rsvg_error_get_type
    from /usr/lib/librsvg-2.so.2
  • #10 rsvg_handle_new_from_data
    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_new_from_data
    from /usr/lib/librsvg-2.so.2
  • #20 rsvg_handle_new_from_data
    from /usr/lib/librsvg-2.so.2
  • #21 rsvg_handle_render_cairo_sub
    from /usr/lib/librsvg-2.so.2
  • #22 rsvg_handle_get_pixbuf_sub
    from /usr/lib/librsvg-2.so.2
  • #23 fill_info
    from /usr/lib/gtk-2.0/2.10.0/loaders/svg_loader.so
  • #24 gdk_pixbuf_loader_close
    from /usr/lib/libgdk_pixbuf-2.0.so.0
  • #25 gnome_gdk_pixbuf_new_from_uri_at_scale
    from /usr/lib/libgnomeui-2.so.0
  • #26 gnome_thumbnail_factory_generate_thumbnail
    from /usr/lib/libgnomeui-2.so.0
  • #27 nautilus_marshal_BOOLEAN__POINTER
  • #28 start_thread
    from /lib/libpthread.so.0
  • #29 clone
    from /lib/libc.so.6
  • #30 ??

Comment 1 Christian Kirbach 2006-11-12 11:16:43 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 356666 ***