https://bugs.documentfoundation.org/show_bug.cgi?id=152333
Bug ID: 152333
Summary: Crash opening saved spreadsheet which was modified
with macro
Product: LibreOffice
Version: 7.5.0.0 alpha0+ Master
Hardware: All
OS: Linux (All)
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: Calc
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: jim.av...@gmail.com
Description:
A specific sequence of operations results in a Crash dialog when LO is started
again after saving a spreadsheet and exiting. The problem seems to depend on
the details of how the spreadsheet was modified before it was saved (the
modification happens in Basic macros which delete and re-create a sheet).
No crash report opens after I click "Send Crash Report". This might be a
problem where LO can not make my browser open the crash report page. While I
am using a non-standard browser (firefox-esr) I think I have configured my
desktop system to use it correctly: The command "xdg-open <url>" works.
FWIW I'm running xubuntu 22.04.1 LTS; the desktop uses xfce, not gnome.
STEPS TO REPRODUCE:
1. Download both the "t.ods" and "tickers.csv" files and place them in the /tmp
directory (tickers.csv *must* be in /tmp -- the test macro is hard-coded to
look for /tmp/*.csv)
Note: Macro security should be set to "Medium" (prompt each time).
2. /path/to/lo t.ods
Enable macros when prompted.
3. Click the yellow "Reload csv" button
(the tickers.csv file *must* be in /tmp and no other .csv files in /tmp)
4. File->Save
5. File->Exit
6. /path/to/lo t.ods
(crash dialog appears)
Note: After clicking through the crash dialogs the spreadsheet opens anyway, so
this is odd.
Steps to Reproduce:
.
Actual Results:
.
Expected Results:
.
Reproducible: Always
User Profile Reset: Yes
Additional Info:
I did delete $HOME/.config/libreoffice/r/user which is supposed to have profile
data (the 'util' directory never re-appeared, so I suspect dev builds store
profile somewhere else). I also entered "safe" mode and did "reset to
defaults".
--
You are receiving this mail because:
You are the assignee for the bug.
