1. Open new (blank) document (writer or calc), open File-Properties -> CRASH
2. Open existing document (XLS, XLSX, ODS), open File-Properties -> CRASH
LO 126.96.36.199 (build id: 9bb7eadab57b6755b1265afa86e04bf45fbfc644)
OS: MS Windows Server 2012 Standard
Unable to reproduce. Win7, version: 188.8.131.52
ID build: 9bb7eadab57b6755b1265afa86e04bf45fbfc644
Hello Denis, Raal,
I didn't reproduce with
LO 184.108.40.206 Build ID: 7d55112667c8fcddb67bc3803796b46c93aa56b0
LO 220.127.116.11.0+ Build ID: 77c6ce66696a997269b9fe4dfed1dc2e51ecd00e
TinderBox: Win-x86@42, Branch:libreoffice-4-3, Time: 2014-10-17_16:12:56
LO 18.104.22.168.alpha1+ Build ID: a8c24b25fd9fb21097a08a22797bf61b59099ea1
TinderBox: Win-x86@39, Branch:master, Time: 2014-10-21_06:33:33
Under Windows 7 Home Premium.
Did you try to rename your profile?
I can't rename profile, bacouse it is production terminal server. We tried:
- removing LO profile folder (in %USERPROFILE%\AppData\Roaming) - no results;
- reinstalling LO - no results;
- reboot server (we did it first )) ) - no results.
So, we have removed LO and back to previous version (4.2.7).
So - it seems likely this is based on the profile as now 3 of us can not reproduce. If you cannot test further with a fresh profile I'm afraid there isn't much we can do.
Are you able to zip the profile and attach it? Setting to NEEDINFO as the information currently provided is not sufficient for anyone to reproduce. If you can at least attach the profile set to UNCONFIRMED. Thank you
Confirmation of crash status which occurs when File->Properties is selected. Very frustrating (to put it mildly)!
Also applies to version 22.214.171.124. :(
So another thing that you could do is attach a zip of the profile to this bug....without that I'm afraid we'll have to close the bug as INVALID because no one else can reproduce it and the bug doesn't have the needed information.
Thanks, Joel. I'm new to sending feedback on bugs, so maybe someone could enlighten me on "profile". Is it generated automatically, or what? If not automatically, what should a profile report contain?
BTW, I reinstalled the latest version, this time after completely removing LO, instead of over an old version of LO. Hmm, I cannot now reproduce this bug. :)
About the LO directory profile, you'll find the location here:
So zip the directory and attach it by using this link:
But first, please give a new try with last stable LO version 5.0.3
So reinstalling made it work. In that case I am going to close this bug.