Create a workaround for Evolution backend and PyGTK
Bug #931539 reported by
Izidor Matušov
This bug affects 4 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| GTG |
Invalid
|
Medium
|
Unassigned | ||
Bug Description
Evolution library and current PyGTK can't play well together. See https:/
Revision history for this message
| Izidor Matušov (izidor) wrote | #1 |
| Changed in gtg: | |
| assignee: | Izidor Matušov (izidor) → nobody |
| milestone: | 0.3 → none |
| status: | Confirmed → Invalid |
To post a comment you must log in.
The easiest solution would be to not ship Evolution backend with GTG 0.3 neither and solve this after porting GTG to GTK3. According to my reproducer in that bug, there should be no problem with it afterwards.