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 95095 - Nautilus crash at startup
Nautilus crash at startup
Status: RESOLVED DUPLICATE of bug 93102
Product: nautilus
Classification: Core
Component: general
2.0.x
Other Linux
: Normal major
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-10-07 17:26 UTC by Victor Manuel de Frutos
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Victor Manuel de Frutos 2002-10-07 17:26:38 UTC
When I run nautilus it segfaults. When I execute it with gdb it complains:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1024 (LWP 411)]
0x4031803b in MiniXftPatternFind () from /usr/lib/libpangoft2-1.0.so.0

expected result:

It should run nautilus


How often does this happen?

Always
Comment 1 John Fleck 2002-10-08 02:49:27 UTC
Need to know more specifically what version, and a stack trace also is
essential.
Comment 2 Victor Manuel de Frutos 2002-10-09 11:30:00 UTC
I'm using Debian Sid with Nautilus-2_2.0.7-1

The backtrace what I obtain is:

  • #0 MiniXftPatternFind
    from /usr/lib/libpangoft2-1.0.so.0
  • #1 MiniXftPatternGet
    from /usr/lib/libpangoft2-1.0.so.0
  • #2 MiniXftPatternGetString
    from /usr/lib/libpangoft2-1.0.so.0
  • #3 pango_ft2_font_set_glyph_cache_destroy
    from /usr/lib/libpangoft2-1.0.so.0
  • #4 g_hash_table_lookup
    from /usr/lib/libglib-2.0.so.0
  • #5 _pango_ft2_font_map_remove
    from /usr/lib/libpangoft2-1.0.so.0
  • #6 _pango_ft2_font_map_remove
    from /usr/lib/libpangoft2-1.0.so.0
  • #7 pango_font_map_load_fontset
    from /usr/lib/libpango-1.0.so.0
  • #8 pango_itemize
    from /usr/lib/libpango-1.0.so.0
  • #9 pango_itemize
    from /usr/lib/libpango-1.0.so.0
  • #10 pango_layout_get_pixel_size
    from /usr/lib/libpango-1.0.so.0
  • #11 pango_layout_get_cursor_pos
    from /usr/lib/libpango-1.0.so.0
  • #12 pango_layout_get_extents
    from /usr/lib/libpango-1.0.so.0
  • #13 pango_layout_get_pixel_size
    from /usr/lib/libpango-1.0.so.0
  • #14 gtk_widget_grab_focus
  • #15 gtk_widget_grab_focus
  • #16 gtk_widget_grab_focus
  • #17 gtk_widget_grab_focus
  • #18 gtk_widget_grab_focus
  • #19 gtk_widget_grab_focus
  • #20 gtk_widget_grab_focus
  • #21 gtk_widget_grab_focus
  • #22 gtk_widget_grab_focus
  • #23 gtk_widget_grab_focus
  • #24 gtk_widget_grab_focus
  • #25 gtk_widget_grab_focus
  • #26 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #27 g_object_newv
    from /usr/lib/libgobject-2.0.so.0
  • #28 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #29 gtk_widget_new
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 gtk_widget_grab_focus
  • #31 gtk_widget_grab_focus
  • #32 gtk_widget_grab_focus
  • #33 gtk_widget_grab_focus
  • #34 gtk_widget_grab_focus
  • #35 gtk_widget_grab_focus
  • #36 __libc_start_main
    from /lib/libc.so.6

Comment 3 Luis Villa 2002-10-21 18:20:11 UTC

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