Forum Replies Created
-
Posts
-
This issue has been solved by creating a new account for the affected user. The issue seemed isolated to that user’s old account.
The journalctl log (pasted below) seemed identical to the old one.
Under that specific user’s home folder, we didn’t find any file like ~/.gnome, ~/.gnome2, ~/.nautilus, ~/.gconf, etc. Here are the folders under ~/.config/
- dconf
- enchant
- eog
- evolution
- gedit
- goa-1.0
- gtk-3.0
- ibus
- libreoffice
- matplotlib
- nautilus
- pulse
- update-notifier
- user-dirs.dirs
- user-dirs.locale
- yelp
Should we remove any of these folders to clean up the gnome config?
New journalctl log:
Nov 23 17:02:31 a6k dbus-daemon[2241824]: [session uid=1004 pid=2241821] AppArmor D-Bus mediation is enabled
Nov 23 17:02:33 a6k gnome-session[2241834]: gnome-session-check-accelerated: GL Helper exited with code 512
Nov 23 17:02:33 a6k gnome-session[2241834]: gnome-session-check-accelerated: GLES Helper exited with code 512
Nov 23 17:02:33 a6k gnome-session[2241692]: gnome-session-binary[2241692]: WARNING: Falling back to non-systemd startup procedure due to error: Could not connect: >
Nov 23 17:02:33 a6k gnome-session[2241692]: gnome-session-binary[2241692]: WARNING: Could not make bus activated clients aware of QT_IM_MODULE=ibus environment var>
Nov 23 17:02:33 a6k gnome-session[2241692]: gnome-session-binary[2241692]: WARNING: Could not make bus activated clients aware of XMODIFIERS=@im=ibus environment v>
Nov 23 17:02:33 a6k gnome-session[2241692]: gnome-session-binary[2241692]: WARNING: Could not make bus activated clients aware of GNOME_DESKTOP_SESSION_ID=this-is->
Nov 23 17:02:33 a6k gnome-session[2241692]: gnome-session-binary[2241692]: WARNING: Could not make bus activated clients aware of XDG_MENU_PREFIX=gnome- environmen>
Nov 23 17:02:33 a6k gnome-session-binary[2241692]: WARNING: Falling back to non-systemd startup procedure due to error: Could not connect: Connection refused
Nov 23 17:02:33 a6k gnome-session-binary[2241692]: WARNING: Could not make bus activated clients aware of QT_IM_MODULE=ibus environment variable: Could not connect>
Nov 23 17:02:33 a6k gnome-session-binary[2241692]: WARNING: Could not make bus activated clients aware of XMODIFIERS=@im=ibus environment variable: Could not conne>
Nov 23 17:02:33 a6k gnome-session-binary[2241692]: WARNING: Could not make bus activated clients aware of GNOME_DESKTOP_SESSION_ID=this-is-deprecated environment v>
Nov 23 17:02:33 a6k gnome-session-binary[2241692]: WARNING: Could not make bus activated clients aware of XDG_MENU_PREFIX=gnome- environment variable: Could not co>
Nov 23 17:02:33 a6k gnome-session[2241692]: gnome-session-binary[2241692]: WARNING: Lost name on bus: org.gnome.SessionManager
Nov 23 17:02:33 a6k gnome-session[2241692]: gnome-session-binary[2241692]: CRITICAL: We failed, but the fail whale is dead. Sorry….
Nov 23 17:02:33 a6k gnome-session-binary[2241692]: WARNING: Lost name on bus: org.gnome.SessionManager
Nov 23 17:02:33 a6k gnome-session-binary[2241692]: CRITICAL: We failed, but the fail whale is dead. Sorry….
Thanks for the advice. Does the NX server need to be restarted for this change to take effect? We made the change in node.cfg but haven’t restarted the NX server due to running jobs of other users, the issue seems to persist without the restart.
Also, this change seems universal while the above issue is user specific: from the same computer/NX client, the issue can be reproduced using one user’s username/passwd, while other users can launch NX session without any issue.
Here is the journalctl log corresponding to the issue:
Nov 10 11:00:43 a6k dbus-daemon[2099323]: [session uid=1004 pid=2099321] AppArmor D-Bus mediation is enabled
Nov 10 11:00:45 a6k gnome-session[2099384]: gnome-session-check-accelerated: GL Helper exited with code 512
Nov 10 11:00:45 a6k gnome-session[2099384]: gnome-session-check-accelerated: GLES Helper exited with code 512
Nov 10 11:00:45 a6k gnome-session[2099239]: gnome-session-binary[2099239]: WARNING: Falling back to non-systemd startup procedure due to error: Could not connect: Co>
Nov 10 11:00:45 a6k gnome-session-binary[2099239]: WARNING: Falling back to non-systemd startup procedure due to error: Could not connect: Connection refused
Nov 10 11:00:45 a6k gnome-session[2099239]: gnome-session-binary[2099239]: WARNING: Could not make bus activated clients aware of QT_IM_MODULE=ibus environment varia>
Nov 10 11:00:45 a6k gnome-session[2099239]: gnome-session-binary[2099239]: WARNING: Could not make bus activated clients aware of XMODIFIERS=@im=ibus environment var>
Nov 10 11:00:45 a6k gnome-session[2099239]: gnome-session-binary[2099239]: WARNING: Could not make bus activated clients aware of GNOME_DESKTOP_SESSION_ID=this-is-de>
Nov 10 11:00:45 a6k gnome-session[2099239]: gnome-session-binary[2099239]: WARNING: Could not make bus activated clients aware of XDG_MENU_PREFIX=gnome- environment >
Nov 10 11:00:45 a6k gnome-session-binary[2099239]: WARNING: Could not make bus activated clients aware of QT_IM_MODULE=ibus environment variable: Could not connect: >
Nov 10 11:00:45 a6k gnome-session-binary[2099239]: WARNING: Could not make bus activated clients aware of XMODIFIERS=@im=ibus environment variable: Could not connect>
Nov 10 11:00:45 a6k gnome-session-binary[2099239]: WARNING: Could not make bus activated clients aware of GNOME_DESKTOP_SESSION_ID=this-is-deprecated environment var>
Nov 10 11:00:45 a6k gnome-session-binary[2099239]: WARNING: Could not make bus activated clients aware of XDG_MENU_PREFIX=gnome- environment variable: Could not conn>
Nov 10 11:00:45 a6k gnome-session[2099239]: gnome-session-binary[2099239]: WARNING: Lost name on bus: org.gnome.SessionManager
Nov 10 11:00:45 a6k gnome-session[2099239]: gnome-session-binary[2099239]: CRITICAL: We failed, but the fail whale is dead. Sorry….
Nov 10 11:00:45 a6k gnome-session-binary[2099239]: WARNING: Lost name on bus: org.gnome.SessionManager
Nov 10 11:00:45 a6k gnome-session-binary[2099239]: CRITICAL: We failed, but the fail whale is dead. Sorry….