Bug 4400

Summary:	lxdm logs on tty8, while tty1 just been standardized
Product:	Mageia	Reporter:	Georges Eckenschwiller <paiiou>
Component:	RPM Packages	Assignee:	Oliver Burger <oliver.bgr>
Status:	RESOLVED FIXED	QA Contact:
Severity:	minor
Priority:	Normal	CC:	dmorganec, fundawang, mageia, mageia
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	lxdm-0.4.1-4	CVE:
Status comment:
Bug Depends on:	4406
Bug Blocks:

Description Georges Eckenschwiller 2012-02-03 16:37:48 CET

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

Comment 1 Manuel Hiebel 2012-02-03 19:09:44 CET

IIRC it's more a bug from systemd

CC: (none) => dmorganec, fundawang, mageia, mageia

Comment 2 Colin Guthrie 2012-02-04 14:20:11 CET

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.

Georges Eckenschwiller 2012-02-04 17:38:09 CET

Depends on: (none) => 4406

Comment 3 Georges Eckenschwiller 2012-02-05 10:46:48 CET

(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.

Georges Eckenschwiller 2012-02-15 11:39:08 CET

Summary: lxdm logs on tty1, while tty8 just been standardized => lxdm logs on tty8, while tty1 just been standardized

Damien Lallement 2012-02-29 17:11:41 CET

Assignee: bugsquad => oliver.bgr

Comment 4 Damien Lallement 2012-02-29 17:12:14 CET

I think Oliver was working on it. Reassigning to him.

Status: NEW => ASSIGNED

Comment 5 Oliver Burger 2012-02-29 17:18:11 CET

Should be fixed in current release of lxdm.

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED

Comment 6 Colin Guthrie 2012-02-29 17:19:09 CET

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 :))