Bug 146195 - So much wrong with 7.2.4.1
Summary: So much wrong with 7.2.4.1
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
Version:
(earliest affected)
7.2.4.1 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-12-12 14:08 UTC by John Suter
Modified: 2022-07-12 03:33 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John Suter 2021-12-12 14:08:06 UTC
Description:
This should never have been released.
(1) Fontwork does not save.
(2) Will not allow highlight (marking) of text in writer.
(3) Menus are completely blank, no text. Have to quit program in Task Manager if there was a change to the document as there is no text in the Save dialog window.

Steps to Reproduce:
1. Attempted repair first.  Didn't work.
2. Completely removed it and reinstalled it. Didn't work.


Actual Results:
Will not allow marking of text via mouse or keyboard.  Will not save Text Fontwork in the document.  Menus are blank and have no text whatsoever.

Expected Results:
Expect it to work correctly.


Reproducible: Always


User Profile Reset: No



Additional Info:
This probably should not have been released yet.
Comment 1 V Stuart Foote 2021-12-12 18:10:32 UTC
Can not confirm Windows 10 (21H2), I've had no issues with any of the 7.2 branch including an update to 7.2.4 rc1

Able to select and highlight text (a DF action). Able to insert FontWork object. Able to save to ODF Text (.odt) and reopen.

Needinfo:

Did you verify hash values for the installer?
MD5	3d2b1e00e09fe3c84ed0afc5f759392f
SHA-1 029c55d4a348beab45f597ae13709c8c976f80ca
SHA-256	d8a4b685144c26fe57766f24eb9037fc9a53a82e6c7dfdac6b54ea212e063b05

Please provide text from LibreOffices's Help -> About. Likewise your Windows system details, os and GPU and driver (from a run of msinfo32.exe--the Summary panel, and the Component -> Display panel).

If help about shows your LibreOffice instance is in Skia/Vulkan--please provide the "skia.log" from your LibreOffice user profile "C:\Users\<username>\AppData\Roaming\LibreOffice\4\cache\skia.log"

With your "reinstall" did you delete your user profile? I.e. delete or rename the folder.

Please do so and fully uninstall, then install from command line and capture an installation log. Use an administrative priv command window and issue the command:  "msiexec.exe /i LibreOffice_7.2.4.1_Win_x64.msi /L*v  lo7241instLog.txt" either default or custom with configurations--languages and built-in extensions--as you like.

Relaunch and if all is good, great. Otherwise zip and post your install log.

=-testing-=

Version: 7.2.4.1 (x64) / LibreOffice Community
Build ID: 27d75539669ac387bb498e35313b970b7fe9c4f9
CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster [or Vulkan]; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded

either Skia software rendering or with Skia Vulkan and this driver

RenderMethod: vulkan
Vendor: 0x8086
Device: 0x8a52
API: 1.2.195
Driver: 0.404.1069
DeviceType: integrated
DeviceName: Intel(R) Iris(R) Plus Graphics
Denylisted: no
Comment 2 QA Administrators 2022-06-11 03:29:35 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2022-07-12 03:33:14 UTC
Dear John Suter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp