public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Linux for blind general discussion <blinux-list@redhat.com>
To: orca-list@gnome.org
Cc: blinux-list@redhat.com
Subject: installing jenux
Date: Fri, 27 Mar 2020 12:20:22 -0400	[thread overview]
Message-ID: <alpine.NEB.2.21.2003271212120.25315@panix1.panix.com> (raw)

During a jenux install jenux uses fenrir for a screen reader if
accessibility mode is enabled.  No boot parameters enables accessibility
mode.  During jenux install, much fast text will be spoken by the screen
reader unless insert-f4 is used to toggle speech off and on.  I usually
toggle speech off until I hear the computer beep and then I know jenux
installer needs some input.  Then I toggle speech back on and inspect the
screen and answer questions.  In the mate install path, there's no beep
before the system asks for the user name and password for the first time
and this is after all packages have been installed.  Those questions could
be moved ahead of package installation and answers stored in and retrieved
from variables but that's not now the case with this installer.  I got a
mate install with jenux and you log in on the console which is good with
fenrir then fenrir turns off and the mate environment comes up and orca
turns on.  I've done a base install with no difficulty earlier.  I will
try a gnome install next to see if that now works.  When these installs
fail it's usually because the developer is working on what fails to
download so when that happens maybe try another install later.  The base
install which is archlinux console uses fenrir to run.



--


             reply	other threads:[~ UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Linux for blind general discussion [this message]
 ` Linux for blind general discussion
   ` Linux for blind general discussion
 Installing Jenux blinux-list
 ` blinux-list

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=alpine.NEB.2.21.2003271212120.25315@panix1.panix.com \
    --to=blinux-list@redhat.com \
    --cc=orca-list@gnome.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.
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).