User avatar
paulwratt
Posts: 83
Joined: Fri Jun 12, 2015 12:15 am

virtual consoles keys not working

Thu Apr 20, 2017 12:59 am

I updated raspbian over the Easter weekend and now my virtual consoles are not working (again)

last time I just enabled (the removed) consoles in console-setup

but this time nothing

I even went to extreme of removing plymouth (can somethimes interfere with VT's)

and I cant even bring up VT1 when X is running (presumably on VT7)

what has changed (again)

???
Last edited by paulwratt on Thu Apr 20, 2017 9:27 am, edited 1 time in total.

User avatar
paulwratt
Posts: 83
Joined: Fri Jun 12, 2015 12:15 am

Re: virtual consoles keys not working

Thu Apr 20, 2017 9:27 am

CTRL+ALT+DEL works from the console, but not any other key combos

without plymouth, I know have "started TTYx " messages

consoles are working (chvt)

I have another OS (pipaOS) that I also updated on the weekend, it has X too, but no problems with key combos (or virtual consoles)

the only difference between them is Raspbian is set to auto-login to console (pipaOS is standard login prompt)

I cant see any difference in either /etc/systemd or /lib/systemd

if this was Wheezy, "edit /etc/initrc" would be enough to fix it

Anyone have any ideas

Paul

User avatar
paulwratt
Posts: 83
Joined: Fri Jun 12, 2015 12:15 am

Re: virtual consoles keys not working

Tue Apr 25, 2017 9:22 am

no one know how to fix this? or has comments ?
Last edited by paulwratt on Tue Apr 25, 2017 10:26 am, edited 1 time in total.

User avatar
PeterO
Posts: 4750
Joined: Sun Jul 22, 2012 4:14 pm

Re: virtual consoles keys not working

Tue Apr 25, 2017 9:28 am

I can't help because on recently built 2017-04-10-raspbian-jessie machine the virtual consoles are working just fine without any changes to the default settings.
Ctl-Alt-Fx work just fine.

PeterO
Discoverer of the PI2 XENON DEATH FLASH!
Interests: C,Python,PIC,Electronics,Ham Radio (G0DZB),1960s British Computers.
"The primary requirement (as we've always seen in your examples) is that the code is readable. " Dougie Lawson

User avatar
paulwratt
Posts: 83
Joined: Fri Jun 12, 2015 12:15 am

Re: virtual consoles keys not working

Tue Apr 25, 2017 10:26 am

I ave tried to find SystemD documentation for this, no luck on the keys

it seems X now runs by default on VT1 (as opposed to traditional VT7 started from VT1)

All reference via search engines are for non-systemd (or pre-systemd)

it also appears that there is a "new" dynamic VTx creation, in that they are not actually created until they are "swithed to"

It seems strange that no one has run into this issue yet, then again (daily) Pi users may just get feed up an install clean SD image, and start from scratch again (there are other issues to, including but not limited to (missing) menu items, (destructive) theme updates, etc)

Some ideas would be appreciated

Paul

PS PeterO: thanks..

User avatar
PeterO
Posts: 4750
Joined: Sun Jul 22, 2012 4:14 pm

Re: virtual consoles keys not working

Tue Apr 25, 2017 10:44 am

paulwratt wrote: it seems X now runs by default on VT1 (as opposed to traditional VT7 started from VT1)
X is still on VT7 on my PI, and it's VT8 on this MINT-17 machine I'm using to type this !

Can you try a fresh install on a SDcard ? Maybe you've changed something which has had unexpected consequences ?

PeterO
Discoverer of the PI2 XENON DEATH FLASH!
Interests: C,Python,PIC,Electronics,Ham Radio (G0DZB),1960s British Computers.
"The primary requirement (as we've always seen in your examples) is that the code is readable. " Dougie Lawson

Martin Frezman
Posts: 1020
Joined: Mon Oct 31, 2016 10:05 am

Re: virtual consoles keys not working

Tue Apr 25, 2017 10:53 am

Note: None of what I write below has direct bearing on OP's actual question/problem. It is in regards to the X server running on VT1 instead of VT7.

The change has to do with the latest innovation in security: Running the X server not setuid root. This, it is claimed, is more secure (on the general assumption that the fewer setuid programs you have, the better), but a side effect of the change is that the X server ends up running on the same VT from which it was started (presumably, b/c it doesn't have the privs necessary to allocate and use a new/different one).

I first noticed this behavior (on the Pi) when running Arch Linux.
If this post appears in the wrong forums category, my apologies.

Return to “Troubleshooting”