Bug#798206: gnome-orca: Binding to report notifications does not work

Mario Lang mlang at debian.org
Tue Sep 8 08:55:48 UTC 2015

Jean-Philippe MENGUAL <jpmengual at hypra.fr> writes:

> Package: gnome-orca
> Version: 3.16.2-1
> Severity: normal
> Dear Maintainer,
> *** Reporter, please consider answering these questions, where appropriate ***
>    * What led up to the situation?
> I use orca 3.16 here, with MATE desktop.
>    * What exactly did you do (or not do) that was effective (or
>      ineffective)?
> 1. ins-space
> 2. Create 3 bindings in Bindings tab:
> - ins-f8 for speaking previous notification message;
> - ins-f9 for speaking latest notif message
> - ins-f10 to have notif messages list
> 3. Save. 
> 4. On an IRC client in MATE, be highlighted by someone. O!ca reads the notif.
>    * What was the outcome of this action?
> If you issue ins-f8 f9 f10, orca says: "not notification message"
>    * What outcome did you expect instead?
> It should speak the latest message, at least.
> *** End of the template - remove these template lines ***
> Attached a patch which will likely be applied upst!eam.

Thanks for your report.

The patch attached is already applied upstream.

> Could you apply it to the Debian release?

The patch you sent does not apply to 3.16.2, which is what we have in
Debian unstable right now.
There was an early change during the 3.17 cycle (b1c3c11) which prevents
it from applying cleanly on top of 3.16.2.

> It fixes the problem. This feature is quite useful. The Debian sackage
> should ship it via patch before the next Orca release.

Yes, it is simple.  It would have been simpler (for me) if you actually
submitted a patch that applied cleanly to 3.16.2.
However, indirectly pointing at the corresponding upstream commit is
somewhat sufficient, I managed to manually rebase the patch via git.


> You could apply too for Jessie.

To make one thing clear, we do not randomly patch stable.
A patch to stable has to fix a serious security issue.
Random simple fixes are *never* going to be applied to stable in
Debian.  This is how things go in Debian.
The reason for this is simply, that even if you think you are sure, you
will accidentally introduce new bugs into the system distribution if you
apply fixes to it more or less at random.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 635 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20150908/8d3c15e4/attachment.sig>

More information about the pkg-gnome-maintainers mailing list