Bug 106874 - Failed to connect to bus: Connection refused
Summary: Failed to connect to bus: Connection refused
Status: RESOLVED MOVED
Alias: None
Product: dbus
Classification: Unclassified
Component: core (show other bugs)
Version: unspecified
Hardware: ARM Linux (All)
: medium major
Assignee: D-Bus Maintainers
QA Contact: D-Bus Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-06-10 06:59 UTC by ali
Modified: 2018-10-12 21:35 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description ali 2018-06-10 06:59:11 UTC
I don't know where is the root cause of problem. So I decided to report this bug in two places (systemD[github.com] + dbus[bugs.freedesktop.org]).

https://github.com/systemd/systemd/issues/9248

Thanks in advance
Comment 1 Simon McVittie 2018-06-11 12:04:27 UTC
From the systemd bug report:

"""
systemd version the issue has been seen with

    systemd is already the newest version (238-5)
    xfce4 is already the newest version (4.12.4) [my default environment is based on XFCE-4]
    dbus is already the newest version (1.12.8-2)
    dbus-1-doc is already the newest version (1.12.8-2)
    dbus-java-bin is already the newest version (2.8-9)
    dbus-test-runner is already the newest version (16.10.0~bzr100+repack1-2)
    dbus-tests is already the newest version (1.12.8-2)
    dbus-user-session is already the newest version (1.12.8-2)
    dbus-x11 is already the newest version (1.12.8-2)
    dbus-cpp-bin:i386 is already the newest version (5.0.0+18.04.20171031-1)
    dbus-cpp-dev-examples:i386 is already the newest version (5.0.0+18.04.20171031-1)
    libdbus-cpp-dev:i386 is already the newest version (5.0.0+18.04.20171031-1)

Used distribution

    Kali Linux RaspberryPi-3-B [upgraded to latest changes via sudo apt-get dist-upgrade.
    root@kali: uname -a
    Linux kali 4.9.59-v7_Re4son-Kali-Pi+ #1 SMP Wed Feb 14 20:50:28 CST 2018 armv7l GNU/Linux

Unexpected behaviour you saw

    root@kali: systemctl --user
    Failed to connect to bus: Connection refused
    root@kali: systemctl --user list-units
    Failed to connect to bus: Connection refused

    I got below error in a window:
    Unable to connect to socket /run/user/0 ....... bus: connection refused
    image links:
    https://imgur.com/a/2MOGG1O
    https://imgur.com/a/Y4Sm3bK

Steps to reproduce the problem
i was working on runlevel-3 (command-line mode interface) in Kali Linux [on Raspberry-Pi_3B] and I want to do something in GUI-mode (runlevel-5). before upgrading Kali to last version I hadn't any problem. but now i have it. ;/
"""
Comment 2 Simon McVittie 2018-06-11 12:09:46 UTC
> i was working on runlevel-3 (command-line mode interface) in Kali Linux [on Raspberry-Pi_3B] and I want to do something in GUI-mode (runlevel-5).

Sorry, those are not steps to reproduce the problem.

How did you boot the system into "runlevel 3"? How did you switch it to "runlevel 5"? (Runlevels are a sysv-rc concept and don't really exist in systemd; they are compatibility aliases for systemd targets on a systemd system.)

How did you log in? Did you log in as an ordinary user and escalate privileges to root via su or sudo or pkexec or something, or did you log in as root? Did you log in to a getty session or into something like gdm/xdm/lightdm?

> root@kali: systemctl --user
> Failed to connect to bus: Connection refused
> root@kali: systemctl --user list-units
> Failed to connect to bus: Connection refused
>
> I got below error in a window

I'm fairly sure you didn't get that error message as a result of running systemctl, because systemctl isn't a GUI. What else did you do? Did you try to run a complete XFCE session as root, or run a single GUI application as root under an XFCE session running as some other user, or what?

This sounds like a result of either doing the wrong thing, or a distro integration issue. If it's a distro integration issue, you might have better success talking to Kali Linux support channels.

Whoever you ask, please be complete and specific about how you could produce this error.
Comment 3 GitLab Migration User 2018-10-12 21:35:01 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/dbus/dbus/issues/213.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.