Bug 144753 - Won't open
Summary: Won't open
Status: RESOLVED DUPLICATE of bug 144598
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.1.6.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-09-27 18:24 UTC by mike.a.nicolay
Modified: 2021-10-07 16:59 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 mike.a.nicolay 2021-09-27 18:24:29 UTC
I have downloaded 7.1.6.2 twice and installed it 4 times - it still won't open. Icon is there but when I go to click on it the program just doesn't open!
No error codes, no nothing, it just won't open.
Went to use previous version (that worked fine) but apparently that was removed when this version was installed!
Comment 1 Julien Nabet 2021-09-27 18:47:21 UTC
Could you give a try at https://wiki.documentfoundation.org/QA/FirstSteps#Graphics-related_issues_.28Skia.29 ?

If specifically this part helps:
"    Open registrymodifications.xcu in a plain text editor, and search for UseSkia text string there.
        If found, replace true with false in that line.
        If not found, add this line to the file before the final </oor:items>:

   <item oor:path="/org.openoffice.Office.Common/VCL"><prop oor:name="UseSkia" oor:op="fuse"><value>false</value></prop></item>
"
it may be a dup of an existing bug which has been fixed with next LO releases 7.1.7 and 7.2.2
Comment 2 V Stuart Foote 2021-09-27 23:10:37 UTC
The Needinfo to OP to answer the question. This is probably a dup of bug 144598

But, if you prefer not to test the simple profile adjustment that would verify, we'll lighten your burden and just resolve this insufficient detail and let you get on with things.  Update to 7.1.7 when/if released, or the upcoming 7.2.2 build in a week or so.
Comment 3 gmarco 2021-10-05 17:40:46 UTC
BAD!
I have been using LO (IT) for many years and this is the first time this has happened.
I had been using 7.1.5.2, for several days each time LO proposed me to update to 7.1.6, I didn't have time and I did it today ...
Going to the download is indicated, as usual, v.7.2.1.2 for experts or 7.1.6.2 (it is said extensively tested).
As my use, I downloaded the latter, but it didn't run and I wasted half a day figuring out why, I uninstalled and reinstalled several times without a result.
Finally I tried to install 7.2 and this works!
But, after such a long time, why is that version still suggested and present in the download, but not working?
Comment 4 V Stuart Foote 2021-10-05 17:57:35 UTC
7.1.7 build when released, or 7.2.2 out this week.  Avoid 7.1.6 or 7.2.1--both are poisoned by Clang compiler issue of bug 144598

*** This bug has been marked as a duplicate of bug 144598 ***
Comment 5 gmarco 2021-10-05 21:34:13 UTC
(In reply to V Stuart Foote from comment #4)
> 7.1.7 build when released, or 7.2.2 out this week.  Avoid 7.1.6 or
> 7.2.1--both are poisoned by Clang compiler issue of bug 144598
> 
> *** This bug has been marked as a duplicate of bug 144598 ***

It would be correct for all information to be "timely" and "correct"!
As I said, in 7.1.5 the invitation was to upgrade to 7.1.6, on the IT download site 7.1.6.2 is still proposed as extensively tested.
In addition to this 7.2.1.2 is proposed, finally I installed it and it seems to work (at least it goes running!).
Now you say this too is unreliable ....
Comment 6 gmarco 2021-10-07 15:42:15 UTC
(In reply to V Stuart Foote from comment #4)
> 7.1.7 build when released, or 7.2.2 out this week.  Avoid 7.1.6 or
> 7.2.1--both are poisoned by Clang compiler issue of bug 144598
> 
> *** This bug has been marked as a duplicate of bug 144598 ***

Today also v.7.1.6.2 is opening and running.
Is that sentence right? 
Is the build 7.1.6.2 really poisoned?