-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
pango breaking pygtk and other packages #6014
Comments
atk also seems to have problems, glib2 and gobject2 are now private objects in the pkgconfig scripts causing more grief with pygtk. Atleast i can fix atk to work by hand modifying atk.pc but that might not fly well with everybody.
should be
|
yeah, there is a fix upstream. I'll have a look. |
See #6021. Regarding pango, we don't ship pango 1.44 nor cairo > 1.16, so I don't think we are affected by all of this. |
well then it must be the atk package ? cause i could not build pygtk unless i modified the package config files like above. pango seems to be vesion 1.43 and cairo 1.16 so yeah that seems to be ok. |
Ah you allready fixed it :) no problems then. |
We are also stuck with pango < 1.44 but not because of font loading but because of broken font rendering. |
hmm only problem im noticing so far is that gtk3's viewport seems to be off by a bit, oh wait i see now pango crashes when trying to render fonts ouch :S |
yikes |
So after finally updating to gcc-9.2.0 i decided to rebuild most packages, but theres a snag...
seems recent pango removed bitmap support and private headers causing applications such as pygtk to fail building. This in turn breaks gimp as it relies on pygtk and inkscape as well.
Most distros have reverted to pango-1.42 because of this, since it also causes T1 font problems.
pygobject was intended to replace pygtk at some point but there has been little to any development
in that regard, so waiting for them to fix it might take longer than you might want to wait.
So i suggest downgrading pango to 1.42 and possibly cairo to in the meantime.
The text was updated successfully, but these errors were encountered: