From: Linux for blind general discussion <blinux-list@redhat.com>
To: Linux for blind general discussion <blinux-list@redhat.com>
Subject: Re: fedora is toast.
Date: Wed, 21 Jun 2017 23:05:36 -0400 (EDT) [thread overview]
Message-ID: <alpine.NEB.2.20.1706212300580.28754@panix1.panix.com> (raw)
In-Reply-To: <6360B492-6C63-4E62-95BC-8069641F12CB@icloud.com>
I tried that option next. I got zeniel release installed. It even
connected to the ubuntu home page with firefox and after I closed
firefox I let zeniel installer run for a while. I didn't hear anything
so shut it down and rebooted the system.
I knew I was rolling the dice doing that but when systems don't talk to
me after usually a reasonable time and sometimes unreasonable I tend to
roll the dice. Surprisingly the system booted and I logged in.
What happens now is that the screen reader shuts off a short time after
login and I think I need to configure the system to fix that.
One thing that surprised me was login as super user prompts through the
installer and I hit enter on them when those came up.
On Wed, 21 Jun 2017, Linux for blind general discussion wrote:
> Date: Wed, 21 Jun 2017 22:21:58
> From: Linux for blind general discussion <blinux-list@redhat.com>
> To: blinux-list@redhat.com
> Subject: Re: fedora is toast.
>
> well,
> ubuntu still works (yeah, I know, this is the red hat list for the blind, but seriously, it should work, shouldn't it?).
>
> -eric
>
> On Jun 21, 2017, at 4:43 PM, Linux for blind general discussion wrote:
>
>> workstation live x86_64 version 24 torrent from fedora official site cannot take user or root credentials in the install and save them not even if advanced user settings are entered and save changes is used. Version 25 workstation x86_64 turned out to have the same problem that I didn't get by bittorrent. Version 26 beta had screen reader get killed shortly after accept your fate button got hit. One good thing about version 24 was it took less time to get to the point I could start the screen reader than any of the other versions I tried. So now I move along to a different distro this one is toast. I was only doing this because I could get some help with a web site creating an account from a sighted individual and I wasted two days with these failures.
>>
>> --
>>
>> _______________________________________________
>> Blinux-list mailing list
>> Blinux-list@redhat.com
>> https://www.redhat.com/mailman/listinfo/blinux-list
>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>
--
prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion [this message]
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.20.1706212300580.28754@panix1.panix.com \
--to=blinux-list@redhat.com \
/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).