Created attachment 63808 [details] backtraces & straces I encountered following issue on my customers productive laptop (fresh installed Ubuntu-like distribution) If the networking is enabled and customer tries to save an open document (loaded from local fs, NOT a network fs!) on a filesystem on the local disk (e.g. in folder Documents of his home directory) LibreOffice hangs for a big time and maybe after an hour (with luck) the document of 1 page text is saved. If the network is switched off, LibreOffice saves within a second. When network is on, all monted network shares are accessible and works well. Also I can save any document with other programs without any issues. I took a backtrace and a strace of this behaviour two times: - one with network active (where the problem is) - one with networking deactivated (where no problem is) Please help to solve this issue. I guess that LibreOffice is asking the network stack for information (why, if we store on a local filesystem?) and running very long until we get a timeout. Thanx in advance for your help! Erm... just to be complete: Of course I already deleted the .libreoffice directory first but the problem remains. Regards Michael
@m.marre@web.de Thank you for your feedback, I regret that you have that problem. Unfortunately you are wrong here, this is the Bug tracking system, not a helpdesk! Life cycle for 3.3 is terminated, no fix can be done except the bug will be reproduced with a current version. You can get assistance on <http://ask.libreoffice.org/questions/> or on the public users mailing list <users@libreoffice.org>, a mailing list from <http://www.documentfoundation.org/contribution/#lists> or <http://wiki.documentfoundation.org/Local_Mailing_Lists> As a first step I recommend to do a test with a renamed User profile <https://wiki.documentfoundation.org/UserProfile> And a parallel installation of a current Version <https://wiki.documentfoundation.org/Installing_in_parallel> Please feel free to reopen this Bug if discussion with others leaded to an assessment that we have a LibO bug with a current Version.