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 435550 - crash in About GNOME: Credits were starting
crash in About GNOME: Credits were starting
Status: RESOLVED DUPLICATE of bug 431255
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-05-03 16:25 UTC by james
Modified: 2007-05-03 18:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description james 2007-05-03 16:25:02 UTC
Version: 2.18.0

What were you doing when the application crashed?
Credits were starting


Distribution: Fedora release 6.93 (Rawhide)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3116.fc7 #1 SMP Thu Apr 26 10:17:55 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 256937984 vsize: 256937984 resident: 15843328 share: 9564160 rss: 15843328 rss_rlim: 18446744073709551615
CPU usage: start_time: 1178209477 rtime: 40 utime: 32 stime: 8 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912665971488 (LWP 3509)]
(no debugging symbols found)
0x00002aaaaf63d805 in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912665971488 (LWP 3509))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 ??
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 pthread_mutex_lock
    from /lib64/libpthread.so.0
  • #4 ??
    from /usr/lib64/libcairo.so.2
  • #5 ??
    from /usr/lib64/libcairo.so.2
  • #6 ??
    from /usr/lib64/libcairo.so.2
  • #7 cairo_scaled_font_text_extents
    from /usr/lib64/libcairo.so.2
  • #8 ??
    from /usr/lib64/libpangocairo-1.0.so.0
  • #9 ??
    from /usr/lib64/libpangocairo-1.0.so.0
  • #10 ??
    from /usr/lib64/libpangocairo-1.0.so.0
  • #11 ??
    from /usr/lib64/libpango-1.0.so.0
  • #12 pango_shape
    from /usr/lib64/libpango-1.0.so.0
  • #13 ??
    from /usr/lib64/libpango-1.0.so.0
  • #14 ??
    from /usr/lib64/libpango-1.0.so.0
  • #15 ??
    from /usr/lib64/libpango-1.0.so.0
  • #16 ??
    from /usr/lib64/libpango-1.0.so.0
  • #17 pango_layout_get_pixel_extents
    from /usr/lib64/libpango-1.0.so.0
  • #18 pango_layout_get_pixel_size
    from /usr/lib64/libpango-1.0.so.0
  • #19 ??
    from /usr/lib64/libgnomecanvas-2.so.0
  • #20 g_object_set_valist
    from /lib64/libgobject-2.0.so.0
  • #21 gnome_canvas_item_set_valist
    from /usr/lib64/libgnomecanvas-2.so.0
  • #22 gnome_canvas_item_set
    from /usr/lib64/libgnomecanvas-2.so.0
  • #23 _start
  • #0 waitpid
    from /lib64/libpthread.so.0


----------- .xsession-errors ---------------------
localuser:james being added to access control list
SESSION_MANAGER=local/juju.internal:/tmp/.ICE-unix/3247
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
(gnome-about:3509): Pango-WARNING **: shape engine failure, expect ugly output. the offending font is 'DejaVu LGC Sans Bold Not-Rotated 0'
--------------------------------------------------
Comment 1 palfrey 2007-05-03 18:07:57 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 431255 ***