Open jgarvin opened 4 years ago
On my home desktop running 19.10, gsd-xsettings
starts normally, so I think this is probably some configuration issue or gnome bug instead of a systematic problem in gnome-session-xmonad or gnome's parser. Unfortunately I don't even know where to start debugging this :frowning:
In my experience, using alternative sessions like gnome-session-xmonad often triggers various gnome or ubuntu bugs that don't happen with the "standard" sessions. For example, at the moment my work laptop running 19.10 has some kind of problem where the desktop background is not drawn correctly if I switch between workspaces and the previous contents of the screen are retained instead. This is fixed by opening dconf-editor, and toggling desktop background boolean config twice (!!). So every time I log in on that computer, I open dconf-editor and do this magic trick...I've also had similar strange issues in the past on several machines, and nuking my home folder has usually helped if nothing else has worked.
If you want to debug this problem a bit more, try creating a new user, setting up your xmonad config appropriately in that user's home folder, and logging in. With a fresh home folder you might have different results. It's not really a solution, but might give us more info :smile:
I'm using gnome-session-xmonad on Ubuntu 19.10. My fonts looked much uglier than they do in the default Ubuntu session, so I did some digging. I found the various daemons runnning:
Notice that gsd-xsettings is missing. So I manually ran
/usr/lib/gnome-settings-daemon/gsd-xsettings
and immediately everything looked better. So then I checked the code checked in here and my local/usr/share/gnome-session/sessions/gnome-xmonad.session
, but they both contain the XSettings at the end:Maybe there's an off by 1 in the parser for this so the last entry doesn't startup? Happy to provide more details if you have commands to run.