On Saturday 02 November 2013, Istvan Gabor wrote:

Istvan Gabor írta:

...

Hello:

Frequently my openSUSE 12.2 starts the graphical screen on vt7 (instead of vt8).

Correction:

I mixed up, of course it is the opposite, the GUI starts on vt8 instead of vt7.

I have also noticed it still on 13.1. It's very annoying. cu, Rudi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2013-11-02 10:34 (GMT-0400) Carlos E. R. composed:

It is related to plymouth, I understand. If you disable/remove it, the problem disappears. Of course, you get no boot nice animation...

ISTR this happening to me long ago even though I never have Plymouth installed in openSUSE except by forgetting to taboo it during installation. X on tty8 hasn't happened to me in a long time except on purpose as a second X instance. Not having it happen any more may be because I force gettys to start on ttys1-6 during init instead of allowing them to be created on demand the systemd way, which may be dispensing with the race condition that causes use of tty8 instead of tty7 for the display manager. I run the following script (which I keep in /bin in the partition I have mounted to /usr/local/, and thus in $PATH) one time after system installation to get the gettys started at init time: http://fm.no-ip.com/Share/gettysmk.sh The script does something else too, so you might want to modify it before use: It causes tty1 not to clear when init finishes. To undo what the script does, simply delete the 6 new symlinks it made and restore the original that it renamed, thus: mv /etc/systemd/system/getty.target.wants/getty@tty1.service-orig /etc/systemd/system/getty.target.wants/getty@tty1.service Naturally this script shouldn't help your X on tty8 problem if simply disabling Plymouth works for you, but if you're like me, you don't like waiting for on demand gettys to start when you want to use one. Originally I was also seeing in some cases X running on tty1, tty4, tty2 or tty5 instead of tty7, but that may have been only in Fedora and/or Mageia, and having all 6 ttys prestarted like with sysvinit forced the DM back to tty7. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Felix Miata írta:

On 2013-11-02 10:34 (GMT-0400) Carlos E. R. composed:

...

It is related to plymouth, I understand. If you disable/remove it, the problem disappears. Of course, you get no boot nice animation...

ISTR this happening to me long ago even though I never have Plymouth installed in openSUSE except by forgetting to taboo it during installation. X on tty8 hasn't happened to me in a long time except on purpose as a second X instance.

Not having it happen any more may be because I force gettys to start on ttys1-6 during init instead of allowing them to be created on demand the systemd way, which may be dispensing with the race condition that causes use of tty8 instead of tty7 for the display manager. I run the following script (which I keep in /bin in the partition I have mounted to /usr/local/, and thus in $PATH) one time after system installation to get the gettys started at init time:

http://fm.no-ip.com/Share/gettysmk.sh

The script does something else too, so you might want to modify it before use: It causes tty1 not to clear when init finishes. To undo what the script does, simply delete the 6 new symlinks it made and restore the original that it renamed, thus:

mv /etc/systemd/system/getty.target.wants/getty@tty1.service-orig /etc/systemd/system/getty.target.wants/getty@tty1.service

Naturally this script shouldn't help your X on tty8 problem if simply disabling Plymouth works for you, but if you're like me, you don't like waiting for on demand gettys to start when you want to use one. Originally I was also seeing in some cases X running on tty1, tty4, tty2 or tty5 instead of tty7, but that may have been only in Fedora and/or Mageia, and having all 6 ttys prestarted like with sysvinit forced the DM back to tty7.

Thank you Felix. I don't think that this is a plymouth issue. See my answer to Carlos' message. I will try the script. What about my other question: How can I restart X forcing it to use vt7? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Felix Miata írta:

On 2013-11-03 13:40 (GMT+0100) Istvan Gabor composed:

...

What about my other question: How can I restart X forcing it to use vt7?

One way (if vt7 isn't committed already somehow):

startx -- :0

What DM do you use? Could it be that its config is missing a :0 specification for default location that it should have? In early implementations of systemd, :0 wasn't always definitively equated to vt7.

I use KDM3 desktop manager. Where to look for the config file you mentioned? But I hope I won't have to mess with this again, after removing plymouth. Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

"Carlos E. R." írta:

On 2013-11-02 15:29, Ruediger Meier wrote:

...

I have also noticed it still on 13.1. It's very annoying.

It is related to plymouth, I understand. If you disable/remove it, the problem disappears. Of course, you get no boot nice animation...

I removed all plymouth* packages from my system. I still have a graphical boot screen, the same as before (with the moving white bubbles). But there is one important difference: Previously (when plymouth was installed) the graphical boot screen was shown on vt1, it disappeared after boot, and vt1 turned to a normal console login screen. If the GUI login started on vt8, vt7 remained blank with blinking underscore at the top left corner. Now (without plymouth) the graphical boot screen is shown on vt7, it does not disappear after boot has finished (that is it stays on vt7), and vt8 is the GUI login screen. Does not this indicate that it is not plymouth that causes the issue? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

"Carlos E. R." írta:

On 2013-11-03 13:35, Istvan Gabor wrote:

...

Does not this indicate that it is not plymouth that causes the issue?

Did you rebuild initrd?

I forgot it. I rebuilt it in the meantime and now I have reasonable boot screen. Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Felix Miata írta:

On 2013-11-03 14:22 (GMT+0100) Istvan Gabor composed:

...

"Carlos E. R." composed:

...

...

Did you rebuild initrd?

...

I forgot it. I rebuilt it in the meantime and now I have reasonable boot screen.

And where is X running?

Now X (desktop :0) starts on vt7. I have rebooted (only) 3-4 times to check it, but so far it is consistent. (By reasonable boot screen I meant that I have a graphical boot screen, though without a progress bar, and it occupies vt1, not vt7.) Second X (desktop :1) is on vt8. (I use frequently two desktops simultaneously, occasionally even three.) Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 11/04/2013 09:35 AM, David Haller pecked at the keyboard and wrote:

Hello,

On Fri, 01 Nov 2013, Istvan Gabor wrote:

...

2. How can I have my system to start the graphical window always on vt7 at boot?

==== /etc/systemd/logind.conf ==== NAutoVTs=6 ReserveVT=6 ==== /etc/X11/xdm/Xservers ==== :0 local /usr/bin/X [-nolisten tcp -br] vt7 ====

HTH, -dnh

And what is the magic command that is used to get back to the graphic session after using <ctrl><alt>F1 to go to tty1? I went to tty1 and any combination of <cntr><alt> or <alt> F2-F12 did nothing. openSUSE 13.1 RC2 installed fresh. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* tooth pik [11-04-13 17:34]: [...]

dunno about you, but for me (os 12.2) it mattered whether I used the right or the left <CTRL><ALT> with <F7> -- with the right pair, nothing happened -- with the left, I got back straight away -- go figure

simple explanation: right <alt> is <compose> ie: <rt-alt> != <alt> -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 11/04/2013 07:34 PM, Patrick Shanahan pecked at the keyboard and wrote:

* tooth pik [11-04-13 17:34]: [...]

...

dunno about you, but for me (os 12.2) it mattered whether I used the right or the left <CTRL><ALT> with <F7> -- with the right pair, nothing happened -- with the left, I got back straight away -- go figure

simple explanation: right <alt> is <compose> ie: <rt-alt> != <alt>

YA it worked for me in 12.2 as well, but this is now 13.1 -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org