Trying to use ./Xresources to change options of xterm
does not work under Gnome Wayland. Example:
[mfabian@Fedora-Live-Workstation-x86_64-2 ~]$ cat ~/.Xresources
[mfabian@Fedora-Live-Workstation-x86_64-2 ~]$ xrdb -load ~/.Xresources
[mfabian@Fedora-Live-Workstation-x86_64-2 ~]$ xterm
But xterm shows up with default white background, not green.
Under a non-Wayland Gnome session, the above works fine,
xterm has a green background then.
Any comment on this? It's a serious drawback.
(In reply to Stefan Assmann from comment #1)
> Any comment on this? It's a serious drawback.
This bug is not filed against the right component, Wayland libraries are not responsible for this, and xterm uses Xwayland anyway, it's not been ported to Wayland (and I doubt it will ever be).
Moving to gnome-session, I guess it would need to load the ~/.Xresources file with xrdb at startup with Wayland.
Also, please note that I reckon you have a typo in your example in comment #0 it's either "XTerm" or "xterm" (either class or instance)) for the Xresources file, not "Xterm" (ie your example does not work even in a plain X session).
And with the correct syntax, "xrdb -load ~/.Xresources" works fine in Wayland/XWayland as well.
thanks for taking a look at this. We weren't sure what exactly is the problem, but had to choose a component.
I can confirm that after manually running "xrdb -load ~/.Xresources" xterm behaves as expected again.
(In reply to Olivier Fourdan from comment #3)
> Also, please note that I reckon you have a typo in your example in comment
> #0 it's either "XTerm" or "xterm" (either class or instance)) for the
> Xresources file, not "Xterm" (ie your example does not work even in a plain
> X session).
> And with the correct syntax, "xrdb -load ~/.Xresources" works fine in
> Wayland/XWayland as well.
You are right about the typo! I was pretty sure I had tested this and
saw "xrdb -load ~/.Xresources" work on Gnome non-Wayland and not work
on Gnome Wayland. But when I tested again now, I found that it does
not work on either Gnome Wayland or Gnome non-Wayland with the
spelling "Xterm" but works on both with the spelling "XTerm", just
like you write.
I wonder how I could make that mistake during testing...
Anyway, that seems to make the problem far less serious because making
gnome-session load .Xresources should be fairly easy, I guess.
a long, long time ago we ran xrdb at startup, and at the time it was actually one of the main things that slowed down the login process. It was at the top of the login profile, because it runs a full blown c preprocessor or something. Anyway, we're not likely to add that back. Users, of course, can make it run at start up
Ray, you're saying this was a long time ago. Could we check if this is still the case before abandoning the idea? I'm only seeing minimal delays here.
sassmann@t530:~ > time xrdb -load ~/.Xresources
Same for me:
$ cat ~/.Xresources
$ time xrdb -merge ~/.Xresources
Timings with -load instead of -merge are similarly low.
That old reason for not loading the startup files is not valid *for me* as of now.