Bug #7503
The Persistent Volume Assistant is not readable by Orca
Start date:
2014-07-06
Due date:
% Done:
0%
Description
__Hi,
The tails persistance tool prints its error messages in an inaccessible format.
Subtasks
History
#1 Updated by geb 2014-07-06 18:01:35
- Priority changed from Normal to High
#2 Updated by geb 2014-07-06 18:02:49
- Subject changed from Tails Persistance Tools prints error messages in inaccessible format to Tails Persistance Tools prints error messages in an inaccessible format
#3 Updated by geb 2014-07-07 13:27:17
It may be the same kind of issue (and hopefully solution) that for the unsafe browser: Bug #7502
#4 Updated by intrigeri 2014-07-21 09:10:41
- Subject changed from Tails Persistance Tools prints error messages in an inaccessible format to The Persistent Volume Assistant prints error messages in an inaccessible format
#5 Updated by intrigeri 2014-07-21 09:13:34
- Priority changed from High to Elevated
#6 Updated by intrigeri 2014-07-21 09:14:06
- related to Bug #7502: Unsafe Browser is not accessible added
#7 Updated by BitingBird 2016-06-26 10:53:54
- Priority changed from Elevated to Normal
#8 Updated by intrigeri 2017-09-02 08:21:11
- Parent task set to Feature #14522
#9 Updated by intrigeri 2017-09-02 08:22:27
- related to deleted (
Bug #7502: Unsafe Browser is not accessible)
#10 Updated by intrigeri 2017-09-02 08:23:24
- related to Bug #7502: Unsafe Browser is not accessible added
#11 Updated by intrigeri 2019-05-02 16:07:42
- Subject changed from The Persistent Volume Assistant prints error messages in an inaccessible format to The Persistent Volume Assistant is not readable by Orca
#12 Updated by zersiax 2020-05-01 16:20:16
geb wrote:
> __Hi,
>
> The tails persistance tool prints its error messages in an inaccessible format.I would rather say that the entire UI of this tool is currently inaccessible. The title of the issue reflects this, but the description did not.
#13 Updated by zersiax 2020-05-01 16:22:16
I am currently blocked on this issue and would really appreciate it getting some attention. In the meantime, is there a commandline way of working around this inaccessible UI?