Bug 678510 - g_object_set_property: construct property "type" for object `Window' can't be set after construction
g_object_set_property: construct property "type" for object `Window' can't be...
Status: RESOLVED FIXED
Product: pygobject
Classification: Bindings
Component: introspection
3.2.x
Other Linux
: Normal minor
: ---
Assigned To: Nobody's working on this now (help wanted and appreciated)
Python bindings maintainers
:
Depends on:
Blocks:
  Show dependency tree
 
Reported: 2012-06-20 23:47 UTC by Serhiy Zahoriya
Modified: 2012-06-25 13:08 UTC (History)
1 user (show)

See Also:
GNOME target: ---
GNOME version: ---

Attachments
reproducer (354 bytes, text/plain)
2012-06-25 12:25 UTC, Martin Pitt 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Serhiy Zahoriya 2012-06-20 23:47:04 UTC 
This error is showed with the default Quickly application template on Ubuntu 12.04 and according to https://bugs.launchpad.net/pygobject/+bug/974729/comments/2 it can be fixed in /usr/lib/python2.7/dist-packages/gi/overrides/Gtk.py which belongs to the python-gi package which has pygobject as a source.
Comment 1 Martin Pitt 2012-06-21 03:57:23 UTC 
You need to give some more information about how to reproduce this. Please attach some example code which generates this error, or describe how to run the code you are running. https://launchpad.net/ubuntu-accomplishments does not show a PPA nor a branch, "bzr branch lp:ubuntu-accomplishments" does not work, and the package is not in Ubuntu Quantal.
Comment 2 Serhiy Zahoriya 2012-06-21 12:19:00 UTC 
Commands to reproduce on the current Ubuntu 12.04 installation:
sudo apt-get install quickly
quickly create ubuntu-application test
cd test/
quickly run
Comment 3 Martin Pitt 2012-06-25 12:25:22 UTC 
Created attachment 217190 [details]
reproducer

Thanks. Attaching standalone reproducer.

This happens when reading a subclassed Gtk.Window from a Gtk.Builder.
Comment 4 Martin Pitt 2012-06-25 13:08:24 UTC 
Fixed in master with a rather extensive test case.
Note You need to log in before you can comment on or make changes to this bug.