Devuan bug report logs - #99
devuan-installer: the installed devuan system is not fully accessible

Package: devuan-installer; Reported by: Gregory Nowak <greg@gregn.net>; Keywords: jessie; dated Sat, 3 Jun 2017 02:48:01 UTC; Maintainer for devuan-installer is (unknown).

Bug 99 cloned as bug 432 Request was from Mark Hindley <mark@hindley.org.uk> to control@bugs.devuan.org. Full text available.

Message received at 99@bugs.devuan.org:

Date: Wed, 25 Mar 2020 20:49:23 -0700
From: Gregory Nowak <greg@gregn.net>
To: 99@bugs.devuan.org
Subject: Re: bug#99: Acknowledgement (devuan-installer: the installed devuan
 system is not fully accessible)
Message-ID: <20200326034923.GA6093@gregn.net>
References: <20170603023622.3689.66246.reportbug@acer1.gregn.net>
 <handler.99.B.149645760715284.ack@bugs.devuan.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <handler.99.B.149645760715284.ack@bugs.devuan.org>
User-Agent: Mutt/1.5.23 (2014-03-12)

I'm updating this bug as promised. I'm leaving out the promised log
file though, since I figured out a solution to the first issue, and
Mark provided the solution to the second lightdm issue in the dng
thread I linked to previously.

1. The first issue was that orca didn't speak on the lightdm login
   screen on a fresh install, but does speak on my regular install
   which is Ascii upgraded to Beowulf. In the fresh install, on a
   hunch, I ran:

apt-get purge lightdm lightdm-gtk-greeter

That removed lightdm, lightdm-gtk-greeter, and task-mate-desktop. It
also brought in some xterm packages. I than ran:

apt-get install lightdm lightdm-gtk-greeter task-mate-desktop

which installed those three packages, and removed the xterm packages
which were installed when I purged the lightdm packages earlier.

I than rebooted, and got speech from orca at the login screen. I won't
pretend to know why purging the lightdm packages and installing them
again works. Oh, I almost forgot. In order for orca to speak at the
lightdm login screen, the user lightdm needs to be added to the audio
group, which it isn't on a fresh install right now.

2. The other issue is that after logging in from lightdm, orca didn't
   come up, and couldn't connect to accessibility bus errors were
   logged. The solution Mark pointed to is to set

xserver-share=false

in /etc/lightdm/lightdm.conf. I think that does it for the lightdm
issues.

Acknowledgement sent to Gregory Nowak <greg@gregn.net>:
Extra info received and forwarded to list. Copy sent to Ralph Ronnquist <ralph.ronnquist@gmail.com>. Full text available.

Information forwarded to devuan-bugs@lists.dyne.org, Ralph Ronnquist <ralph.ronnquist@gmail.com>:
bug#99; Package devuan-installer. Full text available.

Message received at 99@bugs.devuan.org:

Date: Wed, 25 Mar 2020 15:49:16 -0700
From: Gregory Nowak <greg@gregn.net>
To: 99@bugs.devuan.org
Subject: Re: bug#99: Acknowledgement (devuan-installer: the installed devuan
 system is not fully accessible)
Message-ID: <20200325224916.GA3824@gregn.net>
References: <20170603023622.3689.66246.reportbug@acer1.gregn.net>
 <handler.99.B.149645760715284.ack@bugs.devuan.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <handler.99.B.149645760715284.ack@bugs.devuan.org>
User-Agent: Mutt/1.5.23 (2014-03-12)

Here's an update on Beowulf. Thanks first of all for bringing back the
PC speaker beep for the boot menu in the Beowulf netinst iso.

I thought lightdm wouldn't be a long term option, since in the
original gitlab discussion this bug was migrated from centurian Dan
had indicated that lightdm wouldn't be a long term option. I'm glad to
see that lightdm is still available in Beowulf. I'm also glad to see
the mate desktop in Beowulf is installed with lightdm and
lightdm-gtk-greeter by default. That's the good news, now for the bad
news.

1. There are problems when attempting to do a Beowulf install with
speech in a VirtualBox guest. On one of my machines, the guest crashed
totally. I don't know what was on the screen, the guest just became
unresponsive to attempted keyboard input when I started the install
with speech using the "s" option from the boot menu, and after I
attempted to set speakup volume and rate. On another guest, only the
software speech died, and I was still able to activate a hardware
synthesizer, and do the install that way. The good news is that this
seems to be a problem in debian as well:

<http://linux-speakup.org/pipermail/speakup/2020-March/062176.html>

So, this should be resolved once it is fixed upstream. There is a
patch which might fix this being backported to the 4.19.x kernels:

<http://linux-speakup.org/pipermail/speakup/2020-March/062166.html>

2. The other issue is still with lightdm, and this is a two part
issue. The first part is that after a fresh Beowulf install, orca
doesn't speak at the login screen. It seems that orca has trouble
initializing. I don't have access to the machine where I did the
install, so I'll reply again with the log file. On my regular install,
which is a minimal Ascii install upgraded to Beowulf, orca does in
fact talk at the login screen. I'm still trying to track down why it
works on my upgraded regular install, but doesn't work on a fresh
one. Like I said, I'll reply again with a log file when I have access
to that machine in a few hours.

The second problem with orca not speaking is after loging in through
lightdm a "couldn't register with accessibility bus" message appears
in $HOME/.xsession-errors. This means that orca also can't register
with the accessibility bus, so there is no speech in the GUI. When
running startx by hand, orca does in fact come up, and works just
fine. I started a thread to try to work out a solution to the problem
at:

<https://lists.dyne.org/lurker/message/20200325.043908.484afc83.en.html>

That's all for now. I'm glad to see that progress is being made with
accessibility in Beowulf. I'll be back with the orca not starting in
lightdm log
file I mentioned earlier.

Acknowledgement sent to Gregory Nowak <greg@gregn.net>:
Extra info received and forwarded to list. Copy sent to Ralph Ronnquist <ralph.ronnquist@gmail.com>. Full text available.

Information forwarded to devuan-bugs@lists.dyne.org, Ralph Ronnquist <ralph.ronnquist@gmail.com>:
bug#99; Package devuan-installer. Full text available.

Message received at 99@bugs.devuan.org:

Received: (at 99) by bugs.devuan.org; 17 Jan 2020 13:00:01 +0000
Return-Path: <mark@hindley.org.uk>
Delivered-To: devuanbugs@dyne.org
Received: from tupac3.dyne.org [195.169.149.119]
	by doc.devuan.org with IMAP (fetchmail-6.4.0.beta4)
	for <debbugs@localhost> (single-drop); Fri, 17 Jan 2020 13:00:01 +0000 (UTC)
Received: from mx.hindley.org.uk (mohindley.plus.com [81.174.245.179])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by vm6.ganeti.dyne.org (Postfix) with ESMTPS id EC9D4F60A43
	for <99@bugs.devuan.org>; Fri, 17 Jan 2020 13:51:49 +0100 (CET)
Received: from apollo.hindleynet ([192.168.1.3] helo=apollo)
	by mx.hindley.org.uk with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128)
	(Exim 4.84_2)
	(envelope-from <mark@hindley.org.uk>)
	id 1isR6K-000743-7P
	for 99@bugs.devuan.org; Fri, 17 Jan 2020 12:51:48 +0000
Received: from mark by apollo with local (Exim 4.84_2)
	(envelope-from <mark@hindley.org.uk>)
	id 1isR6I-0001GH-TP
	for 99@bugs.devuan.org; Fri, 17 Jan 2020 12:51:46 +0000
Date: Fri, 17 Jan 2020 12:51:46 +0000
From: Mark Hindley <mark@hindley.org.uk>
To: 99@bugs.devuan.org
Subject: Re: devuan-installer: the installed devuan system is not fully
 accessible
Message-ID: <20200117125146.GA4821@hindley.org.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Debbugs-No-Ack: No Thanks
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Spam-Status: No, score=0.0 required=5.0 tests=FAKE_REPLY_C,SPF_PASS
	autolearn=disabled version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tupac3.dyne.org

Gregory,

We are preparing the release of beowulf. This is an important issue as far as
I am concerned.

You said you thought lightdm would not still be an option in the future. It certainly
is in beowulf.

Is this still an unresolved issue?

Thanks.

Mark

Information forwarded to devuan-bugs@lists.dyne.org, owner@bugs.devuan.org:
bug#99; Package devuan-installer. Full text available.

Tags added: jessie Request was from KatolaZ <katolaz@freaknet.org> to control@bugs.devuan.org. Full text available.

Message received at submit@bugs.devuan.org:

Received: (at submit) by bugs.devuan.org; 3 Jun 2017 02:40:07 +0000
Return-Path: <greg@gregn.net>
Delivered-To: devuanbugs@dyne.org
Received: from mail.dyne.org [178.62.188.7]
	by fulcanelli with IMAP (fetchmail-6.3.26)
	for <debbugs@localhost> (single-drop); Sat, 03 Jun 2017 04:40:07 +0200 (CEST)
Received: from vserver.gregn.net (vserver.gregn.net [174.136.110.154])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by tupac2.dyne.org (Postfix) with ESMTPS id 25AED18EBD7
	for <submit@bugs.devuan.org>; Sat,  3 Jun 2017 02:36:55 +0000 (UTC)
Authentication-Results: tupac2.dyne.org; dkim=pass
	reason="2048-bit key; unprotected key"
	header.d=gregn.net header.i=@gregn.net header.b=dIsO2SfN;
	dkim-adsp=pass; dkim-atps=neutral
Received: from acer1.gregn.net (unknown [IPv6:2001:470:d:6c5:ba88:e3ff:fe4f:939])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by vserver.gregn.net (Postfix) with ESMTPSA id 1570D19C5;
	Fri,  2 Jun 2017 19:36:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=gregn.net; s=default;
	t=1496457412; bh=6fZxSyN+CvHBC3+feYNemMPLPnZJUxW7xKJJUyH0CtE=;
	h=From:To:Subject:Date:From;
	b=dIsO2SfNUiKO7f59Meg+zg5Iel/QanoE+d2WJn/3w05MV25t7XAZr7vvow5MWnofF
	 Z24hvEEdr3rw3umLKBpn8RaAM0+mW8iwMzenm082LeaE2eqdQEOkkVbGibqKGSijr8
	 oSleTRqg4ziJKb2hdXmipQVNmfqCFqRlY9B2651xwKQ/jO3W5mnQGmhMa269rJpl3i
	 wJ0GxtUSU48d5GncywM6z04tl/Qixkb4h+Oni0uCoi7lifRmGUB5r8TIvzPnuXgtzG
	 Gy3CBb9HKyZb7WcSukJBsdMqW8X5fWuKUGCXbIfjUkFZQ6OgamhiUt1o/SMYXifSaY
	 2U6gOsdqTDgAw==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Gregory Nowak <greg@gregn.net>
To: Devuan Bug Tracking System <submit@bugs.devuan.org>
Subject: devuan-installer: the installed devuan system is not fully accessible
Message-ID: <20170603023622.3689.66246.reportbug@acer1.gregn.net>
X-Mailer: reportbug 6.6.3+devuan1.3
Date: Fri, 02 Jun 2017 19:36:22 -0700
X-Virus-Scanned: clamav-milter 0.99.2 at vserver
X-Virus-Status: Clean
X-Spam-Status: No, score=-0.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	DKIM_VALID_AU,RP_MATCHES_RCVD,SPF_PASS autolearn=disabled version=3.4.0
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on tupac2

Package: devuan-installer
Severity: important

Dear Maintainer,
this is a migration of:
<https://git.devuan.org/devuan-infrastructure/Installer_Feedback/issues/3>

When the option to install with speech synthesis is chosen by pressing s and enter at the boot prompt, the resulting installed system isn't fully accessible if
the user chose to install using the default devuan desktop environment. Specifically, because the default session manager is slim, the orca screen reader doesn't
activate at the GUI login screen. This is true on both i386, and amd64.

Installing lightdm and lightdm-gtk-greeter is still a useable option in jessie, but I understand that will not be the case in the future. The only other solution in this
+case for now is for the user to run startx by hand to get a GUI console. Another option is to login without speech using slim, once a sighted person has described the login screen, and the blind user has a routine worked out which key strokes to enter, and when in that routine to type in the user name and password. This solution is not ideal, since it requires assistance initially.


-- System Information:
Distributor ID:	Devuan
Description:	Devuan GNU/Linux 1.0 (jessie)
Release:	1.0
Codename:	jessie
Architecture: x86_64

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Acknowledgement sent to Gregory Nowak <greg@gregn.net>:
New bug report received and forwarded. Copy sent to Daniel Reurich <daniel@centurion.net.nz>.

Your message specified a Severity: in the pseudo-header, but the severity value important was not recognised. The default severity normal is being used instead. The recognised values are: critical, grave, normal, minor, wishlist.

Full text available.

Report forwarded to devuan-bugs@lists.dyne.org, Daniel Reurich <daniel@centurion.net.nz>:
bug#99; Package devuan-installer. Full text available.

Devuan bug report logs - #99 devuan-installer: the installed devuan system is not fully accessible

Message received at 99@bugs.devuan.org:

Message received at 99@bugs.devuan.org:

Message received at 99@bugs.devuan.org:

Message received at submit@bugs.devuan.org:

Devuan bug report logs - #99
devuan-installer: the installed devuan system is not fully accessible