Bug 123422 - After install (Flatpak) it will not start
Summary: After install (Flatpak) it will not start
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
Version:
(earliest affected)
6.2.0.3 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-02-13 00:55 UTC by Walter Harrison Stoermer
Modified: 2019-11-08 03:39 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 Walter Harrison Stoermer 2019-02-13 00:55:46 UTC
Description:
After install (Flatpak) it will not start. It hangs on the splash screen or the bar loads and it goes away, but nothing else opens. 

Steps to Reproduce:
1. Began with no LibreOffice on the computer and Flatpak fully installed.

2. Start LibreOffice or one of the programs (Writer, Calc, etc) through terminal or clicking the icon.  

3. Watch the fail

Actual Results:
Install through the app center, bash, or install from Flatpak website (by clicking "install" at the top of the page). I have started it by clicking on the icon and through the terminal, but it will not get past the splash screen. Sometimes the splash screen will load all of the way and disappear, or it will freeze and stay that way until I "kill" the operation in system monitor

Expected Results:
That LibreOffice will run and I can use it.


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
Using an HP-17" Pavillion/AMD A8/8GB RAM/1TB/ Fedora 29
Comment 1 Xisco Faulí 2019-02-13 10:04:56 UTC
Hello,
Thanks for reporting this issue.
Do you use Wayland? bug 123080 ?
Comment 2 Walter Harrison Stoermer 2019-02-13 22:03:54 UTC
(In reply to Xisco Faulí from comment #1)
> Hello,
> Thanks for reporting this issue.
> Do you use Wayland? bug 123080 ?

Yes, I am running Wayland. 

Update: I seemed to solve the problem by running in safe mode and disabling the DirectGL, but I have never had an office program require that before. 

It works, for now, and I like the new Tabbed user interface. It makes it easier to find commands, and it makes it easier for an old MSO user like me to switch over. I am a massive fan of LibreOffice and Flatpak, and fixing this makes my Linux experience much better.

If I switch distros, I now know what to do, but I like Fedora, and I hope to stay with it for a long time.

Thank you!
Comment 3 Xisco Faulí 2019-02-14 14:56:02 UTC
(In reply to Walter Harrison Stoermer from comment #2)
> (In reply to Xisco Faulí from comment #1)
> > Hello,
> > Thanks for reporting this issue.
> > Do you use Wayland? bug 123080 ?
> 
> Yes, I am running Wayland. 
> 
> Update: I seemed to solve the problem by running in safe mode and disabling
> the DirectGL, but I have never had an office program require that before. 

Did you mean OpenGL?
Does it fail if you enabled it again ?
if so, could you please share the OpenGl info ? -> https://wiki.documentfoundation.org/OpenGL#Linux_.2F_BSD
Comment 4 QA Administrators 2019-10-08 02:29:17 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2019-11-08 03:39:10 UTC
Dear Walter Harrison Stoermer,

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