Error connecting to dbus antiX 21 testing SOLVED

[Member ModdIt]

Running antiX 21 with testing repos, this message keeps popping up after recent updates when I use Terminal.
Some other applications, one is librewolf show similar messages when started from the terminal.
Browser is very slow to start so looking for problems ).

Error connecting to dbus: Failed to connect to socket /tmp/dbus-D1CpcyaArQ: Connection Refused

Last time I saw the error was eons ago, found a lot of old posts but as yet no solution.
Any suggestions/ideas for a fix welcome.

• This topic was modified 9 months ago by ModdIt.

[Member sybok]

Helpful

Up

0

::

Hi, I run antiX-21 testing (with SysV init) as well and I did not experience the issue.
When/How exactly does the message appear? (E.g. I start <this terminal>, execute <this command> and there it is.)

I’ve no idea apart from doing interweb search (both Google and DuckDuckGo) out of curiosity; the queries were:
“Error connecting to dbus: Failed to connect to socket” /tmp/dbus-D1CpcyaArQ: “Connection Refused”
“Error connecting to dbus: Failed to connect to socket” /tmp/dbus “Connection Refused”

And it produced rather old posts too.

1) Arch-Linux [https://bbs.archlinux.org/viewtopic.php?id=216451]
1.A) Workaround: downgrade dbus, dbuslib*
1.B) Remove some files: https://bbs.archlinux.org/viewtopic.php?pid=1651391#p1651391
1.C) Remove another file: https://bbs.archlinux.org/viewtopic.php?pid=1652394#p1652394
2) Open-Suse:
Anaconda modified ‘~/.bashrc’: https://forums.opensuse.org/showthread.php/527568-Continuing-dbus-session-manager-not-starting
3) antiX (finally!):
installing ‘dbus-x11’ may help fix roxterm not opening: https://antixlinux.com/forum-archive/roxterm-won-t-open-after-nvidia-update-t4024.html

Not much of help, I guess. 🙁
Perhaps suggesting which of the recent updates (explore ‘/var/log/apt/history.log*’ files) you do suspect to be the cause of the issue(s) might provide a hint for someone interested.

• This reply was modified 9 months ago by sybok. Reason: Explicitly mentioning I run SysV init version

[Forum Admin anticapitalista]

Helpful

Up

0

::

I suspect dbus is not running as a runit service.

Firstly,

ls -la /etc/service/

Use runit-service-manager.sh to start it.

Perhaps you will need a reboot

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member stevesr0]

Helpful

Up

0

::

Not trying to kidnap the thread – re: /etc/service.

I have an /etc/sv directory (running Sid svinit), but no /etc/services directory. Is this a recent change with Sid or have I got something peculiar.

I do get a list of services using the service –status-all command.

…and as far as I know, things are working <g>.r

(I tried searching the forum and after a few tries was locked out as a possible robot. After passing the captcha test, I was let back in.)

stevesr0

[Forum Admin anticapitalista]

Helpful

Up

0

::

/etc/service/ not /etc/services is used for runit not sysvinit

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member ModdIt]

Helpful

Up

1

::

Thanks to all for suggestions. I have learned quite a lot about the system setup in the last two days :-).
I had checked dbus was running before posting, Init is on this install sysV.

To cut a long story short, reinstalling the no systemd dbus packets plus deleting contents of
/home/username/.dbus/session-bus/ seem to have fixed the issue.

My guess is after system lock ups during NVidia Vulcan drivers install there were old PID/lock or similar
files left over. Probably the reinstall was unnecessary

Next time I know what to do first.

During this problematic installation I had to remove a misbehaving NVME drive mounted in an internal
adapter and install to an SSD. Installing the NVidia drivers for the modern silent card was a pain, but the graphics
performance and reduction in GPU temperature and CPU load is worth the work.

The NVME setup was fine but after a couple of months refused to work as boot device and became slug slow. Now will
replace the adapter and hope to be able to reuse the expensive quality 512 GB drive.
Both drive and adapter are still under warranty so hoping the seller will give me either a refund or ask amazon to send
a replacement adapter card.

• This reply was modified 9 months ago by ModdIt.

[Forum Admin anticapitalista]

Helpful

Up

0

::

Glad you fixed it.
I totally misread your post. I read ‘Running’ as ‘runit’

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member ModdIt]

Helpful

Up

0

::

Hallo anticapitalista,
Thanks for your assistance and no worries, the same problem would probably have occurred with any init
version.
We now know the first aid, I had never noticed the /home/username/.dbus/session-bus/ file before.
The info may be useful after any desktop freeze or crash case.

Based on this install, if a modern Nvidia card is involved the best strategy seems to be to find
which driver supports it, make sure system is on newest available kernel then install the highest
version of Nvidia driver packages directly using apt.

Still doing some configuration, system is now running lightning fast and stable.

Will give feedback on NVME issues in a separate thread once I have replaced the adapter.

• This reply was modified 9 months ago by ModdIt.

[Author]

Posts