https://bugs.documentfoundation.org/show_bug.cgi?id=147572
Mike Kaganski <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |NOTABUG Status|UNCONFIRMED |RESOLVED --- Comment #10 from Mike Kaganski <[email protected]> --- (In reply to Michał Piotrowski from comment #9) > I increased a space for offline files and cleared a "cache" (or > something like that for offline files). > After that LO can close correctly Great that you found it! > but another strange thing start happen: > after opening and closing a few documents it starts to hangs on opening > (also tried to access or write some files). > My temporal solution is to disable offline files at all and it solves this > problems correctly but I must to investigate it later. >From my times of administrating a Windows-based domain on my ex-job, I remember struggling with RDP-related quotas, roaming profiles, and some applications that regularly made those blow (including AutoCAD and OOo/LO). I don't remember the RDP-related details (it was more than 7 years ago - time flies...), but I do remember excluding some program-specific %appdata% subfolders from roaming profile content in respective group policies (adding exclusion of paths). Yes, the configuration of that is not straightforward. > Btw. probably I can be not alone in that kind of problems, so maybe it's a > good idea to set some kind of timeout (number of tries) for saving this user > configuration in LO? No, not at this time, since it's still not affecting many, and at this point, it's better to create a FAQ at wiki ( https://wiki.documentfoundation.org/Faq/General ) - I ask you to do that when you have some time, to dump the information you gathered. At some point, the FAQ could enable to see the problem as a whole; but implementing a "timeout" means great additional complexity at the code that is really fragile and critical (shutdown, which may happen at logoff time, must be as fast as possible as documented by MS; and timing out means we need to create a dedicated thread for the writing, and synchronizing on it (blocking), with all respective overhead for everyone). I close it NOTABUG (just because there's no suitable "COMBINATION_OF_PARTICULAR_SYSTEM_SETTINGS_AND_OUR_PROCESSING" resolution), since we have found the problem (a system configuration blocking the write on system level), and we don't have something to fix at our side for the time being. Thank you for filing the issue; and again - please do create a FAQ with your findings, which might benefit other admins. Also: please feel free to put it back to UNCONFIRMED, if you feel it should not be closed; please provide explanation why you think so, if you do. -- You are receiving this mail because: You are the assignee for the bug.
