Bug 116604 - Java.io file not found on application startup
Summary: Java.io file not found on application startup
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.4.5.1 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-24 12:48 UTC by Colin
Modified: 2018-03-24 15:18 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Screen grab of the alert pane (29.76 KB, image/png)
2018-03-24 12:48 UTC, Colin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Colin 2018-03-24 12:48:44 UTC
Created attachment 140854 [details]
Screen grab of the alert pane

Opening an existing document pinned to the start bar shortcut produces a Java.io file not found exception trying to access the language tool log.
Only appears to happen on the first access after a system start but I'm not sure if the error rectifies or the report is suppressed if it has already been advised within the current startup
Comment 1 Julien Nabet 2018-03-24 13:07:21 UTC
Could you try this:
- uninstall language tool
- rename your LO directory profile (see https://wiki.documentfoundation.org/UserProfile#Windows)
- install language tool (Languagetools website provides LanguageTool-4.0.oxt)
?

Of course, if you use LO 32 bits, you must use Java 32 bits
..LO 64bits->Java 64bits
Comment 2 Colin 2018-03-24 13:24:31 UTC
That user profile folder also holds a file called registrymodifications.xcu.
Is removing that from access going to have further impact - should I clean the registry as well?
Also, My user root folder contained a file called .languagetool-ooo.cfg. I assume a reinstal of the Language tool would be preferred without any prior configuration settings cluttering the place up so that has been deleted. Still recoverable so please adise soonest if I should not have used my own initiative.
Comment 3 Colin 2018-03-24 13:35:15 UTC
I've just noticed. I'm running LO.5 and the AppData only contains a LO>4 Sub directory. Could that be a significant factor?
Comment 4 Colin 2018-03-24 13:54:13 UTC
Having just read the entire text at the link you provided it states that unusual effects can result if an older version profile folder is targeted. V.5 was installed over a month ago and in all the years I have used LO (I moved from OOO when you did), I certainly don't recall specifically telling it to reuse a profile. I may be wrong and perhaps did indicate a re-use as upgrades always manage to lose my special sort sequences but the error has only been occurring in the last week or so.
Are any other applications likely to access and leave the offending file locked or is it exclusively LO territory?
Would it make life simpler if I just completely uninstalled everything associated with LO including manually clearing all ProgData / AppData locations and registry entries and simply reinstalled current stable release?
Comment 5 Dennis Roczek 2018-03-24 14:12:34 UTC
(In reply to Colin from comment #3)
> I've just noticed. I'm running LO.5 and the AppData only contains a LO>4 Sub
> directory. Could that be a significant factor?

no, libreoffice 5 and 6 do use the same folder as nothing has changed. This is indeed confusing, but all works correctly. :-)
Comment 6 Dennis Roczek 2018-03-24 14:13:56 UTC
(In reply to Colin from comment #2)
> That user profile folder also holds a file called registrymodifications.xcu.
> Is removing that from access going to have further impact - should I clean
> the registry as well?
> Also, My user root folder contained a file called .languagetool-ooo.cfg. I
> assume a reinstal of the Language tool would be preferred without any prior
> configuration settings cluttering the place up so that has been deleted.
> Still recoverable so please adise soonest if I should not have used my own
> initiative.

Simply rename the complete folder 4 to (for example) "4backup".

All preferences, extensions, user dictionaries, etc. are included in that folder.
Comment 7 Dennis Roczek 2018-03-24 14:22:18 UTC
(In reply to Colin from comment #4)
> [...] simply reinstalled current stable release?
yes, please try also the latest released version
Comment 8 Colin 2018-03-24 15:07:24 UTC
(In reply to Dennis Roczek from comment #7)
> (In reply to Colin from comment #4)
> > [...] simply reinstalled current stable release?
> yes, please try also the latest released version

It wasn't necessary to completely uninstall.
After removing languagetool and renaming the user profile it still didn't change but then I simply deleted all Languagetool files from my USER root and rebooted which solved the problem.
The log was recreated and survived a couple of reboots but the config file hasn't been recreated.
Perhaps it only does that once it's been active in the program. Will find out soon.
I think it's safe to set the status to resolved or not a bug. I will leave that to you as they are obviously two different criterea.
Quick question - Do I just delete the 4backup profile now it's solved?
Also
A big thank you to all of you.
Colin
Comment 9 Dennis Roczek 2018-03-24 15:18:21 UTC
(In reply to Colin from comment #8)
> Quick question - Do I just delete the 4backup profile now it's solved?
> Also
it contains your old settings; feel free to delete it, if you do not need them any longer.

> A big thank you to all of you.
You're welcomed.
> Colin
Dennis Roczek