From: marialong2--- via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 68085@debbugs.gnu.org
Subject: bug#68085: a issue about orca@43.2
Date: Thu, 28 Dec 2023 05:23:54 +0100 (CET) [thread overview]
Message-ID: <NmieWcW--3-9@tutanota.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1496 bytes --]
Dear maintainers,Highly appreciate your work on completely free(libre) distribution!
I write this to submit an issue i came accross recently about the use of orca screen reader.Though a bug (at least to a normal user like me, it is a bug) might seem annoying to you and such fix on a single package is neither prior nor urgent to handle with, I wish such unhappiness won't spread to others who need a screen reader to function because of poor eyesight(like me) or blindness.
Here is how I came accross it:
First, I download the .qcow2 file from the main website and transferred it to .vdi with qemu-img on my windows pc.
Then, I loaded the .vdi file in VirtualBox.It booted successfully into a clean xfce window manager.
After that, I tried the icons and panels they functioned well.I opened the terminal emulator at the bottom of screen and typed in:
>guix install gcc #it worked well and gcc command is ok after that
>guix install icecat #it functioned as expected too
>guix install emacs #fine as well
>guix install orca #it smoothly 'installed'
Finally, I typed:
>orca #it returned a Traceback of file .../bin/.orca-real followed with
<from orca import debug<MODULENOTFOUNDERROR: module "orca" not found
I tried orca -s / remove and install again / restart , doesn;t work :(
Please fix it or add more detail on how to set it up in the orca package page:)
Best wishes to you!
--
已通过Tuta 安全发送，立即注册您的加密无广告邮箱！
https://tuta.com
[-- Attachment #2: Type: text/html, Size: 2118 bytes --]
reply other threads:[~2023-12-28 18:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=NmieWcW--3-9@tutanota.com \
--to=bug-guix@gnu.org \
--cc=68085@debbugs.gnu.org \
--cc=marialong2@tutanota.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.