Created attachment 84848 [details] capture écran message du bug Problem description: Nous avons fait la maj de 404 vers 405. Pour ouvrir un fichier calc ou writer sur le pc il n'y avait pas de problème. Mais nous centralisons tout sur un nas, et là, plus moyen d'ouvrir ces fichiers. (...fichier utilisé par inconnu...). Je ne me rappelle plus exactement le message. Je l'ouvrais en faisant une copie, je modifiais, enregistrais, refermais. Puis plus moyen de le rouvrir, le message apparaissait de nouveau sur ce fichier que personne n'utilisait. J'ai désinstallé la 405 et remis la 404, tout est redevenu à la normal. Steps to reproduce: 1. .... 2. .... 3. .... Current behavior: Expected behavior: Operating System: Windows 7 Version: 4.0.5.2 rc Last worked in: 4.0.4.2 release
Xav: several points here: 1) we need more info: - a way to reproduce the bug - some information about the nas: the network protocol used, the file system, is there some encryption, ... - did you install some LO specific extensions - did you rename your LO directory profile (see https://wiki.documentfoundation.org/UserProfile) - did you give a try to 4.1.1 2) since LO is not French only, it's important to write in English (BTW, I'm French so nothing against French people:-)). BTW: what's the link with MinGW?
Changing 'regression' -> 'PossibleRegression' until we have independent confirmation of a regression.
Dear Bug Submitter, Please read the entire message before proceeding. 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 INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/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
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INVALID 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 FDO
Migrating Whiteboard tags to Keywords: (possibleRegression) [NinjaEdit]