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 769644 - wayland session does not process /etc/X11/Xresources ~/.Xresources
wayland session does not process /etc/X11/Xresources ~/.Xresources
Status: RESOLVED OBSOLETE
Product: gnome-session
Classification: Core
Component: gnome-session
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Session Maintainers
Session Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-08-08 19:04 UTC by Hans de Goede
Modified: 2021-06-14 18:22 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Hans de Goede 2016-08-08 19:04:40 UTC
As discussed in bug 36660 gnome-session should do the equivalent of:

xrdb -merge /etc/X11/Xresources
xrdb -merge ~/.Xresources

After starting Xwayland so that X11 apps started under a Wayland gnome3 session honor the settings from those files.
Comment 1 Ray Strode [halfline] 2016-08-08 21:47:18 UTC
The more I think about it, the more I think that Xwayland should do it.  Do you have any objections to that?

What about you Olivier ?
Comment 2 Hans de Goede 2016-08-09 06:23:17 UTC
Having Xwayland do this would be fine with me, but that is more Olivier's call to make then mine.
Comment 3 Olivier Fourdan 2016-08-09 07:03:11 UTC
Xwayland is an X server, as such I don't see it loading the client resources database itself nor rely on xrdb, I don't see any other DDX doing that.

Historically, this was done by gnome-settings-daemon but the xrdb plug-in was dropped circa GNOME 2.91.

I am probably missing some background here (can't find the bug referenced in comment 0 neither in bugzilla.gnome.org nor bugs.freedesktop.org), like how does this work in regular X GNOME session, and why do we need to do any different in Wayland session (apart maybe that Xwayland is started by mutter/gnome-shell) 

What are the pros and cons of having it started from the one of the X clients such as gnome-session or gnome-settings-daemon?
Comment 4 Hans de Goede 2016-08-09 09:36:29 UTC
Sorry, the bug in comment 0 should have been bug 736660.
Comment 5 Ray Strode [halfline] 2016-08-09 19:03:04 UTC
(In reply to Olivier Fourdan from comment #3)
> Xwayland is an X server, as such I don't see it loading the client resources
> database itself nor rely on xrdb, I don't see any other DDX doing that.
Well, it's a local X server though. You aren't going to do Xwayland -query or something, so it's a bit of a special case.
Comment 6 Olivier Fourdan 2016-08-10 08:08:22 UTC
(In reply to Ray Strode [halfline] from comment #5)
> Well, it's a local X server though. You aren't going to do Xwayland -query
> or something, so it's a bit of a special case.

Sure it's a bit of a special case, but still, I am not convinced this is up to Xwayland to load the xrdb.

Besides, other desktops such as KDE may load the xrdb database on their own (I haven't really checked thoroughly, but startkde from plasma-workspace spawns xrdb apparently).

Maybe we could think of an alternative, like using a wrapper script or launcher program similar to what xinit does?

 - Write an Xwayland init/wrapper script that takes care or running the requested X clients at startup
 - Make the command to run Xwayland configurable in mutter/gnome-shell (as it is in weston for example).
Comment 7 Ray Strode [halfline] 2016-08-10 15:24:42 UTC
running a wrapper is fine with me, but why would it be configurable? Wouldn't mutter just always runs the wrapper ?
Comment 8 André Klapper 2021-06-14 18:22:29 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version of gnome-session, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/gnome-session/-/issues/

Thank you for your understanding and your help.