https://bugs.kde.org/show_bug.cgi?id=477889

            Bug ID: 477889
           Summary: Cannot access password-protected feeds
    Classification: Applications
           Product: akregator
           Version: 5.24.3
          Platform: Flatpak
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: kdepim-bugs@kde.org
          Reporter: d...@coneharvesters.com
  Target Milestone: ---

SUMMARY
Trying to access a feed URL protected with HTTP Digest authentication fails.
For the feed I encountered this on the UI shows dialogs to accept a self-signed
certificate, then silently fails to download the feed and the feed name in the
list on the left turns red. The console shows these messages:

kf.kio.core: Can't communicate with kiod_kpasswdserver (for checkAuthInfo)!
kf.kio.core: Can't communicate with kiod_kpasswdserver (for queryAuthInfo)!

An older version (20.12.0) installed locally (not with via Flatpak) works fine,
and requests the username and password from the user the first time, then
automatically uses those credentials on subsequent uses.

kf.kio.core: Can't communicate with kiod_kpasswdserver (for checkAuthInfo)!
kf.kio.core: Can't communicate with kiod_kpasswdserver (for queryAuthInfo)!

STEPS TO REPRODUCE
1. Configure a feed that requires Digest authentication
2. Try to "Fetch feed"
3. Go out and do some gardening because you aren't going to be reading RSS
feeds

OBSERVED RESULT
No feed and a red feed name

EXPECTED RESULT
Feed contents available for browsing

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
KDE Plasma Version: 
KDE Frameworks Version: 5.111.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION
The Flatpak permissions for org.kde.akregator do not include
org.kde.kpasswdserver in the [Session Bus Policy] section. Running "sudo
flatpak override org.kde.akregator --talk-name=org.kde.kpasswdserver" lets
akregator get past this problem (but then it encounters another, which I'll
open momentaryily).

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to