Version: 4.7.2 (using KDE 4.7.3) OS: Linux Having installed espeak, festival, and kde accessibility does not yield a change to this solution. The correct behavior would be click on an article(s) and click "Speak Selected Articles" to hear them. Reproducible: Always Steps to Reproduce: Open Akregator, point at some feed articles, click "speak selected articles". Actual Results: Does not play articles. Does nothing. Expected Results: Speak the articles using a text to speech synthesizer (to be heard out of the speakers). OS: Linux (x86_64) release 3.0.0-14-generic Compiler: gcc
I can confirm this bug on Linux Mint 14 KDE - Akgregator/KDE v. 4.9.5
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of akregator (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Created attachment 101281 [details] attachment-2110-0.html I can report this on akregator 4.14.2,(which is also what all users from Debian stable are likely to be using). I don't have frameworks / version 5 onwards though. Thanks. On 24 September 2016 20:43:51 BST, Denis Kurz via KDE Bugzilla <bugzilla_noreply@kde.org> wrote: >https://bugs.kde.org/show_bug.cgi?id=289641 > >Denis Kurz <kdenis@posteo.de> changed: > > What |Removed |Added >---------------------------------------------------------------------------- > Resolution|--- |WAITINGFORINFO > Status|UNCONFIRMED |NEEDSINFO > >--- Comment #2 from Denis Kurz <kdenis@posteo.de> --- >This bug has only been reported for versions before 4.14, which have >been >unsupported for at least two years now. Can anyone tell if this bug >still >present? > >If noone confirms this bug for a Framework-based version of akregator >(version >5.0 or later, as part of KDE Applications 15.08 or later), it gets >closed in >about three months. > >-- >You are receiving this mail because: >You are on the CC list for the bug. >You voted for the bug.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.