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 442218 - crash in Computer: Browsing folders. This h...
crash in Computer: Browsing folders. This h...
Status: RESOLVED DUPLICATE of bug 357939
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-05-30 04:12 UTC by David Martin
Modified: 2007-05-31 11:46 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description David Martin 2007-05-30 04:12:17 UTC
What were you doing when the application crashed?
Browsing folders. This has happened a few times in recent days. The cause may be some SVG files I have - Nautilus is apparently crashing when it is trying to create preview icons for the SVG files (or possibly some PDF files I have in the same folder). Inkscape created these SVG files, but I also note that Inkscape crashes on a regular basis when trying to read vector-based images from other programs.


Distribution: openSUSE 10.2 (i586)
Gnome Release: 2.16.1 2006-11-28 (SUSE)
BugBuddy Version: 2.16.0

Memory status: size: 107569152 vsize: 0 resident: 107569152 share: 0 rss: 12087296 rss_rlim: 0
CPU usage: start_time: 1180497460 rtime: 0 utime: 741 stime: 0 cutime:551 cstime: 0 timeout: 190 it_real_value: 0 frequency: 746

Backtrace was generated from '/opt/gnome/bin/nautilus'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1227929920 (LWP 24045)]
[New Thread -1240880240 (LWP 1620)]
0xb7f7d410 in ?? ()

Comment 1 palfrey 2007-05-30 10:48:06 UTC
Can you reproduce this while running nautilus under gdb? See http://live.gnome.org/GettingTraces/Details#gdb-not-yet-running for details how to do this.
Comment 2 David Martin 2007-05-31 00:42:30 UTC
(In reply to comment #1)

It took a little effort but here you go:

...<snip>...
Program received signal SIGABRT, Aborted.
[Switching to Thread -1228343616 (LWP 20188)]
0xb7f18410 in ?? ()
(gdb) thread apply all bt

Thread 1 (Thread -1228343616 (LWP 20188))

  • #0 ??
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 raise
    from /lib/libc.so.6
  • #5 abort
    from /lib/libc.so.6
  • #6 __assert_fail
    from /lib/libc.so.6
  • #7 cairo_ft_scaled_font_unlock_face
    from /usr/lib/libcairo.so.2
  • #8 cairo_ft_scaled_font_lock_face
    from /usr/lib/libcairo.so.2
  • #9 pango_cairo_fc_font_get_type
    from /opt/gnome/lib/libpangocairo-1.0.so.0
  • #10 pango_fc_font_lock_face
    from /opt/gnome/lib/libpangoft2-1.0.so.0
  • #11 script_engine_init
    from /opt/gnome/lib/pango/1.5.0/modules/pango-basic-fc.so
  • #12 pango_coverage_set
    from /opt/gnome/lib/libpango-1.0.so.0
  • #13 pango_shape
    from /opt/gnome/lib/libpango-1.0.so.0
  • #14 pango_layout_set_width
    from /opt/gnome/lib/libpango-1.0.so.0
  • #15 pango_layout_iter_get_char_extents
    from /opt/gnome/lib/libpango-1.0.so.0
  • #16 pango_layout_iter_get_char_extents
    from /opt/gnome/lib/libpango-1.0.so.0
  • #17 pango_layout_iter_get_char_extents
    from /opt/gnome/lib/libpango-1.0.so.0
  • #18 pango_layout_get_pixel_extents
    from /opt/gnome/lib/libpango-1.0.so.0
  • #19 gtk_cell_renderer_text_new
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #20 gtk_cell_renderer_text_new
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #21 gtk_cell_renderer_render
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #22 gtk_tree_view_column_focus_cell
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #23 gtk_tree_view_column_cell_is_visible
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #24 gtk_tree_view_get_hadjustment
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #25 gtk_marshal_BOOLEAN__VOID
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #26 g_type_class_meta_marshal
    at gclosure.c line 567
  • #27 g_closure_invoke
    at gclosure.c line 490
  • #28 signal_emit_unlocked_R
    at gsignal.c line 2478
  • #29 g_signal_emit_valist
    at gsignal.c line 2209
  • #30 g_signal_emit
    at gsignal.c line 2243
  • #31 gtk_widget_get_default_style
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #32 gtk_main_do_event
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #33 gdk_window_is_viewable
    from /opt/gnome/lib/libgdk-x11-2.0.so.0
  • #34 gdk_window_process_all_updates
    from /opt/gnome/lib/libgdk-x11-2.0.so.0
  • #35 gdk_window_process_all_updates
    from /opt/gnome/lib/libgdk-x11-2.0.so.0
  • #36 g_idle_dispatch
    at gmain.c line 3926
  • #37 g_main_context_dispatch
    at gmain.c line 2045
  • #38 g_main_context_iterate
    at gmain.c line 2677
  • #39 g_main_loop_run
    at gmain.c line 2881
  • #40 gtk_main
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #41 main
    at nautilus-main.c line 513
  • #42 __libc_start_main
    from /lib/libc.so.6
  • #43 _start

Comment 3 palfrey 2007-05-31 11:46:07 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 357939 ***