Re: Scroll Lock on VT prevents reboot/shutdown
Hi.
On Fri, 30 Sep 2016 10:09:25 -0300
Henrique de Moraes Holschuh <hmh@debian.org> wrote:
> On Fri, 30 Sep 2016, Reco wrote:
> > On Thu, Sep 29, 2016 at 10:03:31PM +0000, Matt Sickler wrote:
> > > I'm not sure which package this bug should be filed against, partially because I'm not entirely sure of the root cause. I'm able to replicate it on our systems every time, though I have not tried on a fresh install of Debian - our images aren't really that much different anyway. We don't have a GUI installed, just text mode or whatever you want to call it. I've spent hours googling and I have not found anyone else affected by this, nor did I find anything in BTS.
> > <skip>
> > > Could someone confirm that this happens on more than just my systems and/or let me know what package I should file the bug against?
> >
> > Please run "dpkg -S /sbin/shutdown", and file a bug against a package
> > found. I suspect that this issue must be linked somehow to systemd's
> > console handling, because I cannot reproduce the behavior you describe
> > (but I don't use systemd).
>
> Hmm, careful there. sysv-rc console handling isn't much better, I don't
> know when we regressed it or why anymore, it was on lenny or even
> earlier, but...
I can get a Unicode VT console without any hassle with sysvinit.
I can get my hosts rebooted without fiddling with stty with sysvinit.
I cannot do both (as of jessie) with systemd.
Presumably systemd has its merits, but VT handling is not one of them.
I agree that there're many cornercases in sysvinit's VT handling, but
inability to shut down and reboot is always a touchy subject to me.
But I'm not intending to start a flamewar here (although it's a Friday
night ;), this 'unable to reboot' thing is clearly a minor bug ether in
systemd or jessie's kernel.
> If you ever need to log in the console before getty ran
> (i.e. in single-user mode, etc), *always* run "stty sane" as the first
> thing.
> Otherwise, you might find yourself on a shell that doesn't have many of
> the interrupt signals working from the vty.
I don't know as I never tried that. Either getty is working for me or
I'm booting with init=/bin/sh. But thank you for the advise.
Reco
Reply to: