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 749637 - No transparency in other window managers with compositor.
No transparency in other window managers with compositor.
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Backend: X11
3.17.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2015-05-20 14:36 UTC by Sebastián Calarco
Modified: 2018-04-15 00:15 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Sebastián Calarco 2015-05-20 14:36:42 UTC
There's no transparency in window managers like bspwm with compton. I looked at gtkwindow.c and I think it's because rgba is not enabled when the window manager doesn't support _GTK_FRAME_EXTENTS. This happens since 3.16.
Comment 1 Matthias Clasen 2015-05-21 01:52:23 UTC
you mean shadows and invisible borders with 'transparency' ? A screenshot of what you are seeing would be helpful
Comment 2 Sebastián Calarco 2015-05-21 14:41:26 UTC
Transparent parts in some themes doesn't work. I tried giving an alpha background to the .window-frame.solid-csd class in the theme without luck. The theme i tried is this https://github.com/horst3180/Arc-theme.
Comment 3 Matthias Clasen 2018-02-10 05:18:22 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 4 Matthias Clasen 2018-04-15 00:15:20 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