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 367649 - crash in CD/DVD Creator: browsing files in /media...
crash in CD/DVD Creator: browsing files in /media...
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-10-30 14:13 UTC by grassglade
Modified: 2006-10-30 16:34 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description grassglade 2006-10-30 14:13:25 UTC
What were you doing when the application crashed?
browsing files in /media/d_win with nautilus and then click the UP button


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

Memory status: size: 170057728 vsize: 0 resident: 170057728 share: 0 rss: 45965312 rss_rlim: 0
CPU usage: start_time: 1162217454 rtime: 0 utime: 802 stime: 0 cutime:563 cstime: 0 timeout: 239 it_real_value: 0 frequency: 121

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 -1226545488 (LWP 6247)]
[New Thread -1249137760 (LWP 6562)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 2 (Thread -1249137760 (LWP 6562))

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

Comment 1 Christian Kirbach 2006-10-30 16:34:17 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 360691 ***