Re: localectl list-keymaps : Couldn't find any console keymaps
On Fri, Jul 03, 2015 at 09:26:29AM +0100, Darac Marjal wrote:
> On Thu, Jul 02, 2015 at 11:52:41PM +0200, Alberto Cortés wrote:
> > On Thu, Jul 02, 2015 at 09:53:22PM +0200, Alberto Cortés wrote:
> > > Pretty much what the subject says.
> > >
> > > I'm trying to configure my virtual consoles in Debian Jessie.
> > >
> > > When I ask for a listing of the available keymaps, this is what I get
> > > instead:
> > >
> > > ; localectl list-keymaps
> > > Couldn't find any console keymaps.
> > >
> > > Other localectl incantations seem to be working just fine:
> > >
> > > ; localectl list-locales
> > > C.UTF-8
> > > en_US.utf8
> > >
> > > More info:
> > >
> > > ; aptitude show console-data | egrep ^State
> > > State: installed
> > >
> > > P.S.: It is hard to find information about virtual console
> > > configuration nowadays, any pointer will be helpful, thanks.
> >
> > First, sorry about the subject mistake and change.
> >
> > Now, more info:
> >
> > ; strace localectl list-keymaps 2>&1 | tail -7
> > lstat("/usr/share/kbd/keymaps", 0x7ffceed35a40) = -1 ENOENT (No such file or directory)
> > lstat("/usr/lib/kbd/keymaps", 0x7ffceed35a40) = -1 ENOENT (No such file or directory)
> > lstat("/lib/kbd/keymaps", 0x7ffceed35a40) = -1 ENOENT (No such file or directory)
> > writev(2, [{"Couldn't find any console keymap"..., 34}, {"\n", 1}], 2Couldn't find any console keymaps.
> > ) = 35
> > exit_group(1) = ?
> > +++ exited with 1 +++
> >
> > That directories are not present on my system.
> >
> > The console-data package seems to install some keymaps on other directories
> > though:
>
> That sounds like a bug to me. Check the bug reports for console-data and
> systemd to see if either mentions it and, if not, raise a bug. My gut
> feeling would be that this is a bug in systemd (not because of any
> ill-feeling towards that package, but simply because console-data has
> been around longer than systemd)
Checked and reported [1], thank you.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790955
Reply to: