Description of problem: lxdm logs on tty1, while tty8 just been standardized. Just change the following line in lxdm.conf arg=/usr/bin/X -background vt1 instead of vt8 Version-Release number of selected component (if applicable): lxdm-0.4.1-4
IIRC it's more a bug from systemd
CC: (none) => dmorganec, fundawang, mageia, mageia
What do you mean by "tty8 just been standardized"? X certainly *should* be starting on vt1... but there are sometimes bugs where restarting it means it starts on vt7 or 8 which I'm looking into.
Depends on: (none) => 4406
(In reply to comment #2) > What do you mean by "tty8 just been standardized"? > Sorry. It is about a mistranslation. In fact, I had read that vt1 is used with the other display manager. > X certainly *should* be starting on vt1... but there are sometimes bugs where > restarting it means it starts on vt7 or 8 which I'm looking into. The line "arg=/usr/bin/X -background vt8 " was put to by-pass one bug ( 3578 ) because it was not possible any more to connect. In fact, at present, this line is not necessary any more. She can be again commented, as in the configuration file of origin.
Summary: lxdm logs on tty1, while tty8 just been standardized => lxdm logs on tty8, while tty1 just been standardized
Assignee: bugsquad => oliver.bgr
I think Oliver was working on it. Reassigning to him.
Status: NEW => ASSIGNED
Should be fixed in current release of lxdm.
Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED
Yup, we confirmed that the correct fix here is to add the following lines to the "[server]" section of the standard lxdm.conf file: [server] active_vt=1 args=/usr/bin/X -background This was done in the following patch: http://svnweb.mageia.org/packages/cauldron/lxdm/current/SOURCES/lxdm-0.4.1-mga-use_vt1.patch?r1=177120&r2=216038 As a side note, the current /etc/X11/prefdm, does not have specific support for lxdm. This means that plymouth will be stopped before lxdm is run. Looking at the code in lxdm, it appears to be perfectly capable of stopping plymouth by itself, and thus we should probably also fix initscripts package to reflect this. I will look into that (tho' I need to test that it really does stop plymouth first :))