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 391251 - crash in Open Folder: clicar no icono -acima- ...
crash in Open Folder: clicar no icono -acima- ...
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-12-31 10:40 UTC by inacio
Modified: 2006-12-31 11:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description inacio 2006-12-31 10:40:28 UTC
What were you doing when the application crashed?
clicar no icono -acima- do nautilius, para entrar num  subdirectorio


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

Memory status: size: 88633344 vsize: 0 resident: 88633344 share: 0 rss: 32931840 rss_rlim: 0
CPU usage: start_time: 1167558633 rtime: 0 utime: 25884 stime: 0 cutime:24371 cstime: 0 timeout: 1513 it_real_value: 0 frequency: 460

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 -1227082064 (LWP 5032)]
[New Thread -1247671392 (LWP 7440)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 2 (Thread -1247671392 (LWP 7440))

  • #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-12-31 11:04:15 UTC
Fixed in CVS. The fix will go into the next patch release. Thank you for your bug report.
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 ***