Your message dated Mon, 16 Apr 2012 19:22:47 +0200
with message-id <[email protected]>
and subject line Re: Bug#661217: systemd: gdm3 does not start
has caused the Debian Bug report #661217,
regarding systemd: gdm3 does not start
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
661217: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661217
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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 disabled systemd to have Gnome back.
Today
I checked again to see if this was fixed -> this bug report.
Thanks
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 ExecStart=/etc/init.d/gdm3 start (code=exited,
status=0/SUCCESS)
CGroup: name=systemd:/system/gdm3.service
root@piti:~# /etc/init.d/gdm3 restart
Restarting gdm3 (via systemctl): gdm3.serviceStopping GNOME Display Manager:
gdm3.
Starting GNOME Display Manager: gdm3.
..
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:20:47 +0200; 4s ago
Process: 7573 ExecStop=/etc/init.d/gdm3 stop (code=exited,
status=0/SUCCESS)
Process: 7582 ExecStart=/etc/init.d/gdm3 start (code=exited,
status=0/SUCCESS)
CGroup: name=systemd:/system/gdm3.service
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=ro_RO.UTF-8, LC_CTYPE=ro_RO.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages systemd depends on:
ii initscripts 2.88dsf-22
ii libacl1 2.2.51-5
ii libaudit0 1:1.7.18-1.1
ii libc6 2.13-26
ii libcap2 1:2.22-1
ii libcryptsetup1 2:1.3.0-3.1
ii libdbus-1-3 1.4.18-1
ii libpam0g 1.1.3-7
ii libselinux1 2.1.0-4.1
ii libsystemd-daemon0 37-1
ii libsystemd-login0 37-1
ii libudev0 175-3.1
ii libwrap0 7.6.q-23
ii udev 175-3.1
ii util-linux 2.20.1-3
Versions of packages systemd recommends:
ii libpam-systemd 37-1
Versions of packages systemd suggests:
ii python 2.7.2-10
ii systemd-gui 37-1
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 44-1
On 16.04.2012 18:49, Teodor MICU wrote:
> 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 #[email protected] is necessary.
This was most likely fixed by the following change
* Explicitly order debian-fixup before sysinit.target to prevent a
possible race condition with the creation of sockets.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
