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 690560 - Regression: GtkSocket draws background when container window becomes inactive
Regression: GtkSocket draws background when container window becomes inactive
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Themes
3.13.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2012-12-20 15:05 UTC by kdekorte
Modified: 2018-04-15 00:26 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description kdekorte 2012-12-20 15:05:02 UTC 
In version of GTK3 prior to 3.6, when the containing window of a GtkSocket became inactive the GtkSocket was not cleared. In 3.6 this appears to be happening. I have added the following to my code

GdkRGBA color;

color.red = 1.0;
color.alpha = 0.25;
gdk_window_set_background_rgba (gtk_widget_get_window(player->socket), &color);
gdk_window_set_background_pattern (gtk_widget_get_window (player->socket), NULL);

And this color overwrites the contents of my GtkSocket.And the contents are not seen under the color.

If there is a new way in gtk 3.6 to not have the socket overwrite the contents of the window, that is fine, but I could not find it in the documentation.
Comment 1 kdekorte 2012-12-20 16:48:28 UTC 
Note that this problem happens with the adwaita theme, but not the high contrast theme.
Comment 2 kdekorte 2012-12-20 18:11:46 UTC 
Tested several themes and Adwaita is the only one that exhibits this issue. The theme should not redraw the background of the GtkSocket widget when the window becomes insensitive.
Comment 3 Jakub Steiner 2014-07-01 14:06:00 UTC 
Would you be so kind and provide a test case (app) where this occurs?
Comment 4 Matthias Clasen 2018-02-10 05:21:42 UTC 
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
Comment 5 Matthias Clasen 2018-04-15 00:26:07 UTC 
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla.

If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab:

https://gitlab.gnome.org/GNOME/gtk/issues/new