You are not logged in.
Pages: 1
I recently setup a new workstation complete with GDM and Gnome. Unlike in the past where I have disabled Wayland because I had problems getting it to work, GDM/Gnome with Wayland worked out of the box on this new machine.
I use RXVT and load all its settings through an `.Xresources` file, which gets automatically loaded either via `.xinitrc` or `.Xsession` (using X). I am confused as to how this should (or maybe, should not) work in Wayland. In the new install, I know that if I call
xrdb ~/.Xresourcesbefore opening RXVT all my settings are loaded so I know the solution involves calling
xrdb ~/.Xresourcesat some point before opening RXVT (which can be accomplished in a number of ways I can think of). However, I am looking for what is considered standard practice for automatically calling xrdb in my new setup?
I have been searching through the internet and there have been several posts related to this topic. However, to me, I have not found a clear answer to my question. I am hoping someone will explain this to me and/or point to me to resources that makes this clear.
Last edited by mjellis1687 (2019-08-15 15:35:00)
Offline
As it became clear from your question, you need this: https://wiki.archlinux.org/index.php/GD … plications
Run ~ / .xinitrc as a session is standard practice
Offline
nb. that this is only going to work if something™ keeps the xwayland server process around (and in this case "beginning w/ the gnome session starup"), otherwise the rdb is lost w/ the termination of that server.
Online
Thanks for the link @assertion and the clarification @seth. So, if I am understanding correctly, assuming GDM runs ~/.xinitrc as a session, then, nothing is different between X and Wayland for my configuration.
Offline
For anyone stumbling onto this thread, it turns out the problem I was experiencing had little to do with my question. It seems that xwayland was crashing at some point, which would clearly caused the rdb to be lost as pointed out by seth. I did not immediately find this as xwayland was only throwing a warning in the journal that it had lost connection. After getting up to speed with the latest on Wayland, I decided to disable it in favor of X as (1) it was not clear to me how to resolve the xwayland problem and (2) I learned that Wayland still does not work with nvidia drivers. Thus, I am marking this thread solved.
Offline
Pages: 1