New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

_cairo_surface_begin_modification: Assertion `! surface->finished' failed. #28

Closed
kirbyfan64 opened this Issue May 6, 2014 · 4 comments

Comments

Projects
None yet
2 participants
@kirbyfan64
Copy link
Contributor

kirbyfan64 commented May 6, 2014

I'm running the latest version of Howl from Git. When I try to open a .hpp file, I get this:

howl: /build/buildd/cairo-1.10.2/src/cairo-surface.c:385: _cairo_surface_begin_modification: Assertion `! surface->finished' failed.
Aborted (core dumped)

All other files(including .cpp files and .h files) are perfectly file.

@nilnor

This comment has been minimized.

Copy link
Contributor

nilnor commented May 6, 2014

I'm unable to reproduce this here. Do you have an example of a .hpp file where this happens? Also, what Gtk version are you on?

@kirbyfan64

This comment has been minimized.

Copy link
Contributor

kirbyfan64 commented May 6, 2014

Huh...weird. It seems to happen on only specific files. For example, it happens on Howl's makefile and download helper script, but not on main.c. I have no idea what's going on. I'm on GTK+ version 3.4.2.

@nilnor

This comment has been minimized.

Copy link
Contributor

nilnor commented May 6, 2014

I've updated a patch for Scintilla that affects Gtk 3. So when you have the time, could you try pulling the latest from master (1e5c39f), and issue:

cd <howl-dir>/src
rm -rf deps/scintilla341/
make

I'm logging off for the day, but I'm crossing my fingers that this will fix it for you - let me know how it goes!

@kirbyfan64

This comment has been minimized.

Copy link
Contributor

kirbyfan64 commented May 6, 2014

It works! Thank you!

@kirbyfan64 kirbyfan64 closed this May 6, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment