Description: opening an openoffice document with embedded pictures which require authentication on access forces an authentication dialog which crashes. So the document can't be opened. Steps to Reproduce: 1. create a new document and embedd a picture which can only be accessed via https / webDav 2. save and close libreoffice 3. reopen the document - an empty dialog appears Actual Results: unable to open the document - even without external pictures Expected Results: at least the document should be able to open Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.3.2.2 Build ID: 30(Build:2) CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: de-DE (de_DE.UTF-8); UI: de-DE Calc: threaded
Created attachment 180613 [details] auth dialog
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Created attachment 180617 [details] test file
test file added. The crash does not happen all the time - in some rare cases the credential dialog appears.
In Linux I get the authentication dialog. Not clear if crash is before or after correct credentials are used.
the crash is before - but sometimes I get that dialog too. But not always.
No crash here. It opens two dialogs, one per image. Maybe the code could be made smarter, so the same domain only needs authentication once. I created bug 153060 for it. Do you still get the crash with 7.4? Set to NEEDINFO. Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away. Arch Linux 64-bit, X11 Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 959fbfc000d2e3167b2b57b6d11bea231993b4f0 CPU threads: 8; OS: Linux 6.1; UI render: default; VCL: gtk3 Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Jumbo Built on 17 January 2023 Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: f1830bff71847a9c17715cff52383956719847fe CPU threads: 2; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: en-US (en_FI); UI: en-US Calc: threaded
Dear Marc, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Marc, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp