Bug 463432

Summary: DAV account setup in kontact : TLS dialog box cannot be interacted with
Product: [Applications] kdepim Reporter: Matthieu Volat <mazhe+kde>
Component: wizardsAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: nicolas.fella
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Matthieu Volat 2022-12-24 15:15:39 UTC
SUMMARY
Hi,

From either KAddressbook, KOrganizer, Akonadiconsole, if I try to setup a Card/Cal DAV account, I can go up to the step where an URL is provided to inspect the available connection. My DAV server is a Nextcloud instance running in a private network and use a self-signed TLS certificate, a dialog box to warn me and require approval is expected, but :

1. The dialogbox is hidden bellow every other window and cannot be elevated (I have to minimize every other window)
2. I cannot interact with this dialog bog: mouse clicks are not registered, neither are keyboard attempts

The dialog cannot be closed until other wizard window are also closed, and I cannot configure anything. I tried to add the self signed cert to the global CA database, it shows in the KDE SSL preference windows but the dialogbox still "appears"

If I try http, I will get another dialog box with a different warning (telling me password is plain on the network) but same behavior. 

Thanks for your time and KDE.

STEPS TO REPRODUCE
1. New KDE/Neon install, install Kontact
2. Open Kontact, add new adressbook
3. Fill credentials, click to fetch collections, select Card/Cal DAV, fill URL

OBSERVED RESULT
Cannot click on the ssl warning dialog box.

EXPECTED RESULT
Dialogbox is expected and message correct, but I would expect to be able to be able to click on its button to proceed futher

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE NEON (up-to-date as 24/12/2022)
(available in About System)
KDE Plasma Version: 5.26.4
KDE Frameworks Version: 5.101.0
Qt Version: 5.15.7

ADDITIONAL INFORMATION
Comment 1 Matthieu Volat 2022-12-24 15:33:49 UTC
Additional comment: same behavior observed on a computer with nvidia graphics, proprietary driver, X11 & wayland *and* in a virtualbox VM.
Comment 2 Nicolas Fella 2022-12-24 15:43:40 UTC

*** This bug has been marked as a duplicate of bug 463124 ***