From: Christopher Howard <christopher@alaskasi.com>
To: Bengt Richter <bokr@bokr.com>, Jan Nieuwenhuizen <janneke@gnu.org>
Cc: 40542@debbugs.gnu.org
Subject: bug#40542: wip-hurm-vm build failure
Date: Tue, 14 Apr 2020 09:29:46 -0800 [thread overview]
Message-ID: <2b3d4348c2c47a029b1ec5ce9eb5d5de1bcabd2d.camel@alaskasi.com> (raw)
In-Reply-To: <20200414165755.GA11406@LionPure>
[-- Attachment #1: Type: text/plain, Size: 2140 bytes --]
I am using only a mouse. I unplugged the mouse, but am getting similar
behavior.
Something of interest, however: the keyboard inputs seem to be working
fine until a few seconds after I "login root", at which point the
emulated VGA screen blinks, and the wonky behavior starts.
-----Original Message-----From: Bengt Richter <bokr@bokr.com>Reply-To:
Bengt Richter <bokr@bokr.com>To: Jan Nieuwenhuizen <janneke@gnu.org>Cc:
Christopher Howard <christopher@alaskasi.com>,
40542@debbugs.gnu.orgSubject: Re: bug#40542: wip-hurm-vm build
failureDate: Tue, 14 Apr 2020 18:57:55 +0200
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
> > ofweird things are happening with keyboard input into the
> > qemuwindow. It seems like the meta keys (shift, ctrl, alt, super)
> > arebehaving in strange ways, or that terminal state is getting
> > corruptedsomehow. E.g., sometimes shift key stops working, or the
> > cursors jumpsup to the middle of the screen, or text gets garbled.
>
> Since yesterday I've been seeing that too. I'm pretty sure that if
> youbuild a VM from core-uupdates, the console is fine.
> I haven't looked into the details of the console/tty setup, so I
> musthave 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 carefulnot 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
>
>
>
--
Christopher Howard
Enterprise Solutions Manager
Alaska Satellite Internet
PO Box 70, Ester, AK 99725
3239 La Ree Way, Fairbanks, AK 99709
907.451.0088
1.888.396.5623
www.alaskasatelliteinternet.com
[-- Attachment #2: Type: text/html, Size: 4107 bytes --]
next prev parent reply other threads:[~2020-04-14 17:31 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
2020-04-14 17:29 ` Christopher Howard [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2b3d4348c2c47a029b1ec5ce9eb5d5de1bcabd2d.camel@alaskasi.com \
--to=christopher@alaskasi.com \
--cc=40542@debbugs.gnu.org \
--cc=bokr@bokr.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).