W dniu 2014-04-30 14:40, Joanmarie Diggs pisze:
On 04/30/2014 07:41 AM, Jarek Czekalski wrote:
If you're curious, these are the bugs, that I intended to fix in webkit1:
https://bugs.webkit.org/show_bug.cgi?id=130941
https://bugs.webkit.org/show_bug.cgi?id=132349
FWIW, the WebCore accessib
Guys,
I'm wondering how much effort should be put in fixing webkit1 bugs, when
we know it just became deprecated.
Yelp exhibits several accessibility problems on Debian Unstable. Their
origin sits in webkit1, at least that's what I see on my box.
Does anyone knows what will happen with epip
I can avoid crashes by inserting an immediate return in highlight method
src/lib/accerciser/node.py.
So something inside the highlighting code goes wrong.
Jarek
--
To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas.
This is the backtrace, shown by gdb.
Script started on Sat 19 Apr 2014 08:41:43 PM CEST
jcdeb:/m/usr/src/accerciser# gdb --args python3 /usr/lib/ac
bin/accerciser
GNU gdb (GDB) 7.6.2 (Debian 7.6.2-1)
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL versio
Package: accerciser
Version: 3.12.0-1
Severity: important
Dear Maintainer,
* What led up to the situation?
Right after starting, accerciser shows accessible applications. When I expand
an application, e.g. gedit, and try to select the first object, it crashes, in
cairo_status. Full backtrace
Hi Accessibility Team
Firefox is not accessible on Debian due to bug #743580 [1] and seems
like it won't be resolved soon. So I filed a Debian specific bug for
this Debian specific problem, #743440 [2]. The source of this problem is
that libraries lie in multiarch directory, which is not pract
Unfortunately this release is bugged on my machine. See this Ubuntu
report: bug 1224497 [1]. I need to wait for 3.12.0 release and use
upstream version meanwhile.
[1] https://bugs.launchpad.net/ubuntu/+source/accerciser/+bug/1224497
W dniu 2014-03-21 14:33, Debian FTP Masters pisze:
Accepted
It's reported as Mozilla bug under #743580, but seems like Multiarch is
a Debian invention and a Debian only problem for now. So
debian-accessibility list looks like the best place to develop a
solution to this bug.
The workaround with "ln -s" was posted on orca list quite a while ago [2].
Th
Maybe these links would help:
By Chuck, in Bug#735202: speakup crashes debian (fwd)
http://linux-speakup.org/pipermail/speakup/2014-February/058536.html
By Janina, in speakup paste problem on debian
http://linux-speakup.org/pipermail/speakup/2014-January/058531.html
Jarek
--
To UNSUBSCRIBE, e
W dniu 2014-01-12 11:04, Paul Gevers pisze:
I think there is just something trivial wrong in our latest upload to
experimental. I completely not understand why your compilation from
upstream works and the experimental upload not. There is no differerece.
This regards bug 734392 [1]. I sent more
Hi
I have problems with starting the latest (experimental)
speech-dispatcher. It seems that all come down to the audio output
setting. With alsa it is ok. With pulseaudio either does not work at all
or with an ugly sounding speech. (I use espeak output module). I figured
out that even when sp
Hi Paul
Thanks for your work. Nice to start a new year with a step forward :)
Are you in the position to do the
same for speech-dispatcher?
The position is much different. Less knowledge of the software, less
usage experience. Basic testing comprises launching a command "spd-say
hello" and
An important thing about speech-dispatcher 0.8:
"pkgconfig include path incorrect?"
http://lists.freebsoft.org/pipermail/speechd/2013q4/004484.html
Seems like all packages using speech-dispatcher have to change their
"include" lines when switching from 0.7 to 0.8.
Jarek
--
To UNSUBSCRIBE, e
W dniu 2013-12-22 19:31, Paul Gevers pisze:
If nobody else does the work (e.g. you) I will do it, and call it a
team release. That is how I work.
Fine. So we have a fallback solution. Now what my idea was. It's
possible to run speech-dispatcher 0.8 without upgrading dotconf from 1.0
to 1.3.
Again we exchanged a couple of emails with Paul, that aim at releasing
speech-dispatcher. We both think that this discussion should be made
public, but I think it first should be decided who's gonna release
speech-dispatcher. Is there anyone to do it? Please don't say "the team
will release", b
Probably this is the clue: outdated dotconf package:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637652
The package maintainer Shane Wegner is said to be unaccessible. Is that
true? Hallo, Shane :)
Jarek
--
To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org
with a su
Hi
People on Orca list ask why Debian has so old gnome-orca, 3.4. Ubuntu
has 3.10. Could you explain?
http://packages.qa.debian.org/g/gnome-orca.html
The page suggests that the package was last touched in June 2012.
Jarek
--
To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debi
Searching a given Debian list seems to be problematic, see this bug report:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670947
For the orca list I suggested to use nabble as a searchable archive:
http://gnome-orca.1098411.n5.nabble.com/
Do we have any reasonable search option now? If yes, p
Package: emacspeak
Version: 39.0+dfsg-2
Severity: minor
M-x emacspeak-version
returns wrong number: 38 instead of 39.
It is an upstream bug.
Right after the tags for the version 39 were produced in upstream
(r8591, 8592), there appeared two fixes that address version numbers:
https://code.goo
Please reopen this entry.
Although the title says about q switch removal, it should not be done in
a plain way. Please see the original patch at [1].
If q switch is removed and INITSTR is left unchanged, it results in
running the emacs user init file twice. Once normally, and once through
IN
Whenever I deal with Debian maintainers I meet immediate and thoughtful
response. Thank you for that!
Paul, I agree with your remarks about Emacspeak and Emacs versions. Now
I'll do some testing and prepare the testing guide too.
Jarek
--
To UNSUBSCRIBE, email to debian-accessibility-requ..
W dniu 2013-11-28 09:30, Samuel Thibault pisze:
Jarek Czekalski, le Thu 28 Nov 2013 09:18:37 +0100, a écrit :
That is: if we decide to run Emacspeak 39 on Emacs 24, don't bother to
support Emacs 23.
I don't think this can work: other packages may not support Emacs 24
yet, and s
I see in the log above that emacs22 is involved in upgrade process of
emacspeak 38. Emacspeak 38 works on emacs23 and there's no need to
support any older version of Emacs. So the only thing to investigate is
how to disconnect emacs22 from play.
Emacspeak is rapidly adjusting to new Emacs feat
Hi Paul
W dniu 2013-11-27 19:59, Paul Gevers pisze:
Please file [2] a bug report in the bts so that we don't forget.
Sure, done.
I'll try to update the packaging soon, maybe on Friday.
Have you decided yet which Emacs to use? I made a comment on bug 729861,
"emacspeak: fails to upgrade le
Package: emacspeak
Version: 38.0+dfsg-2
Steps to reproduce:
1. Launch Emacspeak using emacspeak script (the default method)
2. C-h v emacspeak-speak-messages
3. Variable description is displayed, click "customize"
4. A message appears at top: Custom settings cannot be saved; maybe you
started E
Hey guys
Emacspeak 39 is released. I'd like to help in Debian release. The
minimum what I can do is testing. I was also thinking about providing a
full tester's guide, but at this moment probably I'll just do the
testing myself.
There was one patch posted by me on Emacspeak mailing list, whi
26 matches
Mail list logo
