https://bugs.documentfoundation.org/show_bug.cgi?id=163960

aslamK <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #206951|Document recover dialog     |Document recovery dialog
        description|                            |

--- Comment #9 from aslamK <[email protected]> ---
Comment on attachment 206951
  --> https://bugs.documentfoundation.org/attachment.cgi?id=206951
Document recovery dialog

Version: 26.2.2.2 (X86_64)
Build ID: 620(Build:2)
CPU threads: 8; OS: Linux 6.8; UI render: default; VCL: kf5 (cairo+xcb)
Locale: en-US (en_US.UTF-8); UI: en-US
Ubuntu package version: 4:26.2.2.2-0ubuntu0.24.04.1~lo1
Calc: threaded

1. [Crash]
- The following launches LibreOffice, which crashes immediately and shows the
document recovery dialog with an empty document list.
- Clicking OK closes the dialog and opens the start center.
$ libreoffice /path/to/test.ods
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc

2. [Safe mode]
- Launching LibreOffice in safe mode, and clicking "Continue in safe mode" in
the safe mode dialog, opens test.ods as expected.
$ libreoffice --safe-mode /path/to/test.ods

3. [Correct behavior]
- Closing/quitting test.ods, then launching LibreOffice again with test.ods,
opens the spreadsheet as expected.
$ libreoffice /path/to/test.ods

4. [Crash]
- Closing/quitting test.ods, then launching LibreOffice again with test.ods,
crashes as described in #1.
$ libreoffice /path/to/test.ods
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc

So, if launched from the command line, LibreOffice launches and crashes, unless
it is launched in safe mode or the preceding launch was in safe mode.

If LibreOffice is launched through a ^.desktop file with an Exec key like the
following, the crash doesn't happen and the behavior is as expected:
Exec=xdg-open /path/to/test.ods

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to