Sometimes Akregator produces multiple certificate errors. Whilst these may be correct (I'm not actually sure - sometimes I get errors without any clear reason why i should be getting an error), and whilst sometimes i seem to be getting problems with certificates I've asked it to accept permanently (see bug https://bugs.kde.org/show_bug.cgi?id=100302), sometimes I get these errors from logging in on an open network, e.g. in a library, where it produces a login window in a browser . The way it produces these errors can be quite inconvenient, as a) it produces an error even though akregator is only running in the system tray and is not actively open, and b) if there are multiple certificates error, it brings these all up as individual error messages which the user has to click through to continue with what they are doing. My suggestion would be that errors are disabled while akregator is in the system tray (they could be held for when akregator is opened), and also that if multiple errors are found, these are all bundled together into one message, or there could be an option to ignore/hide future certificate errors within the session. Thanks! Reproducible: Sometimes Steps to Reproduce: 1. Have Akregator running 2.Have multiple feeds with new items that cause certificate errors (not sure what these are) 3. Actual Results: Multiple errors as described. Expected Results: Errors should be less prominent, not multiple, and with the possibility to hide them. Certainly errors should only appear when akregator itself is open (i.e. not in system tray).
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 101280 [details] attachment-1929-0.html Hi, 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:45:25 BST, Denis Kurz via KDE Bugzilla <bugzilla_noreply@kde.org> wrote: >https://bugs.kde.org/show_bug.cgi?id=329530 > >Denis Kurz <kdenis@posteo.de> changed: > > What |Removed |Added >---------------------------------------------------------------------------- > Status|UNCONFIRMED |NEEDSINFO > Resolution|--- |WAITINGFORINFO > >--- Comment #1 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 reported the bug.
Nick, I'm afraid your version is still way too old. 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.
Created attachment 103277 [details] attachment-10693-0.html Hi Denis, thanks yes when I upgrade (when a new Debian stable is released, most likely) I will try hat out. Thanks, Nick On 7 January 2017 23:26:10 GMT+00:00, Denis Kurz <bugzilla_noreply@kde.org> wrote: >https://bugs.kde.org/show_bug.cgi?id=329530 > >Denis Kurz <kdenis@posteo.de> changed: > > What |Removed |Added >---------------------------------------------------------------------------- > Status|NEEDSINFO |RESOLVED > Resolution|WAITINGFORINFO |UNMAINTAINED > CC| |kdenis@posteo.de > >--- Comment #3 from Denis Kurz <kdenis@posteo.de> --- >Nick, I'm afraid your version is still way too old. 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. > >-- >You are receiving this mail because: >You reported the bug.
This looks a lot like the bug I came here to log... Cerificate error notifications should not IMHO be a modal popup (whatever the korrect term might be these days) - especially when Akregator is docked in the tray. More appropriate behaviour would be a systray notification that does not require user interaction to dismiss. This is still how it works in 5.2.3, so can we REOPEN this as a bug/enhancement as I am confirming it for Framework-based Akregator.