Bug 3947 - Crash: Assertion about cairo status failed
Summary: Crash: Assertion about cairo status failed
Status: RESOLVED INVALID
Alias: None
Product: cairo
Classification: Unclassified
Component: general (show other bugs)
Version: 0.9.3
Hardware: x86 (IA32) Linux (All)
: high critical
Assignee: Carl Worth
QA Contact: cairo-bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-02 06:35 UTC by Daniel Stone
Modified: 2006-08-18 14:19 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments

Description FreeDesktop Bugzilla Database Corruption Fix User 2005-08-02 06:35:58 UTC 
Evince just crashed for me with the following error. I cannot reproduce it though.

evince: cairo.c:86: _cairo_error: Assertion `status > CAIRO_STATUS_SUCCESS &&
status <= CAIRO_STATUS_FILE_NOT_FOUND' failed.
Comment 1 Carl Worth 2005-08-02 07:22:48 UTC 
This sounds similar to a bug found by our friends over at the ubuntu bugzilla:

https://bugzilla.ubuntu.com/show_bug.cgi?id=13073

Could you precisely state which version of cairo you were using? If from CVS,
what was the most recent commit message in cairo/ChangeLog)?
Comment 2 FreeDesktop Bugzilla Database Corruption Fix User 2005-08-02 07:41:14 UTC 
I'm using libcairo1-0.6.0-1mdk (mandriva cooker). I will try to rebuild evince
against the 0.6.0-devel headers, maybe that makes a difference.
Comment 3 Carl Worth 2005-08-02 08:13:49 UTC 
As referenced in the ubuntu bug #13073 above, there are fixes in the cairo
CVS tree after 0.6.0 that may fix this problem.

You mentioned you were having trouble reproducing the problem, but if you
can, and can see whether the bug goes away with the latest cairo from CVS
that would be very useful information.
Comment 4 Carl Worth 2005-08-22 17:15:03 UTC 
Move bugs against "cvs" version to "0.9.3" so we can remove the "cvs" version.
Comment 5 Behdad Esfahbod 2006-08-18 14:19:41 UTC 
Way too old to be relevant still.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.