Bug 127826 - "Cell Style Modify" window can crash while interacting with 2 documents
Summary: "Cell Style Modify" window can crash while interacting with 2 documents
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.3.1.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Crash
  Show dependency treegraph
 
Reported: 2019-09-27 14:11 UTC by stdedos
Modified: 2023-04-04 08:42 UTC (History)
6 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 stdedos 2019-09-27 14:11:39 UTC
Description:
libreoffice-6.3.1.2-snap1

If I have a workbook open, with a "Cell Style Modify" window open, then window is in a "semi-working state", e.g.: Menus work, buttons don't.

If I manage to open a file (from File->Open Recent), then, the workbook only "partially" loads.

Opening the Style sidebar gives "empty" list.

If then I close the "Cell Style Modify" window, Calc goes down on a (controllable) crash.

Actual Results:
1.
2.
3.

Expected Results:
1.
2.
3.


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 raal 2019-09-28 12:07:59 UTC
I can not confirm with Version: 6.4.0.0.alpha0+
Build ID: 186d36a7036462ae641b35004b4ffba3eeeca46f
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3;
Comment 2 m_a_riosv 2019-09-30 06:34:35 UTC
Please test with Menu/Help/Restart in Safe Mode
Comment 3 stdedos 2019-09-30 08:33:24 UTC
It worked a bit better at first - everything was loaded, and the document was interactive and all. I attempted to work with the new file (I had opened an xlst template), and then I closed/discarded it.

However, when I tried again to open a file, it crashed on the same fashion.
Comment 4 Xisco Faulí 2019-09-30 10:24:40 UTC
to verify the bug. 
(Please note that the attachment will be public, remove any sensitive information before attaching it. 
See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)

I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
Comment 5 stdedos 2019-09-30 10:37:08 UTC
(In reply to Xisco Faulí from comment #4)
> to verify the bug. 
> (Please note that the attachment will be public, remove any sensitive
> information before attaching it. 
> See
> https://wiki.documentfoundation.org/QA/
> FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help
> on how to do so.)
> 
> I have set the bug's status to 'NEEDINFO'. Please change it back to
> 'UNCONFIRMED' once the requested document is provided.

Your response appears incomplete. Please fix it.

I don't believe that the documents I used are necessary. Replication steps are quite straightforward and easy; kindly try them before requesting me to attach sample files.

Additionally, the exact files I used are unlikely to be provided; there is too much scrubbing that needs to be done.
Comment 6 Xisco Faulí 2019-11-08 12:06:52 UTC
Could you please try to reproduce it with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version.
Comment 7 stdedos 2019-11-08 12:28:52 UTC
Define "latest version".

Please keep in mind, that the only versions I am considering testing would be:
* The latest available on a Xenial PPA
* The latest available on snap
* The latest available on AppImage

I won't compile/install from sources, neither will I manually install a debian package, making "complicated" changes to my normal workstation.

Also, any testing will have to be done at least after one week's time.
Comment 9 stdedos 2020-09-14 10:47:00 UTC
(In reply to Buovjaga from comment #8)
> You can use a debug build (-dbg) and try to get a backtrace of the crash: 
> https://dev-builds.libreoffice.org/daily/master/current.html
> https://wiki.documentfoundation.org/Installing_in_parallel/Linux
> https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.
> 2FLinux:_How_to_get_a_backtrace

Is it that complicated to promote bare-bones backtrace capabilities to production packages?

As I said,

> Please keep in mind, that the only versions I am considering testing would
> be:
> * The latest available on a Xenial PPA
> * The latest available on snap
> * The latest available on AppImage

and I don't understand why I have to do the extra 10s of miles to side-by-side install a debug build to triangulate a rare bug. I have a very niche use-case for Calc, which I don't want to de-stabilize even more from getting master@daily
Comment 10 Buovjaga 2020-09-14 11:01:43 UTC
(In reply to stdedos from comment #9)
> (In reply to Buovjaga from comment #8)
> > You can use a debug build (-dbg) and try to get a backtrace of the crash: 
> > https://dev-builds.libreoffice.org/daily/master/current.html
> > https://wiki.documentfoundation.org/Installing_in_parallel/Linux
> > https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.
> > 2FLinux:_How_to_get_a_backtrace
> 
> Is it that complicated to promote bare-bones backtrace capabilities to
> production packages?

No. You can check, if your Xenial PPA provides debug symbol packgages as well. At least Ubuntu's non-PPA packages do.

> As I said,
> 
> > Please keep in mind, that the only versions I am considering testing would
> > be:
> > * The latest available on a Xenial PPA
> > * The latest available on snap
> > * The latest available on AppImage
> 
> and I don't understand why I have to do the extra 10s of miles to
> side-by-side install a debug build to triangulate a rare bug. I have a very
> niche use-case for Calc, which I don't want to de-stabilize even more from
> getting master@daily

From what I remember, the dbg builds don't require any extra miles. You just have to extract the archive and then you can run program/soffice
Comment 11 Xisco Faulí 2021-07-07 10:31:27 UTC
Hello,
Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Comment 13 QA Administrators 2021-07-08 03:43:20 UTC Comment hidden (obsolete)
Comment 14 Stéphane Guillou (stragu) 2023-04-04 08:42:55 UTC
I haven't been able to reproduce using Ubuntu 20.04 with GNOME 3.36.8 and:

Version: 7.4.6.2 / LibreOffice Community
Build ID: 5b1f5509c2decdade7fda905e3e1429a67acd63d
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

I am unable to use the main menu while I am modifying a cell style (e.g. style sidebar, cell styles > right-click on Default > Modify...).
I tested with two documents open at the same time too.

I also tried the latest snap from snapcraft.io:

Version: 7.5.1.2 (X86_64) / LibreOffice Community
Build ID: 81bce3cd17f5e01886721863a4fa0d99f91033a6
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

We haven't been able to get more information to be able to troubleshoot, including detailed information from Help > About LibreOffice, or tests with a more recent version of LibreOffice.

If you happen to witness the same issue in the latest snap or appimage (as you said you'd be happy to try), please provide more information to reproduce the problem, possibly with a test document, and set this report back to "unconfirmed".