Bug 105782 - Snap package crashes when using native load/save dialogs
Summary: Snap package crashes when using native load/save dialogs
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
5.3.0.2 rc
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: snap
Keywords:
Depends on:
Blocks: Crash
  Show dependency treegraph
 
Reported: 2017-02-05 23:56 UTC by ppa
Modified: 2022-10-19 15:28 UTC (History)
3 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 ppa 2017-02-05 23:56:29 UTC
Description:
If Libreoffice is set to use native load/save dialogs (not the Libreoffice ones), any opening of a load/save dialog will crash. This has always been the case with snap packages of Libreoffice and it still affects the latest build (5.3.0.3 snap build)

Steps to Reproduce:
1. sudo snap install libreoffice
2. In Tools - Options - General - Open/Save dialogs, disable 'Use LibreOffice dialogs'
3. Perform any action that involves an open/save dialog (for example, File - Save As)

Actual Results:  
LibreOffice crashes. If the 'Use LibreOffice dialogs' option is enabled, it works as expected.

Expected Results:
An open/save dialog should appear


Reproducible: Always

User Profile Reset: Yes

Additional Info:


User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.0
Comment 2 QA Administrators 2018-03-23 03:35:11 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2020-03-23 02:58:51 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2022-03-24 03:41:13 UTC
Dear ppa,

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