That is. Manjaro Stable. I don’t know why, but after i try to bind yakuake on that hotkey it’s crushes. Hotkeys in kde settings seems also dosn’t work
I just tested this and it does APPEAR to crash my system. However, while the computer fails to respond to any input switching to a TTY and back to the DE clears it.
I just use F12 to cause Yakuake to drop down; that’s the default.
CTRL + ALT + F12 is for one of the TTYs.
It’s not crashing, it’s switching to an unused TTY - just switch back using Ctl + Alt + F1 etc.
Don’t bind Crtl + Alt + F1-F12 to anything - those bindings are already used for switching TTYs.
Ctrl+Alt+F12 will send you to a graphical TTY session, which is a TTY session that cannot accept text input.
Anytime you press Ctrl+Alt+Any F key you will be sent to a TTY session. Some will be text sessions where you can login via a prompt. On my Plasma system Ctrl+Alt+F1 to F6 take me to text TTY sessions, and Ctrl+Alt+F7 to F12 take me to non-text graphical TTY sessions.
All you need to do to return to your Plasma session is find the TTY session where Plasma is running. In my case, after pressing Ctrl+Alt+F12, I was able to return to Plasma by pressing Ctrl+Alt+F1. Plasma won’t always be on TTY1, so you may have to try Ctrl+Alt+F2 etc until you find it.
Hotkeys was depreciated in Plasma 5 - around 2024…
Normally, to launch a terminal we use CtrlAltT (default is Konsole).
You could use CtrlAltK for Kitty, CtrlAltGfor Ghostty, CtrlAltY for Yakuake, CtrlAltF for Firefox…
But you can’t enter a TTY shortcut and you shouldn’t even see Hotkeys, you should have simply ‘Shortcuts’ since 2024 if I remember rightly…
7 is the first default gui session as mentioned above. Didn’t even know there is 12 (well judging by the above there really isn’t).
On this one:
[brian@BG-IdeaPad ~] $ w
04:44:30 up 11 days, 9:02, 1 user, load average: 0.89, 0.77, 0.80
USER TTY LOGIN@ IDLE JCPU PCPU WHAT
brian tty1 27Sep25 11days 0.12s 0.12s /usr/bin/startplasma-wayland
Whereas my Mint machine has the GUI on TTY7 currently.
interesting … on my Gnome system : TTY1=GDM, TTY2=current session, TTY3-6=putty, TTY7-12 nothing happens, just a black blank screen
On xfce, 1 is the kernel, 2-6 are usable text ttys, 7 is the gui, the rest i do not remember but i do not think they are usable.
In any case, the lesson is clear: never try to assign these keys to anything, it will just not work since those are build in in the kernel and will always have priority.
Me personally i stick to letters for my custom shortcuts and that is my recommendation for newbies. Ctrl-alt-letter, alt-shif-letter, whatever.
Traditionally (using X) 1-6 are text ttys, 7 is the first graphical tty (by default the rest are unused), when you switch user a new graphical session is opened on the next available tty. It used to be fairly common for people to set up tty12 to show the system log.
Wayland has changed that, now boot messages are displayed on tty1, that’s often replaced with the first graphical session (I’ve also seen the first graphical session on tty2). Text ttys go up to 6, 7 seems to be unusable for me (can’t switch to it atm). 8+ are unused by default.
Not sure if the graphical ones just use up a text tty or if a new one gets configured, probably the former.
They’re in the keyboard layout for X/Wayland, but they’re likely hardcoded in other places such as the linux console (aka tty). If I remember correctly I helped someone remap them in X but we couldn’t remap them for the ttys.
EDIT:
Forgot to mention that tty1 is used for boot messages in X too. I think it used to be reconfigured as a normal text tty after boot, or boot messages were done another way, as I’m pretty sure I’ve used tty1 in the past.
Yes there is, but in most cases it’s not configured.
tty12 is the syslog console, where one can see output from the system logger — in Manjaro, this is journald by default — in real-time. In order to activate this, you need to edit /etc/systemd/journald.conf and make sure you have the following two lines… ![]()
ForwardToConsole=yes
TTYPath=/dev/tty12
And then of course, you need to reload the configuration… ![]()
sudo systemctl daemon-reload
Your best resolve is to bind Yakuake to F12 only – as @BG405 has already mentioned, it is afterall the default for Yakuake.
As a “newbie”, please follow the links (below) to help familiarise yourself with the Manjaro forum.
We hope you will enjoy your stay.
Regards.
Welcome to the Manjaro community
As a new or infrequent forum user, please take some time to familiarise yourself with Forum requirements, and the many ways to use the forum to your benefit.
To that end, links are provided (below) - Please use them.
Be prepared to provide outputs from various commands when asked. It’s equally important to provide as much actionable information as possible in your first post, rather than simply indicating there is a problem.
Waiting for others to blindly ask questions can be counter-productive – typically, nobody has a
at their disposal – Instead, please help others to make informed suggestions, based on information you provide.
Update Announcements
The Update Announcements contain important information and a Known Issues and Solutions section that should generally be checked before posting a request for support.
System Information
While information from *-fetch type apps might be fine for someone wishing to buy your computer, for Support purposes it’s better to ask your system directly; ![]()
Output of the inxi command (with appropriate parameters, and formatted according to forum guidelines) will generate information useful for those wishing to help:
inxi --filter --verbosity=8
or the short form (preferred):
inxi -zv8
- inxi man pages (Arch Manual)