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 751443 - resource_path value cleared in gtk_image_set_from_resource
resource_path value cleared in gtk_image_set_from_resource
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Widget: Other
3.16.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2015-06-24 13:59 UTC by cedlemo
Modified: 2015-06-25 10:52 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
gtk_image_set_from_resource patch (701 bytes, patch)
2015-06-24 13:59 UTC, cedlemo
committed Details | Review

Description cedlemo 2015-06-24 13:59:29 UTC
Created attachment 306003 [details] [review]
gtk_image_set_from_resource patch

In the gtk3 module of the project Ruby-gnome2, we have observed that when a Gtk::Image object was created from a resource, the resource_path was always NULL.

Here is a link to the github pull request that relates the issue:

https://github.com/ruby-gnome2/ruby-gnome2/pull/461

In the gtk3_image_set_from_resource, the resource_path is set with :

    priv->resource_path = g_strdup (resource_path);

Then gtk_image_set_from_pixbuf or gtk_image_set_from_animation are called. Those two functions call gtk_image_clear() which call gtk_image_reset() which clears priv->resource_path.


The owner of the ruby-gnome2 repository provided a git patch that I have attached to this bug request.

Regards
Comment 1 Matthias Clasen 2015-06-25 10:52:50 UTC
Thanks for the patch