GdkScreen is not valid at the time when create_engine() is called
Bug #993315 reported by
klonuo
This bug affects 4 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Unity |
Confirmed
|
Undecided
|
Unassigned | ||
| unity (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
Developer of oxygen-gtk theme engine, asked me to link this bug here
More info: https:/
Revision history for this message
| Hugo Pereira Da Costa (hugo-pereira) wrote | #1 |
| Changed in unity: | |
| status: | New → Confirmed |
| Changed in unity (Ubuntu): | |
| status: | New → Confirmed |
To post a comment you must log in.
Bottom line is: Oxygen-gtk3 needs to perform some initialization at the create_engine() stage, which in turns, requires GdkScreen (and GtkSettings, accessed via gtk_settings_
It is apparently not the case when running gtk3 applications under unity (same applications work well under other DEs, with same version of oxygen-gtk3, and gtk+-3.0)
Asking the gtk dev on IRC, we got told that GdkScreen should indeed be valid at that stage. Why it is not, for Unity, I have no idea, and maybe you folks know better.
Kindly,
Hugo (Oxygen dev)