Hi Simon,
Simon McVittie wrote:
On 01/03/15 21:58, Simon McVittie wrote:
Cc kdm, lightdm, slim, wdm maintainers to warn you that you might be
getting a RC bug (with a simple fix, add one 3-line file) assigned or
cloned to your DM implementations.
The real bug
I don't see that as bug,
Control: reassign 766462 gdm3
Control: affects 766462 kdm wdm plymouth
Control: tags 766462 = patch pending
On 01/03/15 21:58, Simon McVittie wrote:
Cc kdm, lightdm, slim, wdm maintainers to warn you that you might be
getting a RC bug (with a simple fix, add one 3-line file) assigned or
cloned
On 11/03/15 12:47, Axel Beckert wrote:
Simon McVittie wrote:
The real bug
I don't see that as bug, rather as missing feature.
You say tomato, I say tomato[en_GB] :-)
is that kdm and wdm do not participate in the shared
display-manager.service symlink management (#755359, #761642) which
On 01/03/15 21:58, Simon McVittie wrote:
On Sun, 09 Nov 2014 at 12:11:49 +0100, Laurent Bigonville wrote:
This bug is triggered by the fact that GDM systemd service is enabled
while KDM is also enabled. GDM .service file explicitly conflicts with
plymouth-quit.service as it calls plymouth
On mar., 2015-03-10 at 10:02 +, Simon McVittie wrote:
slim and lightdm do have native systemd .service files, but don't have
those relationships, which I think is probably a bug in those DMs'
service files
If they do not interact with plymouth themselves like gdm does, then it
is
On mar., 2015-03-03 at 03:59 +, Mike Gabriel wrote:
I am quite positive that some missing gettys because of two DMs being
installed in parallel (or some similar normal thing that people might
do) will definitely be worth a freeze exception.
IMHO, if gettys don't come up properly, the
On 03/03/15 09:52, Yves-Alexis Perez wrote:
On mar., 2015-03-03 at 03:59 +, Mike Gabriel wrote:
IMHO, if gettys don't come up properly, the system is rather broken
and this is a no-go for jessie.
Sure, but I had the impression that this wasn't the case for lightdm
(and slim),
On mar., 2015-03-03 at 09:59 +, Simon McVittie wrote:
* have systemd as init
* install plymouth, gdm3 and your favourite non-GDM DM implementation
(kdm in the original bug report)
Ok, I'm missing gdm3 here, so I'll try to install it and report back on
the situation.
* select the
Hi all, hi Yves-Alexis,
On Mo 02 Mär 2015 21:30:49 CET, Yves-Alexis Perez wrote:
On dim., 2015-03-01 at 21:58 +, Simon McVittie wrote:
slim and lightdm do have native systemd .service files, but don't have
those relationships, which I think is probably a bug in those DMs'
service files;
On dim., 2015-03-01 at 21:58 +, Simon McVittie wrote:
slim and lightdm do have native systemd .service files, but don't have
those relationships, which I think is probably a bug in those DMs'
service files; they should probably gain those lines too. However,
because they participate in
Cc kdm, lightdm, slim, wdm maintainers to warn you that you might be
getting a RC bug (with a simple fix, add one 3-line file) assigned or
cloned to your DM implementations.
Peter Palfrader wrote:
I just upgraded to jessie, and with plymouth installed, I don't get
any gettys/login prompts on
On Thu, 23 Oct 2014 12:13:44 +0200 Peter Palfrader wea...@debian.org
wrote:
Package: plymouth
Version: 0.9.0-7
Severity: serious
Hi,
I just upgraded to jessie, and with plymouth installed, I don't get
any gettys/login prompts on any of the VCs. kdm starts up and gives
me an X
Hi,
Peter Palfrader wrote (06 Nov 2014 20:48:15 GMT) :
On Thu, 06 Nov 2014, Peter Palfrader wrote:
Did that, didn't get a logfile.
} weasel@defiant:/var/log$ cat /proc/cmdline
} BOOT_IMAGE=/vmlinuz-3.16-3-amd64 root=/dev/mapper/vg0-root ro splash quiet
plymouth.debug
}
On Tue, 28 Oct 2014, Laurent Bigonville wrote:
Could you please add a bit more information here? Which architectures
are you talking about? is your system completely up-to-date? Which init
system are you using?
amd64, completely up to date jessie, /sbin/init is provided by systemd-sysv.
On Thu, 06 Nov 2014, Peter Palfrader wrote:
Did that, didn't get a logfile.
} weasel@defiant:/var/log$ cat /proc/cmdline
} BOOT_IMAGE=/vmlinuz-3.16-3-amd64 root=/dev/mapper/vg0-root ro splash quiet
plymouth.debug
} weasel@defiant:/var/log$ ls -l pl*
} zsh: no matches found: pl*
tag 766462 + moreinfo unreproducible
thanks
Hello Peter,
Could you please add a bit more information here? Which architectures
are you talking about? is your system completely up-to-date? Which init
system are you using?
I definitely cannot reproduce this on my amd64 machine running an
On Tue, 28 Oct 2014, Laurent Bigonville wrote:
tag 766462 + moreinfo unreproducible
thanks
Hello Peter,
Could you please add a bit more information here? Which architectures
are you talking about? is your system completely up-to-date? Which init
system are you using?
amd64, current
Package: plymouth
Version: 0.9.0-7
Severity: serious
Hi,
I just upgraded to jessie, and with plymouth installed, I don't get
any gettys/login prompts on any of the VCs. kdm starts up and gives me
an X login-prompt, but none of the consoles do.
Purging plymoth gives me login prompts on the VCs.
18 matches
Mail list logo
