After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 695394 - Frequent but inconsistent occurrence of "TypeError: Expected GdkPixbuf.Pixbuf, but got gi.repository.GdkPixbuf.Pixbuf"
Frequent but inconsistent occurrence of "TypeError: Expected GdkPixbuf.Pixbuf...
Status: RESOLVED DUPLICATE of bug 693839
Product: pygobject
Classification: Bindings
Component: introspection
3.4.x
Other Linux
: Normal normal
: ---
Assigned To: Nobody's working on this now (help wanted and appreciated)
Python bindings maintainers
Depends on:
Blocks:
 
 
Reported: 2013-03-07 20:08 UTC by EvilGnome
Modified: 2013-03-14 13:21 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
jpeg which may play a role in raising the exception in question (98.80 KB, application/octet-stream)
2013-03-07 20:08 UTC, EvilGnome
Details

Description EvilGnome 2013-03-07 20:08:59 UTC
Created attachment 238339 [details]
jpeg which may play a role in raising the exception in question

First, an image is downloaded and saved as `filename`.

Then, a pixbuf is created with something like:
    pixbuf = GdkPixbuf.Pixbuf.new_from_file_at_size(filename, min_size, min_size)

Then, a GtkImage called `widget` is set using:
    widget.set_from_pixbuf(pixbuf)

Then, not in every case (even with the same picture data), but in many cases, a confusing exception is raised:
    TypeError: Expected GdkPixbuf.Pixbuf, but got gi.repository.GdkPixbuf.Pixbuf

Here is code that leads to this error (see lines 487-531):
http://pastebin.com/Cm1w9txS
[full project at https://github.com/AndydeCleyre/chipmunk-radio]


Arch Linux x86_64
python 3.3.0
python-gobject 3.4.2
Comment 1 EvilGnome 2013-03-14 13:21:17 UTC
I have been testing for this bug with python-gobject 3.7.91.1 this past week, and so far it has not presented itself. Looking at the news between versions leads me to believe this bug report is a duplicate of #693839 ( https://bugzilla.gnome.org/show_bug.cgi?id=693839 ), which was fixed in python-gobject 3.7.90.

*** This bug has been marked as a duplicate of bug 693839 ***