I have a nextcloud server, which gives webdav access at https://[[server.name]]/remote.php/webdav/ Therefore I have set up a new service in the open from server dialogue Host: [server.name] Port: 443 x secure connection Label: Nextcloud Root: /remote.php/webdav/ When I try to open a file file the server nothing happens, no password prompt, no files get listed, no console output.
Which LO version do you use? On which env are you? Would it be possible to have a guest account (even temporary) to give it a try with debug build of LO?
(In reply to Julien Nabet from comment #1) > Which LO version do you use? Version: 6.2.3.2 > On which env are you? The client? Tried it on Debian Buster and Ubuntu 19.04 > > Would it be possible to have a guest account (even temporary) to give it a > try with debug build of LO? Sure. But I'll be away without net access from tomorrow morning until 2 June, so my preference would be have it after that.
Thank you for your feedback.
Just tried the same settings on Windows, where everything seems to work fine out of the box with the same Nextcloud server.
(In reply to Johannes Rohr from comment #2) > (In reply to Julien Nabet from comment #1) > > > > Would it be possible to have a guest account (even temporary) to give it a > > try with debug build of LO? > > Sure. But I'll be away without net access from tomorrow morning until 2 > June, so my preference would be have it after that. Any updates?
I have two different machines with Debian Buster using the same configuration. On one of them, it works. On the other it doesn't. Now, the last thing I tried is to move ~/.config/libreoffice out of the way on the machine where it doesn't work and replace it with a copy from the other one. The result is: Now it works (but I am loosing all my customizations made on this machine). So it seems to be somehow related to the local config, but since there is zero console output and zero error messages, I have no idea what is wrong.
Johannes: could you attach in a zip the 2 profile directories (the old one and the brand new one) so we can compare them and perhaps pinpoint the root cause?
sure, although I am not sure how much of sensitive data will be contained in either of them. Can you advise on that?
If there are sensitive data, we're stuck since any attachment is automatically made public since anybody can consult the bugtracker.
I simply don't know if. I don't know what kind of data Libreoffice stores in its profiles. I can try to have a look, or I can e-mail it to you. Doesn't bugzilla allow to set a bug to confiditial?
I guess it is fine to send it, I'll send it as soon as I get to the affected computer.
(In reply to Johannes Rohr from comment #10) > I simply don't know if. I don't know what kind of data Libreoffice stores in > its profiles. I can try to have a look, or I can e-mail it to you. Doesn't > bugzilla allow to set a bug to confiditial? AFAIK, I don't think Bugzilla allow to set a bug to confidential.
Something you can test: try with brand new LO profile but retrieve registrymodifications.xcu from old profile and put it at the same location in new LO profile. If you reproduce the pb, the only file to search will be this one. If not, try with other directories, 1 by 1. The goal is to isolate the culprit. It may take some time because registrymodifications.xcu may contain a lot of things. See https://wiki.documentfoundation.org/UserProfile for detailed content of LO profile.
Is there any update on this bug?
(In reply to Craig Harding from comment #14) > Is there any update on this bug? So far there is no evidence that this is a bug. Do you have the exact same situation, where you have a problematic user profile and a working one? If yes, then do as said in comment 7 or perhaps as in comment 13.
Dear Johannes Rohr, 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 Johannes Rohr, 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