Bug 145958 - LibreOffice start menu opens, but won't open any document, new or existing
Summary: LibreOffice start menu opens, but won't open any document, new or existing
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
7.3.0.0 alpha1+
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-11-30 01:33 UTC by kara.l.anderson07@gmail.com
Modified: 2023-07-25 03:16 UTC (History)
2 users (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 kara.l.anderson07@gmail.com 2021-11-30 01:33:52 UTC
Description:
Hi, I'm stumped by an issue I'm having with LibreOffice. As of yesterday, I can't open any document, new or saved. The start menu will open, but when I click a document to open it does nothing. When I try to open the document directly from the file, without going through the LibreOffice start menu, it will flash onto the screen as if it's going to open, and then disappear. When I look in the task manager, there's nothing there.

I just uninstalled and reinstalled the latest version (as of this morning, Nov. 28 2021), and I have no updates for my OS (Windows 10).

I can't find any articles on the LibreOffice help pages or their forum describing this problem, it seems like the most common problem is that the application won't open at all.

I've tried opening it in safe mode through the command line, and resetting to factory settings, with no luck.


more info:

- yes I've restarted my computer multiple times

- I've tried to open .odt and .docx files, to no avail

- LibreOffice info:

Version: 7.2.3.2 (x64) / LibreOffice Community

Build ID: d166454616c1632304285822f9c83ce2e660fd92

CPU threads: 12; OS: Windows 10.0 Build 19041; UI render: Skia/Vulkan; VCL: win

Locale: en-CA (en_CA); UI: en-US

Calc: threaded

Steps to Reproduce:
1. open application from link on desktop 
2. try to open a new file (of any type, writer, calc, etc.)
OR
1. Click to open a file directly from file explorer (LibreOffice is set to default app)


Actual Results:
1. open application from link on desktop 
2. try to open a new file (of any type, writer, calc, etc.)
3. Nothing happens
OR
1. Click to open a file directly from file explorer (LibreOffice is set to default app)
2. The screen flashed as if opening
3. Disappears, no task running in background.

Expected Results:
documents should open


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
Version: 7.2.3.2 (x64) / LibreOffice Community

Build ID: d166454616c1632304285822f9c83ce2e660fd92

CPU threads: 12; OS: Windows 10.0 Build 19041; UI render: Skia/Vulkan; VCL: win

Locale: en-CA (en_CA); UI: en-US

Calc: threaded


Based on recommendations from a Reddit post I made on r/LibreOffice I've tried:

"Try excluding soffice.bin from any AV (especially Defender) scanning.
EDIT: Also try turning off Skia."
- no change

"Shutdown Quickstarter, in taskbar, if running. Enable Show hidden files and folders in Windows Folder options. Browse to:

C:\Users\Your Username\AppData\Roaming\LibreOffice

Copy the 4 folder to your desktop, then delete the entire 4 folder from the above location. Try opening Writer or a document. If this works, your profile folder (extensions, toolbar layouts templates etc.), is corrupted."
 - no change

And opening through the command line gives me no information
Comment 1 onlyshilps 2021-12-03 07:46:31 UTC
Thank you for reporting the bug. I can not reproduce the bug in
Version: 7.4.0.0.alpha0+ (x86) / LibreOffice Community
Build ID: 4ac9032163cf55c160145373e7c41741c9c339ca
CPU threads: 4; OS: Windows 10.0 Build 18362; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL
Comment 2 Buovjaga 2021-12-13 17:27:21 UTC
(In reply to kara.l.anderson07@gmail.com from comment #0)
> "Try excluding soffice.bin from any AV (especially Defender) scanning.
> EDIT: Also try turning off Skia."
> - no change

So can you confirm in Help - About you are not seeing Skia/Vulkan and the problem persists?
Comment 3 Tammy 2022-12-24 18:10:33 UTC
I am unable to reproduce the bug in:

Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 780d55199e54fafc3784691d5cf716c1bb92b0aa
CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded

Version: 7.4.2.3 (x64) / LibreOffice Community
Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf
CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded
Comment 4 Buovjaga 2022-12-25 07:57:16 UTC
(In reply to Buovjaga from comment #2)
> (In reply to kara.l.anderson07@gmail.com from comment #0)
> > "Try excluding soffice.bin from any AV (especially Defender) scanning.
> > EDIT: Also try turning off Skia."
> > - no change
> 
> So can you confirm in Help - About you are not seeing Skia/Vulkan and the
> problem persists?

Renewing this request.
Comment 5 QA Administrators 2023-06-24 03:14:38 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2023-07-25 03:16:30 UTC
Dear kara.l.anderson07@gmail.com,

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