Bug#624021: systemd-gui: 'systemadm' fails with "Error connecting: No such file or directory"
A. Costa
Version: 20-1
Severity: important
Test run:
systemadm ; echo $?
...up pops a little error window stating
"Error connecting: No such file or directory".
The terminal shows:
(systemadm:10475): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(systemadm:10475): GLib-GObject-CRITICAL **: g_object_ref_sink: assertion `G_IS_OBJECT (object)' failed
0
The exit code shouldn't be a '0'.
Hope this helps...
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.38-2-686 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/dash
Versions of packages systemd-gui depends on:
ii libc6 2.11.2-11 Embedded GNU C Library: Shared lib
ii libglib2.0-0 2.28.6-1 The GLib library of C routines
ii libgtk2.0-0 2.20.1-2 The GTK+ graphical user interface
ii libnotify1 [libnotify1-gtk2.1 0.5.0-2 sends desktop notifications to a n
ii systemd 20-1 system and service manager
systemd-gui recommends no packages.
systemd-gui suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Michael Biebl
> Package: systemd-gui
> Version: 20-1
> Severity: important
>
>
> Test run:
>
> systemadm ; echo $?
>
> ...up pops a little error window stating
> "Error connecting: No such file or directory".
>
> The terminal shows:
>
> (systemadm:10475): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
>
> (systemadm:10475): GLib-GObject-CRITICAL **: g_object_ref_sink: assertion `G_IS_OBJECT (object)' failed
> 0
>
> The exit code shouldn't be a '0'.
>
> Hope this helps...
Not really.
Can you describe in more detail, what you were doing.
Is systemd running? Did you run systemadm as root/regular user?
Does systemctl dump work?
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
Michael Biebl
> On Sun, 22 May 2011 06:09:58 +0200
> % systemctl dump ; echo $?
> Failed to get D-Bus connection: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
> 1
That means dbus is not running.
Please check the status:
systemctl status dbus.socket
systemctl status dbus.service
Most likely this is a duplicate of #622881.
Please check the dmesg output, if systemd encountered a cycle and attach the output.
A. Costa
Michael Biebl <bi...@debian.org> wrote:
> > % systemctl dump ; echo $?
> > Failed to get D-Bus connection: Failed to connect to
> > socket /var/run/dbus/system_bus_socket: No such
> > file or directory 1
>
> That means dbus is not running.
> Please check the status:
> systemctl status dbus.socket
> systemctl status dbus.service
root [VT] ~>systemctl status dbus.socket
dbus.socket - D-Bus System Message Bus Socket
Loaded: loaded (/lib/systemd/system/dbus.socket)
Active: inactive (dead)
CGroup: name=systemd:/system/dbus.socket
root [VT] ~>systemctl status dbus.service
dbus.service - D-Bus System Message Bus
Loaded: loaded (/lib/systemd/system/dbus.service)
Active: inactive (dead)
CGroup: name=systemd:/system/dbus.service
> Most likely this is a duplicate of #622881.
>
> Please check the dmesg output, if systemd encountered a cycle and
> attach the output.
Attached is the output of:
dmesg | nl | grep -C 5 "systemd.*cycle" | gzip -9 > /tmp/dmesg_systemd_cycle.log.gz
HTH...
Michael Biebl
forcemerge 622881 624021
thanks
Am 25.05.2011 19:08, schrieb A. Costa:
> On Mon, 23 May 2011 05:38:26 +0200
> Michael Biebl <bi...@debian.org> wrote:
>> Please check the status:
>> systemctl status dbus.socket
>> systemctl status dbus.service
>
> root [VT] ~>systemctl status dbus.socket
> dbus.socket - D-Bus System Message Bus Socket
> Loaded: loaded (/lib/systemd/system/dbus.socket)
> Active: inactive (dead)
> CGroup: name=systemd:/system/dbus.socket
>
>> Most likely this is a duplicate of #622881.
>>
>> Please check the dmesg output, if systemd encountered a cycle and
>> attach the output.
>
> Attached is the output of:
Thanks, this is a dup. You can work around this problem by purging the
nfs-common/portmap packages.
Michael Biebl
>
> % dmesg | nl | grep "systemd.*Breaking.*cycle" | sed 's,.*job \(.*\)\..*,\1,'
> dbus
> avahi-daemon
> setserial
> ipmasq
>
> A test run of 'aptitude purge dbus avahi-daemon setserial ipmasq' shows it
> would need to delete 327 packages. Ouch.
>
> Following your lead, I'm guessing that the above four packages, and the
> two before, i.e. 'dbus', 'avahi-daemon', 'setserial', 'ipmasq',
> 'nfs-common', & 'portmap'; these six packages presumably have buggy
> Debian boot dependency code.
dbus is a central piece of a today's Linux desktop. You can't easily remove.
That said, I'm maintainer of dbus and avahi-daemon, so I'm pretty sure those two
services are fine.
It's either setserial or ipmasq.
Could you attach those files, please.
A. Costa
Michael Biebl <bi...@debian.org> wrote:
> dbus is a central piece of a today's Linux desktop. You can't easily
> remove. That said, I'm maintainer of dbus and avahi-daemon, so I'm
> pretty sure those two services are fine.
> It's either setserial or ipmasq.
> Could you attach those files, please.
Not sure, which files from those packages are needed?
A guess: perhaps the 'INIT INFO' headers from the relevant
'/etc/init.d' config files are of interest? Attached are package
version numbers, and those headers, via:
% CHECKTHESE="setserial ipmasq" ; \
{ dlocate -s $CHECKTHESE | egrep Pac\|Ver ; \
parallel dlocate -L -- $CHECKTHESE | grep init.d/ | \
while read x ; do echo $x ; grep -B 100 "END INIT" $x | nl ; done }
HTH...