Bug 1382957

Summary: pixbuf_get_from_window fails due to assertion in cario-surface.cc
Product: [Fedora] Fedora Reporter: Wilfried Philips <Wilfried.Philips>
Component: cairoAssignee: Benjamin Otte <otte>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 26CC: eriksohns, otte
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-29 11:38:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
test program demonstrating the bug none

Description Wilfried Philips 2016-10-08 18:01:22 UTC
Created attachment 1208402 [details]
test program demonstrating the bug

Description of problem:
Creating a screenshot from a GTP3 window in python crashes
with an assertion:

python: cairo-surface.c:1653: cairo_surface_mark_dirty_rectangle: Assertion `! _cairo_surface_has_mime_data (surface)' failed.


Version-Release number of selected component (if applicable):
cairo-1.14.6-2.fc24.x86_64.rpm



How reproducible:

Always

Steps to Reproduce:
 run the attached mini-program. It calls pixbuf_get_from_window
without using returned data. At this point the program should
show a window, but it crashes.


Actual results:

crash

Expected results:
window on screen

Additional info:

I have recompiled 
cairo-1.14.6-2.fc24.x86_64.rpm from soure after commenting out
assert (! _cairo_surface_has_mime_data (surface));
on line 1653.
With this change the program runs fine. 

Perhaps the assertion is not needed, or perhaps 
pixbuf_get_from_window calls cairo_surface_mark_dirty_rectangle
without calling cairo_surface_flush() as the comment near the 
assertion suggests

Comment 1 Fedora End Of Life 2017-07-25 23:24:07 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 2 Wilfried Philips 2017-07-26 10:00:37 UTC
Bug still exists in fedora 26

Comment 3 Fedora End Of Life 2018-05-03 08:25:57 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2018-05-29 11:38:51 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 5 eriksohns 2019-01-04 12:58:39 UTC
Bug still exists in fedora 29