Hasn't this been fixed in FC long time ago?

CC: (none) => mageia, thierry.vignaud
Assignee: bugsquad => nicolas.lecureuil

i don't reproduce this, i think this is fixed in mageia now.

claire do you still reproduce ?

(In reply to comment #1)
> Hasn't this been fixed in FC long time ago?

Keep in mind that fedora now uses quite a different mechanism to start DE's (they dropped the whole prefdm stuff in favour of a systemd-based unit alias system). I'll look into switching to something similar for mga4 but not going to do that for mga3. That said if kdm needed patching then they should likely all be applied to our version too.

We had bigger things to worry about in beta1 so I didn't check this.

I can do so. Anther install \o/

Yes this is still valid. Checked with a VBox install.

Whiteboard: 3alpha3 => 3alpha3 3beta1

I do *not* have it in my 3beta2 KDE install.
Do you still have it, Claire?

However, it is valid for my Mageia2KDE preferred desktop pc and for the Mga2KDE laptop of a friend.

My friend's laptop doesn't always do the auto-switching to tty2 on boot-up, and she isn't good at pressing alt+ctrl+F2 in a way that works :(

CC: (none) => marja11
Hardware: x86_64 => All
Whiteboard: 3alpha3 3beta1 => 3alpha3 3beta1 MGA2TOO

I'll check it now Marja

Confirmed valid from the 3beta2 installer dvd (no updates installed)

Fresh install Mageia-5-beta2-dual-DVD in VM. No updates.

who
nic      :0           2015-02-12 09:03 (:0)
nic      pts/0        2015-02-12 12:56 (:0.0)

Close?

CC: (none) => nic

(In reply to Nic Baxter from comment #9)
> Fresh install Mageia-5-beta2-dual-DVD in VM. No updates.
> 
> who
> nic      :0           2015-02-12 09:03 (:0)
> nic      pts/0        2015-02-12 12:56 (:0.0)
> 
> Close?

It still starts on tty2 here (updated cauldron that started as 5alpha1), but I don't see the problem if you're auto-switched to tty2, which now always happens. I haven't seen a system that did not do that since 2013.

I can't think of a reason why it should start on tty1, unless for someone who likes to work on 5 ttys at the same time (he'll only have four, tty1 here shows system messages from boot-up, but no prompt).

@ Nicolas
WDYT? Close as wontfix?

replying to a question that was mailed to me:

> Maybe this is a little beyond me. How does one know the tty at boot?
> When I have logged in I can crt-alt-F2 to get to tty2 and then crt-altF1
> to get back to xorg on tty1. Is it different on your computer or am I
> misunderstanding the issue?


Well, here ctrl-alt-F2 does nothing, I cannot go to tty2, because that's where I already am.
However, I can go to tty1 and see the boot messages, to tty3-6 and get login prompts on each of them, and then ctrl-alt-F2 will take me back to KDE again.

Yeah it's certainly bad for consistency. Ultimately *something* must be hogging tty1. We should try and find out what and stop it such that KDM/KDE etc do actually start it.

I really wish there was more shared plumbing layers between DEs for bringing up X. It's such a mess under the hood :(

Hopefully as the world moves to Wayland it'll get a lot nicer. Also very much looking forward to ditching kernel tty handling and having it all in userspace with consoled (which handles sessions properly, has properly localisation, font handling and supports hi-dpi screens - one for MGA6).

(anyway, just to echo others comments, it's not crazy critical but would be a nice one to fix).

Isn't there a systemd unit called shutdown-plymouth or something like that ?  It sounds like DM isn't waiting for that to get plymouth off of tty1 in time for DM to grab it.

CC: (none) => ftg

plymouth-quit-wait.service? If so that's only needed for DMs that do not properly implement handover from plymouth. I know kdm, and gdm and various others do that and thus they specifically tell plymouth to quit so these units in systemd are kinda redundant in those cases. That's not to say it's not still related to plymouth of course... :p

OK. back to Mageia-5-beta2-dual-DVD install.
I am definately starting in tty1.
There are no boot messages and ctrl-alt-F2-F6 gives me login prompts. I have tested with kdm, gdm & lxdm, all the same. So it appears this not no longer current.
Has there been a change with the systemd logging level which stops boot messages on tty1?

(In reply to Nic Baxter from comment #16)
> OK. back to Mageia-5-beta2-dual-DVD install.
> I am definately starting in tty1.


Just checked a Mageia5beta3 install on the same machine: there KDE starts on tty1
So maybe it did indeed get solved between 5 alpha and 5 beta (or its occurence depends on something I'm not aware of)

I don't see it on any fresh installs any more, so closing since no one else still saw it

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