Could not acquire name on session bus - SOLVED

Not ThinLinc
, ,
1

I’m running Ubuntu 18.04 with ThinLinc 4.12.1-6733_amd64. When I try to connect to it using the MATE Desktop, I get “Could not acquire name on session bus”. Are there any workarounds for this?

2

Answering my own question:

In the Linux guest machine, edit:

/etc/X11/Xsession.d/80mate-environment

Add:

unset DBUS_SESSION_BUS_ADDRESS

before the closing “fi”

Restart guest.

It seems to work for me, and does not seem to have any ill effects.

2 Likes
3

@dormitionskete do you know if you had a local MATE session running when this problem occurred?

4

No, I did not have a local MATE session running.

I’ve had this problem with Ubuntu MATE 16.04, 18.04 and 20.04, using various different versions of ThinLinc. I just never took the time to investigate it before. It seems to be related to a similar bug in TightVNC and some other flavors of VNC. I believe ThinLinc uses some sort of VNC in their implementation.

Doing a search on the internet for the error message I posted yielded several pages, all with similar suggestions to fix it. It was primarily a matter of locating the correct file to modify.

It’d be nice if ThinLinc would find a way to address this without us having to modify our guest systems; but I’m just happy to have ThinLinc for free limited use !!!

Have a great day!

5

I am running

  • Debian 10 / buster
  • ThinLinc 4.12.0 build 6517

I have this problem "could not acquire name on session bus”.
Updated /etc/X11/Xsession.d/99mate-environment with
“unset DBUS_SESSION_BUS_ADDRESS” , but the problem remains.

*Does any one have any other suggestion how to fix this problem?

6

Hello @ola4711

Make sure you’re not logged in locally with the same user (in the graphical console),
Furthermore, your version of ThinLinc is a bit dated, the current version is 4.14.0

Kind regards,
Martin

7

Hello

Thanks for your answer Martin.
I feel like a newbie on this, but this is as I understand my setup:

I am running

  • Win10 Enterprise (client), using Thinlinc 4.14.0.0 build 2324
  • Debian 10 / buster (server), using ThinLinc 4.12.0 build 6517

Is this setup OK or must something be changed??

  • Server side: User newer ThinkLinc version?? Where do I find this?

Kind regards,
Ola

8

That setup is ok.

ThinLinc server can be downloaded from https://www.cendio.com/thinlinc/download/registration

Regards,
Martin

9

Good that the setup is OK.
This should work then, but I still have this problem, so something is wrong.

Is there a newer/better version available on server side?
Maybe my problem will be solved with newer version…

Regards,
Ola

10

The only way I was able to reproduce your issue, resulting in this screenshot from ThinLinc client, was if I had a local GUI session already running:

Screenshot from 2022-12-22 13-32-41
Screenshot from 2022-12-22 13-32-411024×624 13.3 KB

As soon as I logged out my local session, ThinLinc is working fine.

This was verified with both 4.12.0 and 4.14.0 of ThinLinc server.
An upgrade will probably not solve it for you, but we always recommend running the most recent version of ThinLinc since other bugs and issues has been resolved.

11

This display/window is equal to what is displayed to me…

I rebooted

  • Windows computer
  • Linux computer
    After reboot there can be no local GUI session, right?

Tried to connect via ThinLinc but the problem remains.

12

I think it is like this

  1. Win10 PC uses ThinLinc 4.14.0 to connect to ThinLinc Brigde
  2. ThinLinc Brigde uses ThinLinc 4.7 client to connect to PC Debian 10
  3. PC Debian 10 uses ThinLinc 4.12 server
13

After logon, Window Profile Chooser is displayed. (2 options)
Quit => exit ThinLinc
OK => Start session… flickers quickly by=> Could not acquire name on session bus => close(only option)