Bug 388423 – crash in cairo_reference

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 388423 - crash in cairo_reference


Summary:	crash in cairo_reference


Status:	RESOLVED INCOMPLETE

Product:	pango
Classification:	Platform
Component:	general
Version:	1.14.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	pango-maint
QA Contact:	pango-maint

URL:
Whiteboard:

Duplicates:	394445 (view as bug list)
Depends on:
Blocks:

Reported:	2006-12-21 22:06 UTC by jonah
Modified:	2010-09-13 11:31 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description jonah 2006-12-21 22:06:38 UTC

Version: 2.16.1

What were you doing when the application crashed?
nothing really


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

Memory status: size: 33406976 vsize: 0 resident: 33406976 share: 0 rss: 12382208 rss_rlim: 0
CPU usage: start_time: 1166738776 rtime: 0 utime: 28 stime: 0 cutime:24 cstime: 0 timeout: 4 it_real_value: 0 frequency: 0

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 -1224739136 (LWP 5511)]
(no debugging symbols found)
0xb7de4a2e in __waitpid_nocancel () from /lib/libpthread.so.0

+ Trace 96081

Thread 1 (Thread -1224739136 (LWP 5511))

#0 __waitpid_nocancel
from /lib/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#2 <signal handler called>
#3 raise
from /lib/libc.so.6
#4 abort
from /lib/libc.so.6
#5 __assert_fail
from /lib/libc.so.6
#6 cairo_reference
from /usr/lib/libcairo.so.2
#7 cairo_reference
from /usr/lib/libcairo.so.2
#8 pango_cairo_fc_font_get_type
from /usr/lib/libpangocairo-1.0.so.0
#9 pango_cairo_font_get_type
from /usr/lib/libpangocairo-1.0.so.0
#10 pango_cairo_show_glyph_string
from /usr/lib/libpangocairo-1.0.so.0
#11 pango_renderer_draw_glyphs
from /usr/lib/libpango-1.0.so.0
#12 pango_cairo_show_layout_line
from /usr/lib/libpangocairo-1.0.so.0
#13 gdk_draw_layout_line
from /usr/lib/libgdk-x11-2.0.so.0
#14 pango_renderer_draw_glyphs
from /usr/lib/libpango-1.0.so.0
#15 pango_renderer_draw_layout_line
from /usr/lib/libpango-1.0.so.0
#16 pango_renderer_draw_layout
from /usr/lib/libpango-1.0.so.0
#17 gdk_draw_layout_with_colors
from /usr/lib/libgdk-x11-2.0.so.0
#18 gdk_draw_layout
from /usr/lib/libgdk-x11-2.0.so.0
#19 gnome_canvas_text_get_type
from /usr/lib/libgnomecanvas-2.so.0
#20 gnome_canvas_root
from /usr/lib/libgnomecanvas-2.so.0
#21 gnome_canvas_item_new
from /usr/lib/libgnomecanvas-2.so.0
#22 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#23 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#24 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#25 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#26 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#27 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#28 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#29 gnome_canvas_window_to_world
from /usr/lib/libgnomecanvas-2.so.0
#30 gnome_canvas_set_scroll_region
from /usr/lib/libgnomecanvas-2.so.0
#31 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#32 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#33 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#34 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#35 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#36 ??
#37 ??
#38 ??
#39 ??
#40 ??
#41 ??
#0 __waitpid_nocancel
from /lib/libpthread.so.0

Comment 1 Vincent Untz 2007-01-04 13:14:35 UTC

Moving to pango, since it looks like the bug is there.

Comment 2 André Klapper 2007-01-12 04:11:41 UTC

*** Bug 394445 has been marked as a duplicate of this bug. ***

Comment 3 Jason Brower 2007-05-12 03:28:37 UTC

I think I get something similar... it is after the first name zooms out...
(gnome-about:5792): Pango-WARNING **: shape engine failure, expect ugly output. the offending font is 'URW Gothic L Semi-Bold Not-Rotated 0'
Segmentation fault (core dumped)
skunkyjay@essence:~$ 
Looks like it can't handle the font very well.

Comment 4 Akhil Laddha 2010-06-22 08:55:48 UTC

This bug was reported against a GNOME version that is now not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use. By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME.

The current stable GNOME is 2.30.1.
Please check if the problem you reported here still occurs with a recent version of GNOME by reporting back which exact version you tested against

Thank you for reporting this bug and we are sorry it could not be fixed for your version.
Without feedback this report will be closed as INCOMPLETE in 6 weeks.

Comment 5 Tobias Mueller 2010-09-13 11:31:10 UTC

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!