Trouble with mate-session, "Could not make bus activated clients aware..."

48 views
Skip to first unread message

qwofford

unread,
May 4, 2018, 12:36:21 PM5/4/18
to TurboVNC User Discussion/Support
Hello,

Note: Server is Centos 7.

I've been starting my Xvnc server as a non-privileged user in the following way: "TVNC_WM=mate-session /opt/TurboVNC/bin/vncserver". For a while, this was enough to allow me to connect via TurboVNC Viewer. Recently however, when I connect to this server, I have been getting an error from the VNC Viewer GUI:

"Could not connect to session bus: Failed to connect to socket /tmp/dbus-<unique string>: Connection refused"

Followed by another popup in TurboVNC Viewer:

"Could not acquire name on session bus"

I don't see any errors in the appropriate ~/.vnc/*.log files, I do see errors in /var/log/messages:
May  4 10:22:53 cn9999 mate-session[1556]: WARNING: Could not make bus activated clients aware of XDG_CURRENT_DESKTOP=MATE environment variable: Could not connect: Connection refused
May  4 10:22:53 cn9999 mate-session[1556]: WARNING: Could not make bus activated clients aware of DISPLAY=:1 environment variable: Could not connect: Connection refused
May  4 10:22:53 cn9999 mate-session[1556]: WARNING: Could not make bus activated clients aware of MATE_DESKTOP_SESSION_ID=this-is-deprecated environment variable: Could not connect: Connection refused
May  4 10:22:53 cn9999 mate-session[1556]: dconf-WARNING: failed to commit changes to dconf: Could not connect: Connection refused
May  4 10:22:53 cn9999 mate-session[1556]: WARNING: Could not make bus activated clients aware of SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/1556,unix/unix:/tmp/.ICE-unix/1556 environment variable: Could not connect: Connection refused


When I start the VNC server in the same way as root, I'm able to start a mate session and work with a desktop.

qwofford

unread,
May 4, 2018, 3:59:50 PM5/4/18
to TurboVNC User Discussion/Support
Additional relevant logs from ~/.vnc/*.log, not sure how I missed these before:

error: Error spawning command line 'dbus-launch --autolaunch=c5f447e6a90c4553a11475057c07e6ae --binary-syntax --close-stderr': Child process exited with code 1


Usage:
  dconf write KEY VALUE


Write a new value to a key


Arguments:
  KEY         A key path
(starting, but not ending with '/')
  VALUE      
The value to write (in GVariant format)


mate
-session[2483]: WARNING: Could not make bus activated clients aware of XDG_CURRENT_DESKTOP=MATE environment variable: Could not connect: Connection refused
mate
-session[2483]: WARNING: Could not make bus activated clients aware of DISPLAY=:1 environment variable: Could not connect: Connection refused
mate
-session[2483]: WARNING: Could not make bus activated clients aware of MATE_DESKTOP_SESSION_ID=this-is-deprecated environment variable: Could not connect: Connection refused
mate
-session[2483]: dconf-WARNING: failed to commit changes to dconf: Could not connect: Connection refused
generating cookie
with syscall
generating cookie
with syscall
generating cookie
with syscall
generating cookie
with syscall
mate
-session[2483]: WARNING: Could not make bus activated clients aware of SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/2483,unix/unix:/tmp/.ICE-unix/2483 environment variable: Could not connect: Connection refused
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
XIO
:  fatal IO error 11 (Resource temporarily unavailable) on X server ":1"
      after
14 requests (14 known processed) with 0 events remaining.
Gdk-Message: mate-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.

qwofford

unread,
May 7, 2018, 1:17:23 PM5/7/18
to TurboVNC User Discussion/Support
Please disregard! Anaconda had taken over some dbus libraries. Removing anaconda from my PATH resolved the issue.

DRC

unread,
May 7, 2018, 1:18:31 PM5/7/18
to turbovn...@googlegroups.com
Glad to hear. My favorite problems are the ones that solve themselves. :)
Reply all
Reply to author
Forward
0 new messages