From: valadaa48 <valadaa48@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Cannot chvt to tty2 if a framebuffer/kms app is running on tty1
Date: Tue, 07 Jul 2020 19:57:03 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23456@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 516 bytes --]
New issue by valadaa48 on void-packages repository
https://github.com/void-linux/void-packages/issues/23456
Description:
### System
* xuname:
Void 4.4.189_2 aarch64 Unknown notuptodate rDFFF
* package:
N/A
### Expected behavior
Should show tty2 login. I confirm this works on systemd based systems.
### Actual behavior
Does not switch tty's. Command works if app is stopped.
### Steps to reproduce the behavior
ssh in and run `sudo chvt 2`. agetty-tty2 is running as a service.
next reply other threads:[~2020-07-07 17:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 17:57 valadaa48 [this message]
2021-01-21 17:53 ` ericonr
2021-01-22 10:48 ` travankor
2022-04-17 2:06 ` github-actions
2022-05-01 2:13 ` [ISSUE] [CLOSED] " github-actions
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23456@inbox.vuxu.org \
--to=valadaa48@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).