unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Robert Vollmert <rob@vllmrt.net>
Cc: 36069@debbugs.gnu.org
Subject: bug#36069: Menu-based installer unusable through noVNC
Date: Wed, 05 Jun 2019 12:39:18 +0200	[thread overview]
Message-ID: <87r28848q1.fsf@gnu.org> (raw)
In-Reply-To: <DE060D3A-D662-4779-B68D-A649CD3A5A04@vllmrt.net> (Robert Vollmert's message of "Mon, 3 Jun 2019 11:35:17 +0200")

Hello,

Robert Vollmert <rob@vllmrt.net> skribis:

> There seems to be some conflict between the “graphical” installer’s idea
> of the console size and VNC’s (which appears to be noVNC
> https://novnc.com/info.html). As you can see in the attached screenshot,
> the screen is cropped on all sides, particularly making the menu choices
> unviewable.
>
> Not sure if relevant, but the console goes through a successful mode switch
> earlier in the booting process, where the VNC display size changes. Seems
> like that should happen again when the menus start, but it doesn’t.
>
> I’ve run other installers through noVNC successfully so there’s a good
> chance this is a Guix issue, can’t say for sure though.

I’ve never used noVNC, but doesn’t it allow you to zoom out or
something?  The kernel (KMS) knows what it’s doing, so it seems to me
that the problem is that noVNC doesn’t realize what the actual screen
size is.  Does the Internet have something to say wrt. noVNC vs. kmscon?

BTW, for your VPS, wouldn’t it be easier to bypass the installation
altogether?  That is, you write a config that you want to use, you
create a QCOW2 image or whatever is suitable for your VPS, and you boot
that directly.

Thanks,
Ludo’.

  reply	other threads:[~2019-06-05 10:40 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-03  9:35 bug#36069: Menu-based installer unusable through noVNC Robert Vollmert
2019-06-05 10:39 ` Ludovic Courtès [this message]
2019-06-05 11:25   ` Robert Vollmert
2019-06-05 21:14     ` Ludovic Courtès
2019-06-11  7:13       ` Robert Vollmert
2019-06-11  8:26         ` Ludovic Courtès
2019-06-24 22:24 ` Björn Höfling
2019-06-25 13:59   ` Ludovic Courtès
2019-06-25 14:09     ` Robert Vollmert
2019-06-25 15:06       ` Björn Höfling
2019-06-25 15:54         ` pelzflorian (Florian Pelz)
2019-06-25 17:51           ` Robert Vollmert
2019-06-26 16:51           ` Björn Höfling
2019-06-26 19:16             ` Robert Vollmert
2019-06-26 20:23             ` pelzflorian (Florian Pelz)
2019-06-27  6:34               ` Robert Vollmert
2019-06-27  8:27                 ` Björn Höfling
2019-07-19 11:58                 ` Ludovic Courtès
2019-07-19 16:37                   ` Mark H Weaver
2019-07-20 13:47                     ` Ludovic Courtès
2019-07-20 15:17                       ` Robert Vollmert
2019-07-22  9:25                         ` Björn Höfling
2019-07-22 10:25                           ` Ludovic Courtès
2019-09-02 13:10                             ` Björn Höfling
2019-09-16  8:00                               ` Ludovic Courtès
2019-06-26  8:50         ` Ludovic Courtès
2023-02-05 12:15 ` bug#36069: (No Subject) Attila Lendvai
2023-11-03 20:22 ` bug#36069: "cirrus" added to VM initrd modules Tobias Geerinckx-Rice via Bug reports for GNU Guix

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=87r28848q1.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=36069@debbugs.gnu.org \
    --cc=rob@vllmrt.net \
    /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).