How can I get my space bar working again in LibreOffice Writer?

After upgrading to LibreOffice 4.2.2.1 my space bar for LibreOffice Writer English no longer works. I’m using Windows 8 English. The space bar works for everything else, so it is not a hardware problem. Can anybody help me with this problem, please?

I would do the following:

  • Check in Tools > Options > Languages > Default languages for document if this is English
    no solution
  • Reset the user profile: https://wiki.documentfoundation.org/UserProfile
    no the solution,
  • repair installation: in Control Panel > Add & Remove SW (should be the same or similar in W8)
    no solution
  • remove the entire installation of LibO but save the user profile with different name
  • install LibO new and make sure that you install only languages you need (customized installation)
    no solution
  • come back here again.

See Also: Space-related options under Language Settings > English sentence checking and Tools > AutoCorrect Options….

Thanks, ROSt52 and oweng, for your answers. But I do not know how to change the name in my user profile. My laptop used to belong to my sister, and her name is still in the user profile of the languages folders. Over a year ago, I replaced her name with mine for the computer’s startup. Still, I have never had any problems with LibreOffice in spite of this until upgrading to 4.2. Is there anything else I can do to solve this problem? I have uninstalled and reinstalled the program several times now. Also, I have checked all of the space-related boxes under Punctuation after going to English sentence checking, still no solution.

@richardrcook2, the “user profile” is the LO account, rather than the operating system account. There is no need to change the name of (in) the user profile. @ROSt53 is simply suggesting that in order to preserve existing settings, rather than delete the user profile, it can be renamed. Follow the instructions under the “Resolve corruption” section in the link provided.

Thank you oweng, my problem is solved.

@richardrcook2 - ti would be interesting to know which solution worked. Such information is helpful for others. Could you please indicate it here?