Version: 44-1
The problem is fixed in the latest version, I can run systemd on both
my homestation and my laptop. The above line should close the bug or
an email to #-done@b.d.o is necessary.
2012/2/26 Michael Biebl bi...@debian.org:
Most likely a duplicate of
2012/2/26 Michael Biebl bi...@debian.org:
Could you send the output of
systemctl status dbus.socket dbus.service
directly after (re)boot.
Here it is.
| dbus.socket - D-Bus System Message Bus Socket
| Loaded: loaded (/lib/systemd/system/dbus.socket; static)
| Active:
On 26.02.2012 19:02, Teodor MICU wrote:
2012/2/26 Michael Biebl bi...@debian.org:
Could you send the output of
systemctl status dbus.socket dbus.service
directly after (re)boot.
Here it is.
| dbus.socket - D-Bus System Message Bus Socket
| Loaded: loaded
Package: systemd
Version: 37-1
Severity: grave
Justification: renders package unusable
Hi,
By adding init=/bin/systemd to grub2 boot loader the gdm3 display manager does
not
start as usual. Booting with the legacy init, gdm3 works as expected. This has
appeared a few months ago and I simply
Am 25.02.2012 09:28, schrieb Teodor:
root@piti:~# /etc/init.d/gdm3 status
gdm3.service - LSB: GNOME Display Manager
Loaded: loaded (/etc/init.d/gdm3)
Active: active (exited) since Sat, 25 Feb 2012 10:16:34
+0200; 3min 51s ago
Process: 948
5 matches
Mail list logo