After a `apt upgrade`, the problems seems fixed
The upgraded packages are
* apt apt-utils cpio libapt-pkg6.0 libatspi2.0-0 libc-bin libc-l10n
libc0.3 libdw1 libedit2 libelf1 libepoxy0 libgdk-pixbuf-2.0-0
libgdk-pixbuf2.0-common libglib2.0-0 libidn2-0 locales*
El mar, 17 ago 2021 a las 0:56
Almudena Garcia, le mar. 17 août 2021 00:52:15 +0200, a ecrit:
> ups, wait to translate
>
> pruebas@debian:~$ sudo dpkg-reconfigure hurd
> Setting up translators: /hurd/exec /hurd/proxy-defpager /hurd/pflocal (+link)
> inet (+link) inet6 (+link) /hurd/pci-arbiter /hurd/acpi /hurd/shutdown /hurd/
>
ups, wait to translate
*pruebas@debian:~$ sudo dpkg-reconfigure hurdSetting up translators:
/hurd/exec /hurd/proxy-defpager /hurd/pflocal (+link) inet (+link) inet6
(+link) /hurd/pci-arbiter /hurd/acpi /hurd/shutdown /hurd/password
crash-kill crash-suspend crash-dump-core crash.Creating d
> dpkg-reconfigure hurd
It shows many errors
*pruebas@debian:~$ sudo dpkg-reconfigure hurd*
*[sudo] password for pruebas: Setting up translators: /hurd/exec
/hurd/proxy-defpager /hurd/pflocal (+link) inet (+link) inet6 (+link)
/hurd/pci-arbiter /hurd/acpi /hurd/shutdown /hurd/password cr
Almudena Garcia, le mar. 17 août 2021 00:01:21 +0200, a ecrit:
> After change to mach console, I report that the getty error is not the cause
> of
> the keyboard lock.
> The getty errors continues appearing, but I can using the keyboard in the tty.
That doesn't mean that getty is not an underlyin
After change to mach console, I report that the getty error is not the
cause of the keyboard lock.
The getty errors continues appearing, but I can using the keyboard in the
tty.
Now I have to find the cause of the lock: I've disable the kbd repeater (in
other times, this was the cause) and re-enab
Almudena Garcia, le lun. 16 août 2021 21:32:38 +0200, a ecrit:
> > It rather looks to me like it's the Hurd console which cannot start for some
> reason, and that's where you want to investigate.
> What do I have to search? I only have access via Rescue Mode
You can disable the hurd console from /
> It rather looks to me like it's the Hurd console which cannot start for
some reason, and that's where you want to investigate.
What do I have to search? I only have access via Rescue Mode
El lun, 16 ago 2021 a las 21:30, Samuel Thibault ()
escribió:
> Almudena Garcia, le lun. 16 août 2021 20:52
Almudena Garcia, le lun. 16 août 2021 20:52:07 +0200, a ecrit:
> After install Debian GNU/Hurd in "compatibility" mode in a Thinkpad T410, I've
> found many getty errors which avoid the access to the tty.
>
> It seems any errors in the paths generation, which generates a bad path for
> the
> tty
