[[!meta copyright="Copyright © 2012, 2013, 2014 Free Software Foundation, Inc."]] [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable id="license" text="Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled [[GNU Free Documentation License|/fdl]]."]]"""]] [[!tag open_issue_documentation]] [[!toc]] # IRC, OFTC, #debian-hurd, 2012-09-24 hello, I'm trying to get familiar with the Hurd and would like to change the keyboard layout in use. It seems all the information I can find (relating to console-driver-xkb) is out of date, with the latest info relating to it being that this package should not be used anymore… does anyone know how changing keyboard layouts currently works? ah, never mind. I assume it doesn't currently work: http://www.gnu.org/software/hurd/hurd/console.htmlq *http://www.gnu.org/software/hurd/hurd/console.html it does actually work simply dpkg-reconfigure keyboard-configuration and reboot (see http://www.debian.org/ports/hurd/hurd-install ) mhm, I got that far — but selecting my layout gave me no joy, even after restart. Seem to be stuck with the layout chosen during installation (d-i). Just to check I'm using the right version — still on the installer isos from 15 July? wait… progress is being made — slowly and subtly… Ok, so the XKBLAYOUT is changing as you described, but XKBVARIANT seems to be ignored. Could this be right? yes, the hurd console only supports keymaps (currently) Ah OK, thanks for your help on this. I imagine this is not something that just requires simple repetitive work, but some actual hacking? to fix that is… some hacking yes # IRC, freenode, #hurd, 2013-07-10 http://xkbcommon.org/ ‘¡û sounds interesting for our console translator # IRC, freenode, #hurd, 2013-10-01 [[!tag open_issue_hurd]] teythoon_: df: `/dev/cons': Operation not supported missing/stub implementation in the console translator? ## IRC, freenode, #hurd, 2013-10-02 pinotree: yes, df does file_statfs which fails # IRC, freenode, #hurd, 2013-10-22 hello hurders! I happened to watch samuel's gnu hackers talk and wanted to start to use the hurd more regularily. However I noticed that when I use the preinstalled image, there seems to be some issue with the console driver when I start emacs the mode line is drawn 3 times above the bottom of the screen is this know or did I miss a step in setting it up? Or should I use the debian installer and start from scratch again? C-Keen: it's probably unknown, and not an issue on your side. Did you try to upgrade to the latest packages? youpi: doing that now my base image is debian-hurd-20130504.img still an issue with the latest packages indeed it seems emacs and the hurd console don't agree on the number of lines... C-Keen: you can set TERM=vt100 to work around the issue ah alright. or TERM=linux youpi: can you start the emacs in X? I get an empty window here I never tried I never use emacs :) I see ;) it seems there's a bug in cud1 indeed what's cud1? see man 5 terminfo yes it's a terminfo problem the hurd console isn't well defined there braunr: actually it seems like a bug in emacs cud may or may not scroll the screen, depending on the implementation # IRC, freenode, #hurd, 2013-12-28 ahem, looks like the last xkb-data package dropped /usr/share/X11/xkb/compat/default :/ braunr: Looks more like an upstream issue; check, e. g., http://cgit.freedesktop.org/xkeyboard-config/commit/?id=882f5470713d. braunr: Slightly more surprising is that xkb-data 2.8 was packaged for Debian last Sunday. While the upstream has released 2.10.1 back in October, as per http://www.x.org/releases/individual/data/xkeyboard-config/. ivanshmakov: http://packages.qa.debian.org/x/xkeyboard-config/news/20131222T160519Z.html gg0: ACK, thanks. (No idea how did I read 2.10.1 as 2.8, as I was looking on essentially the same information.) ## IRC, freenode, #hurd, 2013-12-30 on debian/hurd, with startx, show the error "cannot open keyboard (no such file or directory)" ZenWalker: what version of xkb-data do you have ? braunr: 2.10.1-1 ZenWalker: there is a bug in that package you can confirm it by spotting an error during system startup that mentions a missing "compat/default" file this prevents the hurd console from starting and without the hurd console, xorg can't find the input device hopefully it will be fixed soon braunr: yes, "couldn't open include file "compat/default"" thanks ## IRC, freenode, #hurd, 2013-12-31 youpi1: fyi, xkb-data doesn't provide compat/default, which prevents the hurd console from starting braunr: X works with xkb-data 2.5.1-3 :) maybe xkb-data isn't the problem maybe we need to fix the hurd-console youpi: we should probably fix the hurd with regard to xkb-data before releasing the next packages it's very unlikely that xkb-data will be fixed they say compat/default is unused since march 2012 ## IRC, freenode, #hurd, 2014-01-01 Is anyone else having problems with the console? downgrade xkb-data to http://snapshot.debian.org/package/xkeyboard-config/2.5.1-3/#xkb-data_2.5.1-3 ty ## IRC, freenode, #hurd, 2014-01-04 does anybody know if the fact that aptitude looks shitty on the hurd console is a bug in the console implementation or some broken term{cap,info} config? ncurses is pending a terminfo fix, possibly related you can try to recompile your hurd terminfo entry, adding xenl to it, and see whether it fixes it hmm, just did an aptitude upgrade, and now after a restart the Hurd console does not even start any more (did not mess with my terminfo yet) Couldn't open include file "compat/default" yes, xkb-data broke, downgrade it youpi, to which version? well, the previous one :) (or can aptitude or another tool show me what version I had previously?) you can simply take the but-last on snapshot.debian.org youpi, thanks, that helped. And adding xenl to hurd.ti and recompiling helped, too :) ## IRC, freenode, #hurd, 2014-01-13 Couldn't open include file "compat/default" from the console that has been reported on the ml and as debian bug a workaround is both in the upcoming hurd package as well as in the ones i provide in hurd-ci Any workaround for the hang in the console for now? there is no hang there is simply no getty how come? and the xkb-data problems I thought was causing problems with the hurd console to start, not the mach console. gnu_srs: exactly, the missing xkb data prevents your hurd-console from running # IRC, freenode, #hurd, 2014-02-05 btw, does the console handle other keymaps than the qwerty US one ? Samuel thibault talked about this during his fosdem conference it does check /etc/default/hurd-console how ? I mean which lib does it use, because I face a similar issue with my programms and would like a "smart" way to handle this (meaning not reimplement something doing it worse) thx bu^: xkb I'm not clear with xkb and how much it is related to xorg, I would like to be xorg independant, but the hurd console also should be and it seems to work bu^: xkb is just a library xorg uses it but other applications can use it it just happens to be maintained by x.org people oh ok, nice, I'll look at it we are talking about this one ? http://www.x.org/releases/current/doc/libX11/XKB/xkblib.html yes btw the way special caracters like é or à breaks the backspace (erase) key as it will not count properly the number of caracters on the line and I end up with remaining caracters I can't erase I also started to look for this one but didn't find a proper way to use it as a library http://www.kbd-project.org bu^: probably a bogus locale that just works for me # IRC, freenode, #hurd, 2014-02-25 [[!tag open_issue_hurd]] to reproduce "task f5ca6e40 deallocating an invalid port 1711, most probably a bug." just restart hurd-console