always start on vt1

Could you attach /var/log/lightdm/lightdm.log?

Here's the log.

Ok, the config file was just wrong (I missed the move from /etc/lightdm.conf to /etc/lightdm/lightdm.conf). So I was using the “new” config file with vt=active, and lightdm indeed started on vt1. But what puzzles me is that it will happily start on vt1 even if there's something else already running there (like a tty), which looks just wrong to me, since it'll fail sooner or later.

Ok, on one box (at least), when forcing the vt to 7 (or 8) I get:

[ 288.968] (++) using VT number 7

[ 288.968] (WW) xf86OpenConsole: setpgid failed: Operation not permitted
[ 288.968] (WW) xf86OpenConsole: setsid failed: Operation not permitted

in /var/log/Xorg.0.log

No idea what happens but that means I can't start lightdm at all.

Ok, don't pay attention to last comment, it looks like #799069

Ok, it was working fine in 0.4.1 and broke *again* in 0.4.2.

I understand the intention to have a seamless interaction with plymouth, but *please* don't force lightdm on vt1, *even* if plymouth is run there. On Debian and derivatives it'll be replace by a getty and no, we don't want to replace that tty, people expect it there. X should start on vt7, that's all.

So either make the “replace plymouth on the same vt” optional, or make “minimum-vt” enforced for *all* startups. But right now it just can't work.

Sorry, the tone might be a bit rude, but it's quite hard to have a working setup for more than few weeks right now. I had the intention to replace the gdm2 setup in Debian Xfce by lightDM, but right now it's just not possible.

Ok, this patch implements a simple heuristic. If minimum-vt is defined, it'll never start on a vt below that, even if plymouth is running and has an active-vt.

It works fine with minimum-vt=7 (X starts with -vt 7) and with minimum-vt commented (X starts with -vt 1).

Hi Yves-Alexis,

Sorry to hear of your problems. I'm suprised it was working in 0.4.1 - there wasn't any fixes in this area!?

The patch looks like good behaviour, I'm still interested in why it is not working in your situation - you have Plymouth running on a VT that will be replaced with getty? Can you attach a log from this case? (In Ubuntu Plymouth always appears to be running on VT7).

Thanks,

Committed patch with some changes to make logging better

Thank you!