On Thu, Nov 13, 2025 at 12:42 PM Jocelyn Falempe <[email protected]> wrote: > > On 13/11/2025 17:15, Neal Gompa wrote: > > On Thu, Nov 13, 2025 at 10:31 AM Jonathan Wakely <[email protected]> wrote: > >> > >> On Thu, 13 Nov 2025 at 14:35, Allison King via devel-announce > >> <[email protected]> wrote: > >>> > >>> Wiki: https://fedoraproject.org/wiki/Changes/UseKmsconVTConsole > >>> > >>> Discussion Thread: https://discussion.fedoraproject.org/t/172602 > >>> > >>> **This is a proposed Change for Fedora Linux.** > >>> This document represents a proposed Change. As part of the Changes > >>> process, proposals are publicly announced in order to receive community > >>> feedback. This proposal will only be implemented if approved by the > >>> Fedora Engineering Steering Committee. > >>> > >>> == Summary == > >>> This change is to replace the kernel console '''fbcon''' with the > >>> userspace console '''kmscon''' in Fedora, to provide an enhanced and more > >>> secure console for Fedora users. > >>> The long term goal is also to deprecate fbcon/fbdev emulation in the > >>> kernel, and this is the first step in this direction. > >> > >> Generally I think this sounds like a good change... > >> > >>> == How To Test == > >>> Press Ctrl+alt+F3 to switch to the VT console. > >>> Login and check if it's running kmscon with ''ps aux | grep tty3'' > >> > >> Maybe it's obvious if you are actually running kmscon, but I read this > >> and wondered how I would check. What is the expected output of this > >> command? How would it differ from what I see today on F42? > >> > >> Presumably I would I see a kmscon process running on tty3? It might > >> improve the change proposal to say something like "You should see a > >> line in the output showing a kmscon process". > >> > >> > >>> ==== Caveats ==== > >>> * Starting graphical application from the console (like "startx") won't > >>> work, but you can work around it by using the script ''kmscon-launch-gui > >>> startx'' > >> > >> I don't remember the last time I needed to run startx but what is the > >> failure mode if you do run startx from kmscon? Is the > >> kmscon-launch-gui command discoverable for users who do want to use > >> startx or similar commands? > >> > > > > I know there are people who use startplasma to launch the Plasma > > Desktop by hand (since it's a supported method to launch Plasma > > Wayland). Does that also fail with kmscon? If so, does that mean we > > need wrappers to ensure people don't have to figure this out? > > > > I don't think the kmscon-launch-gui command is ergonomic or > > discoverable, so we probably need to adapt things instead. > > Maybe the easiest way is to adapt startplasma script to use > kmscon-launch-gui if started from kmscon. > > The problem is currently kmscon set the $TERM to xterm-256color for > compatibility reason, so I'm not sure how to reliably check that the > script is started from kmscon. >
Maybe kmscon itself should set a brand new variable we can check for. Something like TERM_SESSION_TYPE=KMS similar to the XDG_SESSION_TYPE variable. It would need to be cleared when it dies, so it doesn't get inherited by replacement sessions. -- 真実はいつも一つ！/ Always, there's only one truth! -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
