On 2013-07-14 19:52 +0200, Csanyi Pal wrote: > Sven Joachim <[email protected]> writes: > >> On 2013-07-14 19:22 +0200, Csanyi Pal wrote: >> >>> Hi, >>> >>> my system is Debian GNU/Linux unstable (sid). >>> >>> In the file /etc/default/keyboard the followings setup is present: >>> XKBMODEL="pc105" >>> XKBLAYOUT="hu,hr,rs" >>> XKBVARIANT="nodeadkeys" >>> XKBOPTIONS="grp:rwin_toggle,terminate:ctrl_alt_bksp,grp_led:scroll" >>> >>> BACKSPACE="guess" >>> >>> This setup works sofar, but today suddenly stop working, after I upgrade >>> my SID system. >>> >>> How can I solve this problem? >> >> Does it help to run setupcon by hand? > > No, when I run on the console ( not on X window system's xterm ) the > 'sudo setupcon', it doesn't help.
What does "setupcon -v" print? >>> Is this a bug? If yes, in which package is the bug? >> >> Don't know, but today a new sysvinit version entered unstable. Did the >> other init scripts run at boot time? > > Which init scripts do you mean? The ones in /etc/init.d. But if you can still log in as a normal user and setupcon does not work when run manually, the problem is most likely unrelated to sysvinit. There was a console-setup upload yesterday, but the changelog looks rather innocouos: ,---- | console-setup (1.94) unstable; urgency=low | | [ Dmitrijs Ledkovs ] | * Set debian source format to '3.0 (native)'. | * Bump debhelper compat level to 9. | * Set Vcs-* to canonical format. | | -- Christian Perrier <[email protected]> Sat, 13 Jul 2013 12:24:32 +0200 `---- Cheers, Sven -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
