The same issue has been reproduced in Jammy (22.04.1). The following patch for 55gnome-session_gnomerc is a workaround that fixes this issue.
5c5 < if [ "$BASESTARTUP" = x-session-manager ]; then --- > if [ "$BASESTARTUP" = x-session-manager ] || [ "$BASESTARTUP" = env ]; then -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1895781 Title: ~/.gnomerc is not loaded anymore at startup Status in gnome-session package in Ubuntu: Confirmed Bug description: I have clean-installed Focal and configured to run X.org server instead of Wayland, and found that the ~/.gnomerc is not loaded anymore. In /etc/X11/Xsession.d/55gnome-session_gnomerc, it tries to load ~/.gnomerc but it fails because of the change of the gnome-session's startup process. Let's see this part of the 55gnome-session_gnomerc: BASESTARTUP=${STARTUP%% *} BASESTARTUP=${BASESTARTUP##*/} if [ "$BASESTARTUP" = x-session-manager ]; then BASESTARTUP=$(basename $(readlink /etc/alternatives/x-session-manager)) fi case "$BASESTARTUP" in gnome-session*) GNOMERC=$HOME/.gnomerc if [ -r "$GNOMERC" ]; then . "$GNOMERC" fi In Bionic, at the time of launching 55gnome-session_gnomerc, the value of $STARTUP is "gnome-session" and it works properly. In Focal, however, the value of $STARTUP is "env GNOME_SHELL_SESSION_MODE=ubuntu /usr/bin/gnome-session --systemd --session=ubuntu", and $BASESTARTUP became "env", then it skips loading ~/.gnomerc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1895781/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
