You are not logged in.

#26 2016-09-01 23:11:50

marcoy
Member
From: New York, NY
Registered: 2012-01-19
Posts: 4

Re: Failed to connect to socket /tmp/dbus-xxx: Connection refused

I'm still experiencing the problem. There is nothing under /etc/systemd/user, and there are no *.pacnew files inside /etc/pam.d.
It seems like the only way to resolve this is to downgrade. Any other ideas?

Offline

#27 2016-09-02 01:10:46

Scimmia
Bug Wrangler
Registered: 2012-09-01
Posts: 7,758

Re: Failed to connect to socket /tmp/dbus-xxx: Connection refused

Yeah, get rid of any usage of dbus-launch

Offline

#28 2016-09-02 18:19:00

xela92
Member
Registered: 2016-09-02
Posts: 2

Re: Failed to connect to socket /tmp/dbus-xxx: Connection refused

I had the same issue, either on a older installation either on a fresh one hmm downgrading dbus too

Offline

#29 2016-09-02 18:27:28

marcoy
Member
From: New York, NY
Registered: 2012-01-19
Posts: 4

Re: Failed to connect to socket /tmp/dbus-xxx: Connection refused

Scimmia wrote:

Yeah, get rid of any usage of dbus-launch

I did a grep inside /etc for dbus-launch. The only hits were all inside the file /etc/xdg/xfce4/xinitrc (I'm using xfce4), then I commented out the line that invokes dbus-launch. The problem still persists.

Offline

#30 2016-09-04 12:16:56

gmtch
Member
Registered: 2015-03-29
Posts: 7

Re: Failed to connect to socket /tmp/dbus-xxx: Connection refused

I seem to have a linked dbus issue affecting kodi & kodi-standalone.

I have an Intel NUC running kodi using an MCE remote control. I upgraded the system yesterday.

Post-upgrade whilst watching a video if I pressed the "Stop" button or "Pause" on the remote the video would freeze and kodi be utterly unresponsive. Even with debug logging enabled kodi would stop all logging.

The only method to resolve this was to SSH in and restart the kodi service using systemd.

I also have a wireless RF keyboard attached - it was not affected. Likewise kodi remote-control via http is not affected.

Downgrading dbus to 1.10.8-1 and reinstalling libdbus-1.10.8-1 has resolved the issue.

The kodi.service uses /usr/bin/dbus-launch:

ExecStart = /usr/bin/xinit /usr/bin/dbus-launch --exit-with-session /usr/bin/kodi-standalone -- :0 -nolisten tcp vt7

The kodi wiki itself recommends using dbus-launch in the service file.

Offline

#31 2016-09-04 14:16:21

Scimmia
Bug Wrangler
Registered: 2012-09-01
Posts: 7,758

Re: Failed to connect to socket /tmp/dbus-xxx: Connection refused

There is no kodi.service in the repos.

Offline

#32 2016-09-05 17:41:23

gmtch
Member
Registered: 2015-03-29
Posts: 7

Re: Failed to connect to socket /tmp/dbus-xxx: Connection refused

Ah you are right.

I had forgotten that kodi.service came from the AUR package kodi-standalone-service.

I hadn't looked at the issue since I downgraded dbus yesterday. I clearly have to look more closely at start up methods.

Thanks

Offline

#33 2016-09-05 18:42:22

steff
Member
Registered: 2009-01-08
Posts: 54

Re: Failed to connect to socket /tmp/dbus-xxx: Connection refused

LXQt +sddm I had unusable session,using startx + .xinitrc worked. Solution was the  /etc/pam.d/systemd-user.pacnew file  just put it in place.

# This file is part of systemd.
#
# Used by systemd --user instances.

account  include system-login

session  required pam_loginuid.so
session  include system-login

I solved also my old problem of using  $ systemctl --user start psd

Last edited by steff (2016-09-05 18:43:51)

Offline

#34 2016-09-06 05:26:35

Roken
Member
From: UK
Registered: 2012-01-16
Posts: 1,077

Re: Failed to connect to socket /tmp/dbus-xxx: Connection refused

my systemd-user file already looks like that sad


[img=Speedtest]http://www.speedtest.net/my-result/5145583518[/img]

Ryzen 1800x 8 core/16 thread - GTX 1070 8Gb, Asus ROG STRIX B350-F, 16Gb Corsair DDR4, Cooler Master N300 chassis, 6 HD (1 NvME PCI, 2SSD, 3Spinners) + 1 x optical.
Linux user #545703

Offline

#35 2016-09-06 09:35:59

mcallis
Member
Registered: 2016-09-06
Posts: 2

Re: Failed to connect to socket /tmp/dbus-xxx: Connection refused

Moving 25-xlogin in  /etc/X11/xinit/xinitrc.d/ out of the way fixed the problem for me.

This is the content of that file:

#! /usr/bin/bash

# Don't use the systemd user bus for the X session
if [ "$DBUS_SESSION_BUS_ADDRESS" = "unix:path=$XDG_RUNTIME_DIR/bus" ]; then
    unset DBUS_SESSION_BUS_ADDRESS
fi

My guess is that some part of the system relies on DBUS_SESSION_BUS_ADDRESS, but a quick grep did not give me any results.
I'm using gnome and gdm. The Wayland session always worked for me, but not the default one.

EDIT: That file is part of the xlogin-git AUR package. No idea why I had that installed.

Last edited by mcallis (2016-09-06 09:56:41)

Offline

#36 2016-09-06 20:04:32

Roken
Member
From: UK
Registered: 2012-01-16
Posts: 1,077

Re: Failed to connect to socket /tmp/dbus-xxx: Connection refused

Nope, not got that file sad


[img=Speedtest]http://www.speedtest.net/my-result/5145583518[/img]

Ryzen 1800x 8 core/16 thread - GTX 1070 8Gb, Asus ROG STRIX B350-F, 16Gb Corsair DDR4, Cooler Master N300 chassis, 6 HD (1 NvME PCI, 2SSD, 3Spinners) + 1 x optical.
Linux user #545703

Offline

#37 2016-09-06 23:16:16

marcoy
Member
From: New York, NY
Registered: 2012-01-19
Posts: 4

Re: Failed to connect to socket /tmp/dbus-xxx: Connection refused

mcallis wrote:

Moving 25-xlogin in  /etc/X11/xinit/xinitrc.d/ out of the way fixed the problem for me.

This is the content of that file:

#! /usr/bin/bash

# Don't use the systemd user bus for the X session
if [ "$DBUS_SESSION_BUS_ADDRESS" = "unix:path=$XDG_RUNTIME_DIR/bus" ]; then
    unset DBUS_SESSION_BUS_ADDRESS
fi

My guess is that some part of the system relies on DBUS_SESSION_BUS_ADDRESS, but a quick grep did not give me any results.
I'm using gnome and gdm. The Wayland session always worked for me, but not the default one.

EDIT: That file is part of the xlogin-git AUR package. No idea why I had that installed.

I do have that file. Even after I moved the file to somewhere else, I still have the same problem.

Offline

#38 2016-09-07 08:03:34

mcallis
Member
Registered: 2016-09-06
Posts: 2

Re: Failed to connect to socket /tmp/dbus-xxx: Connection refused

Perhaps you have another init file that either calls dbus-launch oder messes with the DBUS_SESSION_BUS_ADDRESS environment variable.
For me that seems to have been the problem.

Offline

#39 2016-09-07 17:45:48

zofiel
Member
Registered: 2015-03-27
Posts: 11

Re: Failed to connect to socket /tmp/dbus-xxx: Connection refused

gmtch wrote:

I seem to have a linked dbus issue affecting kodi & kodi-standalone.

I have an Intel NUC running kodi using an MCE remote control. I upgraded the system yesterday.

Post-upgrade whilst watching a video if I pressed the "Stop" button or "Pause" on the remote the video would freeze and kodi be utterly unresponsive. Even with debug logging enabled kodi would stop all logging.

The only method to resolve this was to SSH in and restart the kodi service using systemd.

I also have a wireless RF keyboard attached - it was not affected. Likewise kodi remote-control via http is not affected.

Downgrading dbus to 1.10.8-1 and reinstalling libdbus-1.10.8-1 has resolved the issue.

The kodi.service uses /usr/bin/dbus-launch:

ExecStart = /usr/bin/xinit /usr/bin/dbus-launch --exit-with-session /usr/bin/kodi-standalone -- :0 -nolisten tcp vt7

The kodi wiki itself recommends using dbus-launch in the service file.

same problem here.

Deleting /usr/bin/dbus-launch --exit-with-session solved the issue

Offline

#40 2016-09-07 19:43:06

Roken
Member
From: UK
Registered: 2012-01-16
Posts: 1,077

Re: Failed to connect to socket /tmp/dbus-xxx: Connection refused

that's not it with me:

sudo grep -r DBUS_SESSION_BUS_ADDRESS *
grep: webmin/system-status/history/load5: Input/output error
xdg/xfce4/xinitrc:if test x"$DBUS_SESSION_BUS_ADDRESS" = x""; then
xdg/xfce4/xinitrc:    export DBUS_SESSION_BUS_ADDRESS

And I already tried commenting that out of xinitrc


[img=Speedtest]http://www.speedtest.net/my-result/5145583518[/img]

Ryzen 1800x 8 core/16 thread - GTX 1070 8Gb, Asus ROG STRIX B350-F, 16Gb Corsair DDR4, Cooler Master N300 chassis, 6 HD (1 NvME PCI, 2SSD, 3Spinners) + 1 x optical.
Linux user #545703

Offline

#41 2016-09-07 22:42:54

digitalfrost
Member
Registered: 2007-10-15
Posts: 11

Re: Failed to connect to socket /tmp/dbus-xxx: Connection refused

ppine wrote:

As pointed out by:  Nicky726 on https://bugs.archlinux.org/user/3121

I removed dbus files located at /etc/systemd/user (dbus.service, dbus.socket)

This solved my problem.

I could no longer login to KDE. It said

Could not start d-bus. Can you call qdbus?

. Removing these files fixed it for me. DBUS_SESSION_BUS_ADDRESS was empty before as well and is now set.

Offline

#42 2016-09-08 19:07:58

graysky
Wiki Maintainer
From: :wq
Registered: 2008-12-01
Posts: 10,015
Website

Re: Failed to connect to socket /tmp/dbus-xxx: Connection refused

gmtch wrote:

I seem to have a linked dbus issue affecting kodi & kodi-standalone.

Odd, I do not see this on several different hardware configurations, ie aur/kodi-standalone-service-1.8-5 works fine with the current dbus package... it also starts if I replace the ExecStart line I am shipping with the package with the one you recommended, ie:

ExecStart = /usr/bin/xinit /usr/bin/kodi-standalone -- :0 -nolisten tcp vt7

Last edited by graysky (2016-09-08 19:19:05)


CPU-optimized Linux-ck packages @ Repo-ck  • AUR packagesZsh and other configs

Offline

#43 2016-09-14 09:50:42

Felixoid
Member
Registered: 2012-05-23
Posts: 12

Re: Failed to connect to socket /tmp/dbus-xxx: Connection refused

for me works:
Remove dbus-launch --exec-with-session from ~/.xinitrc

exec dbus-launch --exec-with-session startxfce4

Offline

#44 2016-09-18 10:09:06

Addow
Member
Registered: 2011-12-05
Posts: 1

Re: Failed to connect to socket /tmp/dbus-xxx: Connection refused

mcallis wrote:

Moving 25-xlogin in  /etc/X11/xinit/xinitrc.d/ out of the way fixed the problem for me.

EDIT: That file is part of the xlogin-git AUR package. No idea why I had that installed.

Thanks mcallis, this solved it for me too. I have been scratching my head and had to refresh my mind WHY exactly I had this xlogin-git AUR package installed. Apparently back in the days I insisted on having an automatic X login without display manager. Really no idea why, because I actually use one roll

Last edited by Addow (2016-09-18 10:12:29)

Offline

#45 2016-09-18 12:11:53

Roken
Member
From: UK
Registered: 2012-01-16
Posts: 1,077

Re: Failed to connect to socket /tmp/dbus-xxx: Connection refused

I still don't know where this is launching from:

ps -ef | grep dbus-launch
steve      859     1  0 12:10 ?        00:00:00 dbus-launch --autolaunch b61fad530cae4af75f6fbc5800000720 --binary-syntax --close-stderr
steve      874     1  0 12:10 ?        00:00:00 /usr/bin/dbus-launch --sh-syntax --exit-with-session xfce4-session

I've removed all references to dbus-launch in relation to xfce4 that I can find. Parent process is root, and so no clues there.

EDIT:

b61fad530cae4af75f6fbc5800000720 appears to be pulseaudio

Last edited by Roken (2016-09-18 12:14:09)


[img=Speedtest]http://www.speedtest.net/my-result/5145583518[/img]

Ryzen 1800x 8 core/16 thread - GTX 1070 8Gb, Asus ROG STRIX B350-F, 16Gb Corsair DDR4, Cooler Master N300 chassis, 6 HD (1 NvME PCI, 2SSD, 3Spinners) + 1 x optical.
Linux user #545703

Offline

#46 2016-09-22 00:47:19

Maniaxx
Member
From: .de
Registered: 2014-05-14
Posts: 297

Re: Failed to connect to socket /tmp/dbus-xxx: Connection refused

Lookup systemd cgroups (systemctl status) to see if its related to a service/unit file.

Last edited by Maniaxx (2016-09-22 00:50:11)


sys2064

Offline

#47 2017-07-18 05:51:15

stillrottentothegore
Member
Registered: 2017-07-18
Posts: 19

Re: Failed to connect to socket /tmp/dbus-xxx: Connection refused

Did anyone find a fix for this?  I've tried all the suggestions in the thread and no dice so far.

Offline

#48 2017-07-18 07:46:40

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 9,863
Website

Re: Failed to connect to socket /tmp/dbus-xxx: Connection refused

Please don't necrobump. Create a new topic and describe your setup, paste your config files, etc.

https://wiki.archlinux.org/index.php/Co … bumping.22

Closing.


Sakura:-
Mobo: MSI X299 TOMAHAWK ARCTIC // Processor: Intel Core i7-7820X 3.6GHz // GFX: nVidia GeForce GTX 970 // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 5x 1TB HDD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

Board footer

Powered by FluxBB