Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1199553 (f22-kde-gtk3-csd) - kde-settings: gtk3 CSD issues
Summary: kde-settings: gtk3 CSD issues
Keywords:
Status: CLOSED RAWHIDE
Alias: f22-kde-gtk3-csd
Product: Fedora
Classification: Fedora
Component: kde-settings
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F22Blocker-kde
TreeView+ depends on / blocked
 
Reported: 2015-03-06 15:41 UTC by Rex Dieter
Modified: 2015-05-19 15:15 UTC (History)
10 users (show)

Fixed In Version: gtk3-3.15.11-1.fc22
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-05-19 15:15:38 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
gnotes on plasma5 with transparent (csd) border (78.64 KB, image/png)
2015-03-06 15:41 UTC, Rex Dieter 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 729721 0 None None None Never

Description Rex Dieter 2015-03-06 15:41:09 UTC 
Created attachment 998919 [details]
gnotes on plasma5 with transparent (csd) border

gtk3 apps (with client side decorataions, CSD) currently look a bit wierd on plasma5 (See attachment).

mgraesslin (kwin upstream) suggested some options: we can 

* disable the script the enforces win decorations
* we set a custom theme that sets shadow margins to 0

I asked Workstation WG, and they are ok with either option, though (obviously) prefer the first option.

Fwiw, there's a gnome upstream tracking bug on the topic,
https://bugzilla.gnome.org/show_bug.cgi?id=729721

but I'm not hopeful that it will be resolved any time soon.
Comment 1 Kevin Kofler 2015-03-07 00:39:57 UTC 
> * we set a custom theme that sets shadow margins to 0

That does not really solve the issue. It will remove the ugly margin between the 2 window decorations, but it will NOT fix the fact that there are 2 decorations to begin with, which IMHO is a blocker.

What we really need is for GTK+ to disable CSD under KDE Plasma entirely, something they have refused to do. Failing that, showing only the CSD is the only option we have.
Comment 2 Kevin Kofler 2015-03-07 00:50:41 UTC 
The sad thing is that there was actually a patch to disable CSD under non-GNOME:
https://bugzilla.gnome.org/show_bug.cgi?id=729721#c13
but it got reverted by:
https://git.gnome.org/browse/gtk+/commit/?id=fb9a6bb6d8d6b60b25c9b9853decbcea938f7863
supposedly to prevent showing double borders, but showing double borders is exactly what that "fix" results in!
Comment 3 Kevin Kofler 2015-03-07 00:55:06 UTC 
And the real cause of the double headers (i.e. https://bugzilla.gnome.org/show_bug.cgi?id=727414) was that even with CSD disabled, GTK+ draws a redundant title bar just in case the dialog wants to hide some controls in there (even when it doesn't, see the "Find file" example in the linked bug report).
Comment 4 Rex Dieter 2015-03-10 01:59:14 UTC 
Looks like the gtk3 put the check back after all,
https://git.gnome.org/browse/gtk+/commit/?id=5ced234144ce63decbf5afc8a3517290b9027018

So once that gets into gtk3 packaging and we can test/verify, we can probably close this.
Comment 5 Rex Dieter 2015-03-12 17:35:03 UTC 
https://admin.fedoraproject.org/updates/gtk3-3.15.11-1.fc22

tests good for me, closing.
Comment 6 Rex Dieter 2015-03-12 17:38:19 UTC 
I take it back, the transparent borders are gone, but we're still seeing double win decorations.
Comment 7 Rex Dieter 2015-03-12 18:06:27 UTC 
an Kwin's script "Enforces Window Decorations on GTK+ Window" has no effect, I see double decorations whether it's enabled or not.

I suspect it keyed off the CSD shadow stuff that was recently disabled in gtk3.
Note You need to log in before you can comment on or make changes to this bug.