From: Robert Vollmert <rob@vllmrt.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 36069@debbugs.gnu.org
Subject: bug#36069: Menu-based installer unusable through noVNC
Date: Tue, 25 Jun 2019 16:09:48 +0200 [thread overview]
Message-ID: <36FEF9C6-B901-4E6B-920B-00E545A10279@vllmrt.net> (raw)
In-Reply-To: <87v9wtn4u9.fsf@gnu.org>
Hi,
> On 25. Jun 2019, at 15:59, Ludovic Courtès <ludo@gnu.org> wrote:
>
> Hi,
>
> Björn Höfling <bjoern.hoefling@bjoernhoefling.de> skribis:
>
>> On Mon, 3 Jun 2019 11:35:17 +0200
>> Robert Vollmert <rob@vllmrt.net> wrote:
>>
>>> 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.
>>
>> Today I installed Guix on a Server which uses Guacamole as a web-based
>> VNC-client according to the HTML code, see
>> https://guacamole.apache.org/
>>
>> I also had the problem that the screen of the installer was too small,
>> I'm attaching two screenshots: Of the normal GRUB startup and the
>> unreadable installer.
>
> I think Robert concluded that the bug was in noVNC.
Rather, I couldn’t prove the bug was anywhere else.
> What we’d need is either something to fix on our side (but there’s
> apparently nothing), or something to report to noVNC, or a workaround we
> could have on our side specifically for this use case.
It seems noVNC isn’t involved here, though, with the only clearly common
factor being Guix, so maybe the bug is there after all? (At least, as
far as I can tell, Guacamole does not involve noVNC.)
Robert
next prev parent reply other threads:[~2019-06-25 14:11 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
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 [this message]
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=36FEF9C6-B901-4E6B-920B-00E545A10279@vllmrt.net \
--to=rob@vllmrt.net \
--cc=36069@debbugs.gnu.org \
--cc=ludo@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).