Sat 05 Jan 2013 07:33:22 PM UTC, comment #8:
Ok, then closing this issue.
Thanks for quick and thorough follow-up and your work on MyPaint in macports!
|
Sat 05 Jan 2013 05:34:53 PM UTC, comment #7:
This is the pygobject commit that removed the "invalid flag value" error:
http://git.gnome.org/browse/pygobject/commit/gobject/pygflags.c?h=pygobject-2-28&id=eb0e179bff167303db1c20412f4bc9c8baa94582
This is the ticket that commit purportedly resolved:
https://bugzilla.gnome.org/show_bug.cgi?id=642607
|
Sat 05 Jan 2013 05:25:04 PM UTC, comment #6:
I can now confirm that the "invalid flag value" error comes from py-gobject. We were running py-gobject 2.26.0 in MacPorts. Updating to 2.28.6 fixes that error. I have requested py-gobject in MacPorts be updated: https://trac.macports.org/ticket/37538
At this point if I open MyPaint I still get "local variable 'modifiers' referenced before assignment". If I move ~/.mypaint aside and let it be recreated, there is no longer an error.
If I restore ~/.mypaint from my backups from before I started working on the MyPaint 1.1.0 update, and then open MyPaint with py-gobject 2.28.6 installed, MyPaint opens without error.
So I think I can conclude that encountering the "invalid flag value" error with py-gobject 2.26.0 corrupted the settings somehow. So as long as I wait until the update to py-gobject to 2.28.6 is published before I publish the MyPaint 1.1.0 update everything should be fine.
|
Sat 05 Jan 2013 12:55:43 PM UTC, comment #5:
Seems like a GTK/pyGTK issue to be, but maybe we can implement a workaround?
|
Fri 04 Jan 2013 03:24:14 PM UTC, comment #4:
Yes, it's pygtk 2.24.0.
|
Fri 04 Jan 2013 03:18:51 PM UTC, comment #3:
Also
directly if you could please - I think that's the zero in question.
|
Fri 04 Jan 2013 03:17:31 PM UTC, comment #2:
That's two errors, but the second is caused by the first.
For the original one, what version of PyGTK are you running? This should work fine with 2.24.0, and you should be able to do all of
without problems. Let me know if and where any of the >>>s fail :)
|
Wed 02 Jan 2013 06:54:47 PM UTC, comment #1:
Now the error has changed to:
|
Wed 02 Jan 2013 06:42:47 PM UTC, original submission:
Hello, I'm the maintainer of MyPaint in MacPorts. Having braved the build system and gotten MyPaint 1.1.0 to build and install, it runs, but displays this error every time I start it:
Clicking the "Details..." disclosure triangle produces this text:
|