You are not logged in.

#1 2016-08-16 22:40:07

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

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

OK, I use testing, and most of the time it's fine. However, tonight I fired up an, at the "desktop", nada. Switch between TTY1 and TTY7 (TTY7 is my xserver) and I have an X error "Unable to connect to server".

After some playing, going back to Dbus from core got me going. DBus from Testing is kiss of death. A quick search shows nothing. Is this a known problem, or should I be reporting a bug?

Last edited by jasonwryan (2016-09-01 19:01:49)


[img= Speedtest]https://www.speedtest.net/result/10678208597.png[/img]

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

Offline

#2 2016-08-16 23:02:25

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 29,148
Website

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

Works for me...

Moving to [testing]


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#3 2016-08-24 11:37:08

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

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

Nope, I still have the same problem even after dbus 1.10.10-3. More info.

dbus 1.10.10 removes libdbus, presumably providing it itself now, instead of it being split. Last version of libdbus seems to be 1.10.8

The error provided by my (very limited - no window borders, can't alt-tab etc. No wallpaper) xfce session is

Failed to connect to socket /tmp/dbus-xxxxxxxxx: Connection refused

The last message on TTY1 (I run X on TTY7) is

a start job is running for user manager for uid 1000

Which has gone to 1min 30 secs and just stops there.

I can get to a fully working desktop again by killing lightdm, which forces a re-login. However, the blinking light on my webcam suggests something is still awry (possibly connected to pulseaudio)

downgrading dbus to 1.10.8-3 and reinstalling libdbus 1.10.8-3 gets things back to normal. For now, I have them added to ignore in pacman.conf.

The only other ignored package is ttf-ms-win10 until I have time to extract and sha256sum the fonts, but since this is an AUR package it shouldn't have any bearing. Everything else is up to date (xorg, xfce4, lightdm) and as far as I know they haven't been updated recently. I can't find anything on the wiki, unless I'm searching for the wrong thing.

Looking for ideas now.

Last edited by Roken (2016-08-24 11:38:43)


[img= Speedtest]https://www.speedtest.net/result/10678208597.png[/img]

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

Offline

#4 2016-08-28 10:02:58

Alad
Wiki Admin/IRC Op/TU
From: Bagelstan
Registered: 2014-05-04
Posts: 2,143
Website

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

Looking at the changelog, the Arch package removed X11 support with the 1.10.10 update. You should probably open a bug on flyspray about this.

Last edited by Alad (2016-08-28 10:06:43)


Mods are just community members who have the occasionally necessary option to move threads around and edit posts. -- Trilby
Honest Alad's Package Emporium—Now with added bugs! (Grand reopening: December 1st 2018)

Offline

#5 2016-08-28 10:38:01

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

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

Good call. I added it to bugzilla upstream. Reported on flyspray, too.


[img= Speedtest]https://www.speedtest.net/result/10678208597.png[/img]

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

Offline

#6 2016-08-28 15:52:57

Scimmia
Bug Wrangler
Registered: 2012-09-01
Posts: 8,197

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

You seem to be the only one with this issue, though. dbus should be launched in the systemd user session, not through dbus-launch. Do you have the unit masked or something? Session broken?

Offline

#7 2016-08-28 19:20:35

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

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

I have never masked dbus, and never had a problem with it. The problem could be so many things, tho'. Lightdm, pam, dbus etc. etc. Really hoping someone else gets the problem so that I can start narrowing it down.


[img= Speedtest]https://www.speedtest.net/result/10678208597.png[/img]

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

Offline

#8 2016-08-29 09:26:16

lula
Member
Registered: 2009-07-16
Posts: 63

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

Had exactly the same problem and solved it by replacing systemd-user and login in /etc/pam.d with their newer versions (.pacnew)

HTH

Offline

#9 2016-08-29 14:42:05

fabertawe
Member
From: Lloegr
Registered: 2009-11-24
Posts: 275

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

Scimmia wrote:

...dbus should be launched in the systemd user session, not through dbus-launch...

Well I don't know how I missed the news on this but I did! This is why Xorg was freezing for me. I've altered my startup appropriately and all working now. Thanks for the pointer.


i7 4790K 4.4GHz, ASRock Z97 Extreme6, 16GB 2400MHz, GTX 970, Arch x86_64

Offline

#10 2016-08-30 06:09:28

alexdw
Member
Registered: 2013-03-25
Posts: 46

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

lula wrote:

Had exactly the same problem and solved it by replacing systemd-user and login in /etc/pam.d with their newer versions (.pacnew)

HTH

Thank you - I had a similar problem and this fixed it for me.

Offline

#11 2016-08-30 08:44:39

ppine
Member
From: Netherlands
Registered: 2014-10-12
Posts: 5

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

alexdw wrote:
lula wrote:

Had exactly the same problem and solved it by replacing systemd-user and login in /etc/pam.d with their newer versions (.pacnew)

HTH

Thank you - I had a similar problem and this fixed it for me.

There are no .pacnew files in /etc/pam.d on my system hmm

( Not using the testing repo's )

Current login contains:

#%PAM-1.0

auth       required     pam_securetty.so
auth       requisite    pam_nologin.so
auth       include      system-local-login
account    include      system-local-login
session    include      system-local-login

Current systemd-user contains:

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

account  include system-login

session  required pam_loginuid.so
session  include system-login

.xsessions-errors shows :

syndaemon: no process found
/etc/mdm/Xsession: Beginning session setup...
dbus-update-activation-environment: error: unable to connect to D-Bus: Using X11 for dbus-daemon autolaunch was disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead
/etc/mdm/Xsession: Setup done, will execute: /usr/bin/ssh-agent -- startxfce4
/usr/bin/startxfce4: X server already running on display :0
xrdb:  "Xft.hinting" on line 14 overrides entry on line 6
xrdb:  "Xft.hintstyle" on line 17 overrides entry on line 7

(xfce4-session:557): xfce4-session-CRITICAL **: Unable to contact D-Bus session bus: Failed to connect to socket /tmp/dbus-lnsiT0sgGL: Connection refused

Last edited by ppine (2016-08-30 09:35:09)

Offline

#12 2016-08-30 10:16:05

aaronmueller
Member
Registered: 2012-08-25
Posts: 15
Website

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

I have the exact same problem here, @ppine.
I use i3wm with slim.

I opened a issue on the bug tracker
https://bugs.archlinux.org/task/50587

Last edited by aaronmueller (2016-08-30 10:17:50)

Offline

#13 2016-08-30 11:46:31

Sebarres
Member
Registered: 2012-01-08
Posts: 15

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

I am glad to see that I am not alone : same problem than @ppine and @aaronmueller.

Offline

#14 2016-08-30 13:27:10

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

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

lula wrote:

Had exactly the same problem and solved it by replacing systemd-user and login in /etc/pam.d with their newer versions (.pacnew)

HTH

No joy, no pacnew files.

I had a look systemd PKGBUILD, and that modifies systemd-user in place. I checked, and the modifications are made.

I had a look at the new login and tried both modifying my existing login to include the extra, and replacing completely. Neither work sad

Back to the old dbus and libdbus for now.


[img= Speedtest]https://www.speedtest.net/result/10678208597.png[/img]

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

Offline

#15 2016-08-30 13:40:02

Scimmia
Bug Wrangler
Registered: 2012-09-01
Posts: 8,197

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

There seems to be an issue with xfce4, so of course you still have the issue.

https://bugs.archlinux.org/task/50543

Offline

#16 2016-08-30 19:05:47

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

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

Yes, that's my bug report.


[img= Speedtest]https://www.speedtest.net/result/10678208597.png[/img]

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

Offline

#17 2016-08-30 20:52:01

lula
Member
Registered: 2009-07-16
Posts: 63

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

@alexdw: You're welcome

@Scimmia: alexdw and me are both on xfce, so for me the problem seems to be be more specific to Roken's setup

Offline

#18 2016-08-30 21:46:53

Scimmia
Bug Wrangler
Registered: 2012-09-01
Posts: 8,197

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

There's something specific in /etc/xdg/xfce4/xinitrc that runs dbus-launch. This is very likely his issue.

Offline

#19 2016-08-30 22:20:39

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

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

There seem to be even more issues (gksu/gksudo):
https://bbs.archlinux.org/viewtopic.php?id=216523


sys2064

Offline

#20 2016-08-31 10:55:42

luuuciano
Member
Registered: 2007-01-27
Posts: 309

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

I am using lxqt + sddm, after the upgrade it was very broken, can not init in lxqt xfce kde...

Downgrading dbus & libdbus for a while
(sadly I have no time to test & search things right now)


I arch, you arch, he arch, she arch, we arch, they arch...

Offline

#21 2016-09-01 07:59:22

Hacksign
Member
Registered: 2012-07-30
Posts: 92

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

I updated my system yesterday (there is an update of dbus).
After I reboot my system, many program behaved abnormally(like thunar can not remeber window size of last time I set).
Error message r all like this (xxxx is an random string):
Failed to connect to socket /tmp/dbus-xxxx : connection refused

I must run program like this:
dbus-launch <program I want to run>

Any one knows how to fix this ?

Environment is :
systemd + lightdm-gtk-greeter + awesomeWM

Offline

#22 2016-09-01 10:03:38

markus
Member
Registered: 2014-06-16
Posts: 4

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

Same here, downgrading dbus/libdbus to 1.10.8-1 fixed the problem for me.

Offline

#23 2016-09-01 18:59:38

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 29,148
Website

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

Moving this out of [testing] to Apps & DEs


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#24 2016-09-01 19:00:21

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 29,148
Website

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

Merging with existing thread


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#25 2016-09-01 19:03:22

ppine
Member
From: Netherlands
Registered: 2014-10-12
Posts: 5

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

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.

Offline

Board footer

Powered by FluxBB