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 723669 - xsettings: export decoration layout from mutter
xsettings: export decoration layout from mutter
Status: RESOLVED OBSOLETE
Product: gnome-settings-daemon
Classification: Core
Component: xsettings
unspecified
Other All
: High critical
: ---
Assigned To: gnome-settings-daemon-maint
gnome-settings-daemon-maint
Depends on:
Blocks:
 
 
Reported: 2014-02-05 12:41 UTC by Giovanni Campagna
Modified: 2019-03-20 11:15 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
xsettings: export decoration layout from mutter (4.97 KB, patch)
2014-02-05 12:41 UTC, Giovanni Campagna 		none Details | Review

Description Giovanni Campagna 2014-02-05 12:41:34 UTC 
Depends on bug 723665 for mutter to export the property in the
first place.

Using a property instead of watching GSettings directly is
needed because normal and classic modes use different schemas
and keys (and an X window property is the easiest form of IPC)
Comment 1 Giovanni Campagna 2014-02-05 12:41:36 UTC 
Created attachment 268163 [details] [review]
xsettings: export decoration layout from mutter

Read and watch a root window property with the decoration layout.
This allows the WM to have multiple sources for configuration,
and makes sure that at all times the CSD layout is consistent
with server side decorations.
Comment 2 Bastien Nocera 2014-02-05 13:34:41 UTC 
Why can't GTK+ read this from the Atom directly? How will this work for Wayland?

I don't really understand how it all fits together...
Comment 3 Giovanni Campagna 2014-02-05 14:33:27 UTC 
How will this work for wayland is a good question - I guess like the rest of GtkSettings, for which we don't have an answer yet.
(Currently Gtk reads GNOME GSettings directly, but certainly that's not the proper solution)

Why can't GTK read this Atom? I believe because it's a lot simpler for them to reuse the existing XSettings machinery.
Also, GTK+ does not normally select PropertyChangeMask on the root window (because otherwise it would be woken up by all window switches), so XSettings is the only way to get proper notifications.
Comment 4 GNOME Infrastructure Team 2019-03-20 11:15:44 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/242.