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

Package: devuan-installer; Maintainer for devuan-installer is Ralph Ronnquist <>;

Reported by: Gregory Nowak <>

Date: Sat, 3 Jun 2017 02:48:01 UTC

Severity: normal

Tags: jessie

Done: Gregory Nowak <>

Full log

Message #20 received at (full text, mbox, reply):

Received: (at 99) by; 26 Mar 2020 04:00:02 +0000
Return-Path: <>
Received: from []
	by with IMAP (fetchmail-6.4.0.beta4)
	for <debbugs@localhost> (single-drop); Thu, 26 Mar 2020 04:00:01 +0000 (UTC)
Received: from ( [])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by (Postfix) with ESMTPS id 4FBD6F60BBD
	for <>; Thu, 26 Mar 2020 04:49:37 +0100 (CET)
	dkim=pass (2048-bit key; unprotected) header.b="VdVw25Qx";
Received: from (unknown [])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by (Postfix) with ESMTPSA id 99A61239A
	for <>; Wed, 25 Mar 2020 20:50:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;; s=default;
	t=1585194647; bh=gasPk/LgibR/rCq890mH4uleE6UabWoA4+V13EH3hIg=;
Received: from greg by with local (Exim 4.84_2)
	(envelope-from <>)
	id 1jHJWF-0001bF-OJ
	for; Wed, 25 Mar 2020 20:49:23 -0700
Date: Wed, 25 Mar 2020 20:49:23 -0700
From: Gregory Nowak <>
Subject: Re: bug#99: Acknowledgement (devuan-installer: the installed devuan
 system is not fully accessible)
Message-ID: <>
References: <>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Virus-Scanned: clamav-milter 0.102.2 at vserver
X-Virus-Status: Clean
X-Spam-Status: No, score=-0.2 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	DKIM_VALID_AU,DKIM_VALID_EF,SPF_PASS autolearn=disabled version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
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


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

Send a report that this bug log contains spam.

Devuan BTS -- Powered by Debian bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson,
2005-2017 Don Armstrong, and many other contributors.

Devuan Bugs Owner <>.
Last modified: Tue Oct 4 13:07:57 2022;