Bug 125562 - LibreOffice fonts aren't installed with LibreOffice
Summary: LibreOffice fonts aren't installed with LibreOffice
Status: RESOLVED DUPLICATE of bug 97982
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
(earliest affected) release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: Installer-Windows
  Show dependency treegraph
Reported: 2019-05-28 19:56 UTC by João Paulo
Modified: 2019-06-19 02:49 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description João Paulo 2019-05-28 19:56:49 UTC
After removing LibreOffice 64 bits and installing LibreOffice 64 bits on Windows 10, I noticed the Caladea font family wasn't installed.

After checking the list at https://wiki.documentfoundation.org/Fonts, I could verify the following fonts are missing:

* Caladea
* Carlito
* DejaVu Sans
* DejaVu Sans Condensed
* DejaVu Sans Mono
* DejaVu Serif Condensed
* Gentium Book Basic
* Liberation Sans
* Liberation Serif
* Linux Biolinum G
* Linux Libertine Display G
* Linux Libertine G
* OpenSymbol
* Noto Sans
* Source Code Pro
* Source Sans Pro
* Source Serif Pro

Steps to Reproduce:
1. Have LibreOffice 64 bits installed on Windows 10.
2. Verify the fonts at https://wiki.documentfoundation.org/Fonts are installed.
3. Uninstall LibreOffice
3. Install LibreOffice 64 bits.

Actual Results:
The fonts listed at https://wiki.documentfoundation.org/Fonts are missing. Documents that use them (because it was installed before) have their layouts and fonts changed.

Expected Results:
The fonts listed at https://wiki.documentfoundation.org/Fonts should be installed, as they were installed before.

Reproducible: Always

User Profile Reset: No

Additional Info:
I don't thinkt there is an easy workaround because one needs to find and download all the font families listed at https://wiki.documentfoundation.org/Fonts so documents formatted with them are correct again.
Comment 1 Timur 2019-06-18 11:21:09 UTC
I'll mark as a duplicate of older similar bug. 
But, are you sure this is reproducible? 
Did you try more times? 
Did you reboot computer in the meantime?

*** This bug has been marked as a duplicate of bug 97982 ***
Comment 2 João Paulo 2019-06-18 21:40:41 UTC
I rebooted after an uninstall then installed again. Sorry I didn't mention here already (I forgot to save the bug's web page address to revisit it).

I think rebooting after uninstall functions as a workaround.

Maybe the .MSI package from the older version didn't unregister correctly the fonts after uninstalling, then a reboot/logoff was necessary so Windows would rescan installed/registered fonts and the .MSI package for the new version could register the fonts again.