Bug 97982 - DejaVu, Liberation, Linux, PT, Source Code fonts damaged after an upgrade (ttf already in use?)
Summary: DejaVu, Liberation, Linux, PT, Source Code fonts damaged after an upgrade (tt...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
Version:
(earliest affected)
5.0.5.2 release
Hardware: All Windows (All)
: high major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 99152 99748 110427 113308 115441 125562 (view as bug list)
Depends on:
Blocks: Installer-Windows
  Show dependency treegraph
 
Reported: 2016-02-18 14:42 UTC by Timur
Modified: 2024-09-09 19:21 UTC (History)
7 users (show)

See Also:
Crash report or crash signature:


Attachments
Sample of fonts display with WinFontsView (17.98 KB, text/html)
2016-02-18 14:44 UTC, Timur
Details
Sample of fonts display with WinFontsView (34.52 KB, image/jpeg)
2016-02-18 14:48 UTC, Timur
Details
Verbose install log (1.77 MB, application/x-7z-compressed)
2016-10-27 12:06 UTC, Timur
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Timur 2016-02-18 14:42:01 UTC
After a centralized upgrade to dozen of various Windows computers (XP, 7, 10) from LO 4.4.6 to LO 5.0.5, some of them (not related to Windows version) lost some fonts.

There were no DejaVu, Liberation, Linux, PT family of fonts in C:\Windows\Fonts. WinFontsView listed those fonts, but without sample. Manual copying fixed them with the warning that fonts already existed.

Another installation of 5.0.5 didn't fix the issue where fonts were missing after the first installation. But, it didn't delete them where they were previously copied after the first deletion. Then, installation repair fixed Liberation, Linux, PT but it didn't fix DejaVu.
Comment 1 Timur 2016-02-18 14:44:03 UTC Comment hidden (me-too)
Comment 2 Timur 2016-02-18 14:48:49 UTC
Created attachment 122770 [details]
Sample of fonts display with WinFontsView
Comment 3 Andras Timar 2016-02-18 15:33:13 UTC
Oh well... I did what I could with bug 76239. I believe we are doing the same as MS Office installer, in regards to fonts.
Comment 4 Timur 2016-02-18 16:44:58 UTC
I uninstalled 5.0.5 and installed 4.4.6 again but DejaVu wasn't repaired. I installed it manually. Next manual installation retained all fonts.
So I couldn't find a rule how this happens.
Comment 5 Timur 2016-05-16 11:21:30 UTC
*** Bug 99748 has been marked as a duplicate of this bug. ***
Comment 6 Timur 2016-10-27 11:34:34 UTC
Same with LO 5.1.6. I guess this may be related to centralized upgrade with Lansweeper, but I don't see how exactly.

MSI (s) (F8:24) [10:43:02:320]: Verifying accessibility of file: LiberationSerif-Italic.ttf
MSI (s) (F8:24) [10:43:02:325]: Executing op: FileCopy(SourceName=LIBER~7.TTF|LiberationSerif-Regular.ttf,SourceCabKey=LiberationSerif_Regular.ttf,DestName=LiberationSerif-Regular.ttf,Attributes=16384,FileSize=388352,PerTick=65536,,VerifyMedia=1,,,,,CheckCRC=0,Version=2.0.0.0,,InstallMode=58982400,,,,,,,)
MSI (s) (F8:24) [10:43:02:326]: File: C:\Windows\Fonts\LiberationSerif-Regular.ttf;	Overwrite;	Won't patch;	New file versioned - existing file unversioned
MSI (s) (F8:24) [10:43:02:326]: Source for file 'LiberationSerif_Regular.ttf' is compressed
Error 1603. File C:\Windows\Fonts\LiberationSerif-Italic.ttf already in use.  Close the application and try again.
MSI (s) (F8:24) [10:43:02:326]: Re-applying security from existing file.
MSI (s) (F8:24) [10:43:02:327]: Transforming table Error.
Comment 7 Timur 2016-10-27 12:06:25 UTC
Created attachment 128305 [details]
Verbose install log

Some parts are localized. So "Informacija 1603. Datoteka C:\Windows\Fonts\LiberationSerif-Regular.ttf se već koristi .  Zatvorite aplikaciju i pokušajte ponovo." is translated sth. like "Error 1603. File C:\Windows\Fonts\LiberationSerif-Italic.ttf already in use.  Close the application and try again."
Comment 8 Timur 2017-06-02 13:47:27 UTC
The same deployment procedure with LO 5.2.7, again this problem. 
This time it's those fonts: (not DejaVu) again Liberation and Linux family, PT, now also Source Code family.
Comment 9 Timur 2017-08-01 10:44:28 UTC
*** Bug 110427 has been marked as a duplicate of this bug. ***
Comment 10 V Stuart Foote 2018-02-04 18:15:43 UTC
*** Bug 99152 has been marked as a duplicate of this bug. ***
Comment 11 Fabien Fellay 2018-02-04 18:39:22 UTC
*** Bug 115441 has been marked as a duplicate of this bug. ***
Comment 12 Timur 2018-03-20 12:56:47 UTC
*** Bug 113308 has been marked as a duplicate of this bug. ***
Comment 13 Mike Kaganski 2018-05-08 05:40:10 UTC
See also https://ask.libreoffice.org/en/question/152440. Isn't here a similar problem?
Comment 14 Timur 2018-05-08 07:59:24 UTC
Looks similar. 
I wrote "There were no .. fonts in C:\Windows\Fonts". But link says "Files exist in C:\Windows\Fonts". 
So I looked again in my fonts folder: dir  C:\Windows\Fonts  /q  /p
and got (just and example):
26.10.2017  12:49           301.684 NT AUTHORITY\SYSTEM    LiberationMono-Bold.ttf
19.02.2016  09:36           301.684 BUILTIN\Administrators LiberationMono-Bold_0.ttf
04.10.2012  14:24           301.684 BUILTIN\Administrators LiberationMono-Bold_1.ttf

26.10.2017  12:49           277.912 NT AUTHORITY\SYSTEM    LiberationMono-BoldItalic.ttf
19.02.2016  09:36           277.912 BUILTIN\Administrators LiberationMono-BoldItalic_0.ttf
04.10.2012  14:24           277.912 BUILTIN\Administrators LiberationMono-BoldItalic_1.ttf

26.10.2017  12:49           274.984 NT AUTHORITY\SYSTEM    LiberationMono-Italic.ttf
19.02.2016  09:36           274.984 BUILTIN\Administrators LiberationMono-Italic_0.ttf
04.10.2012  14:24           274.984 BUILTIN\Administrators LiberationMono-Italic_1.ttf

26.10.2017  12:49           313.408 NT AUTHORITY\SYSTEM    LiberationMono-Regular.ttf
19.02.2016  09:36           313.408 BUILTIN\Administrators LiberationMono-Regular_0.ttf
04.10.2012  14:24           313.408 BUILTIN\Administrators LiberationMono-Regular_1.ttf

Can't say what this means. 
What I do is installation of those fonts in batch after LO installation.
I didn't also understand whether Bug 116581 is related. I asked brgsousa to test.
Comment 15 Timur 2019-06-18 11:21:09 UTC
*** Bug 125562 has been marked as a duplicate of this bug. ***
Comment 16 QA Administrators 2021-06-18 04:02:52 UTC Comment hidden (obsolete)
Comment 17 Timur 2021-06-18 07:18:19 UTC
I cannot test anymore. Most reports were up to LO 5.4, but one for 6.2.
Maybe to keep open some more because of multiple duplicates.
Comment 18 georg.weickelt 2022-01-03 14:51:45 UTC
This problem is familiar to me. We install LibreOffice (last 7.2.4.1) under Windows 10 with a GPO. After that, the fonts are no longer registered under Windows and are not present in other applications either. A restart solves the problem.
Comment 19 chris 2022-09-09 07:52:46 UTC
In my experience, this does not happen if the installation (update) happens when no user is logged on. That may be because then the fonts are not in use.

On the other hand quite a few of the duplicates report a long list of problematic fonts, most of which would be used mainly in LibreOffice itself, which typically isn't running while being updated or installed.

The amount of my experience is three or four updates on various PCs with interactive users logged on and the fonts getting lost each time vs. 10-20 updates (again across multiple PCs) where I made sure no users were logged on and all fonts were still alive and happy afterwards. These updates were to the latest 7.x releases at the respective times.

Unfortunately I have no logs from any of them.
Comment 20 QA Administrators 2024-09-09 03:15:43 UTC
Dear Timur,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug