Created attachment 154647 [details] Screenshot of the dialog. Notice the wider dialog (self signed cert warning) being shown under the top dialog (where the access protocol and remote url are set) SUMMARY When attempting to add a DAV groupware resource that has a self signed certificate, a warning dialog shows up but its under two modal DAV Resource configuration Dialogs, preventing you from acknowledging the self signed certificate and adding the resource. STEPS TO REPRODUCE 1. Spin up a radicale CalDAV server with a self signed certificate 2. Open Kontact 3. Go to Settings -> Configure KOrganizer 4. Go to General -> Calendars 5. Click Add 6. Select DAV Groupware Resource 7. Enter username and password for radicale server spun up 8. Select configure resource manually 9. Under server Configuration, click add 10. Select CalDAV as the access protocol and under remote URL enter the https url to your radicale server with self signed cert 11. Click Fetch under discovered collections OBSERVED RESULT A dialog will appear stating that the server failed the authenticity check Notice that you cannot click cancel or continue, because it is below the two previous modal dialogs EXPECTED RESULT The failed authenticity check dialog should show up as the topmost modal dialog, allowing you to click continue, override the warning and add your server with a self signed certificate SOFTWARE/OS VERSIONS Linux Mint Cinnamon 20.1 running Kontact from Flatpak Flatpak information: ID: org.kde.kontact Ref: app/org.kde.kontact/x86_64/stable Arch: x86_64 Branch: stable Version: 5.21.3 License: GPL-2.0+ Origin: flathub Collection: org.flathub.Stable Installation: system Installed: 315.8 MB Runtime: org.kde.Platform/x86_64/5.15-21.08 Sdk: org.kde.Sdk/x86_64/5.15-21.08 ADDITIONAL INFORMATION I have a reply from a maintainer of the Kontact flatpak asserting that this is NOT a flatpak related issue but an akonadi related issue. See Here: https://github.com/flathub/org.kde.kontact/issues/179#issuecomment-1353627499
Indeed not Flatpak related See https://bugs.kde.org/show_bug.cgi?id=463124 *** This bug has been marked as a duplicate of bug 463124 ***