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 464949 - crash in About GNOME: Q???????linux???????feso...
crash in About GNOME: Q???????linux???????feso...
Status: RESOLVED DUPLICATE of bug 461849
Product: gnome-desktop
Classification: Core
Component: gnome-about
2.18.x
Other All
: High critical
: ---
Assigned To: Desktop Maintainers
Desktop Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-08-09 07:28 UTC by uechi555
Modified: 2007-08-09 16:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description uechi555 2007-08-09 07:28:24 UTC
Version: 2.18.3

What were you doing when the application crashed?
Q1 私は始めてlinuxについて最近 fesora7を購入しましたが、私のus英語
   関係は全然解らず五里霧中です このぺーじが速く 日本語翻訳欄に
   なれば 凄く助かります
Q2 


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 67522560 vsize: 67522560 resident: 33144832 share: 17915904 rss: 33144832 rss_rlim: 4294967295
CPU usage: start_time: 1186729192 rtime: 1521 utime: 1465 stime: 56 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gnome-about'

(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 -1208178976 (LWP 2832)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208178976 (LWP 2832))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ??
    from /usr/lib/libpangoft2-1.0.so.0
  • #5 pango_fc_font_get_glyph
    from /usr/lib/libpangoft2-1.0.so.0
  • #6 ??
    from /usr/lib/pango/1.6.0/modules/pango-hangul-fc.so
  • #7 ??
    from /usr/lib/pango/1.6.0/modules/pango-hangul-fc.so
  • #8 ??
    from /usr/lib/libpango-1.0.so.0
  • #9 pango_shape
    from /usr/lib/libpango-1.0.so.0
  • #10 ??
    from /usr/lib/libpango-1.0.so.0
  • #11 ??
    from /usr/lib/libpango-1.0.so.0
  • #12 ??
    from /usr/lib/libpango-1.0.so.0
  • #13 ??
    from /usr/lib/libpango-1.0.so.0
  • #14 pango_layout_get_pixel_extents
    from /usr/lib/libpango-1.0.so.0
  • #15 pango_layout_get_pixel_size
    from /usr/lib/libpango-1.0.so.0
  • #16 ??
    from /usr/lib/libgnomecanvas-2.so.0
  • #17 g_object_set_valist
    from /lib/libgobject-2.0.so.0
  • #18 gnome_canvas_item_set_valist
    from /usr/lib/libgnomecanvas-2.so.0
  • #19 gnome_canvas_item_set
    from /usr/lib/libgnomecanvas-2.so.0
  • #20 _start
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
(gnome-about:2832): Pango-WARNING **: shape engine failure, expect ugly output. the offending font is 'DejaVu LGC Sans Bold Not-Rotated 0'
(gnome-about:2832): Pango-WARNING **: shape engine failure, expect ugly output. the offending font is 'DejaVu LGC Sans Bold Not-Rotated 0'
(gnome-about:2832): Pango-WARNING **: shape engine failure, expect ugly output. the offending font is 'DejaVu LGC Sans Bold Not-Rotated 0'
(gnome-about:2832): Pango-WARNING **: shape engine failure, expect ugly output. the offending font is 'DejaVu LGC Sans Bold Not-Rotated 0'
(gnome-about:2832): Pango-WARNING **: shape engine failure, expect ugly output. the offending font is 'DejaVu LGC Sans Bold Not-Rotated 0'
(gnome-about:2832): Pango-WARNING **: shape engine failure, expect ugly output. the offending font is 'DejaVu LGC Sans Bold Not-Rotated 0'
GTK Accessibility Module initialized
Bonobo accessibility support initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
--------------------------------------------------
Comment 1 palfrey 2007-08-09 16:40:52 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 461849 ***