Am 08.06.2015 um 14:29 schrieb Michael Biebl:
> Is that actually still an issue?
>> Oct 30 09:19:36
> Is your clock off or is that from an earlier systemd version?
> Which systemd version do you have installed?
Sorry, was somehow confused by the recent closure of Laurent.
--
Why is it that all o
Control: tags -1 moreinfo
Am 30.10.2014 um 20:24 schrieb r.ductor:
> Package: gdm3
> Version: 3.14.0-1
> Severity: minor
>
> Dear Maintainer,
>
> I have kdm as default display manager.
> Systemd starts gdm.service,
> which contains an ExecStartPre assertion default=gdm
> that fails giving a failu
This is fixed here with systemd-215-16 and gdm3-3.14.1-7.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
I have systemd 215-8 (which is now in Testing) and have the same problem
but with gdm3 and lightdm. Here, both lightdm (1.10.3-3) and gdm3
(3.14.1-3) are installed but the former is set to be the default display
manager. I get lines like these:
gdm.service: control process exited, code=exited
On Thu, 30 Oct 2014 20:24:14 +0100 "r.ductor"
wrote:
> Dear Maintainer,
Hello,
> I have kdm as default display manager.
> Systemd starts gdm.service,
> which contains an ExecStartPre assertion default=gdm
> that fails giving a failure log and a failure status.
>
> I do not know if this is a b
I am also affected by this problem. During boot quite a large amount of
error messages are generated about gdm3 failing to start.
signature.asc
Description: OpenPGP digital signature
Package: gdm3
Version: 3.14.0-1
Severity: minor
Dear Maintainer,
I have kdm as default display manager.
Systemd starts gdm.service,
which contains an ExecStartPre assertion default=gdm
that fails giving a failure log and a failure status.
I do not know if this is a bug or a feature,
nor if I sho
7 matches
Mail list logo
