all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Bengt Richter <bokr@bokr.com>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: 40542@debbugs.gnu.org, Christopher Howard <christopher@alaskasi.com>
Subject: bug#40542: wip-hurm-vm build failure
Date: Tue, 14 Apr 2020 18:57:55 +0200	[thread overview]
Message-ID: <20200414165755.GA11406@LionPure> (raw)
In-Reply-To: <87ftd6bovr.fsf@gnu.org>

Hi Janneke,

On +2020-04-14 07:46:48 +0200, Jan Nieuwenhuizen wrote:
> Christopher Howard writes:
> 
> > I'm having some trouble playing around with the VM, because a lot of
> > weird things are happening with keyboard input into the qemu
> > window. It seems like the meta keys (shift, ctrl, alt, super) are
> > behaving in strange ways, or that terminal state is getting corrupted
> > somehow. E.g., sometimes shift key stops working, or the cursors jumps
> > up to the middle of the screen, or text gets garbled.
> 
> Since yesterday I've been seeing that too.  I'm pretty sure that if you
> build a VM from core-uupdates, the console is fine.
> 
> I haven't looked into the details of the console/tty setup, so I must
> have messed-up something.  Sorry!

Could it be a sensitive touch-pad? (are there configs to adjust triggering on motion?)
(I have to disable mouse/touchpad input to edit unless I'm super careful
not to brush it with my sleeve or palm)

> 
> Meanwhile we do have ssh login :-)
> 
> The startup now goes like this
> 
>     startup -> runsystem -> init -> runsystem.hurd -> rc -> shepherd
> 
> and; i would like to move towards
> 
>     -startup -> rc -> shepherd
> 
> if that's possible.
> 
> Greetings,
> janneke
> 
> -- 
> Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
> Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
> 
> 
> 
-- 
Regards,
Bengt Richter

  parent reply	other threads:[~2020-04-14 16:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-10 15:53 bug#40542: wip-hurm-vm build failure Christopher Howard
2020-04-11 15:46 ` Jan Nieuwenhuizen
2020-04-13 16:59   ` Christopher Howard
2020-04-13 20:40     ` Ludovic Courtès
2020-04-13 21:02       ` Christopher Howard
2020-04-13 21:23         ` Ludovic Courtès
2020-04-13 21:46           ` Jan Nieuwenhuizen
2020-04-13 22:58           ` Christopher Howard
2020-04-14  5:46             ` Jan Nieuwenhuizen
2020-04-14 15:55               ` Christopher Howard
2020-04-14 17:12                 ` Jan Nieuwenhuizen
2020-04-14 16:57               ` Bengt Richter [this message]
2020-04-14 17:29                 ` Christopher Howard
2020-04-14 19:30                   ` Jan Nieuwenhuizen
2020-04-14 23:27                     ` Christopher Howard
2021-03-26  0:16 ` Christopher Howard
2021-03-26  0:25   ` Leo Famulari
2021-03-29 16:49     ` Leo Famulari

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200414165755.GA11406@LionPure \
    --to=bokr@bokr.com \
    --cc=40542@debbugs.gnu.org \
    --cc=christopher@alaskasi.com \
    --cc=janneke@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.