Bug 145921 - Crash in: SfxItemSet::Get(unsigned short,bool) - EDITING
Summary: Crash in: SfxItemSet::Get(unsigned short,bool) - EDITING
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
7.0.4.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-11-27 21:04 UTC by to.give.out
Modified: 2021-12-25 19:28 UTC (History)
1 user (show)

See Also:
Crash report or crash signature: ["SfxItemSet::Get(unsigned short,bool)"]


Attachments
Document being edited when crash occured (redacted) (14.17 KB, application/vnd.oasis.opendocument.calc)
2021-11-27 21:04 UTC, to.give.out
Details

Note You need to log in before you can comment on or make changes to this bug.
Description to.give.out 2021-11-27 21:04:21 UTC
Created attachment 176541 [details]
Document being edited when crash occured (redacted)

This bug was filed from the crash reporting server and is br-71b7ebfe-b93a-435a-bfde-e3fe64a5ce5c.
=========================================

So far as I have noticed, this has not been a recurring problem.  I filed this under Calc because I was using calc when the crash happened.

What I was doing when the crash happened:

LibreOffice had been left open for several days, probably a week or more with both writer and calc files open.  Perhaps notable is that I had both the attached file and an .xlsx file open at once in calc.

I had recently created the only merged cell in the attached document (which has been redacted a bit for privacy reasons), and was editing the text in that cell.  The G on the second line was repeatedly auto-capitalizing, and the "undo" button was greyed out.  I eventually figured out how to get around that.  Shortly after this, the crash happened.  If I recall correctly, the very last thing I did before the crash was: Switched the text alignment back and forth between aligned to the left and centered.
Comment 1 Julien Nabet 2021-11-27 21:39:57 UTC
Without a way to reproduce this, it would be quite difficult to reproduce this.
Moreover, 7.0 branch is EOL. You can try 7.1.7 (it's the last version 7.1 branch) or the brand new 7.2.3.
You can also rename your LO directory profile (see https://wiki.documentfoundation.org/QA/FirstSteps#Corrupted_user_profile)

Let's put this one to NEEDINFO for the moment.
Comment 2 Telesto 2021-11-28 12:37:28 UTC
I have seen similar report reporting this crash also related to text alignment
Not able to repro though..

This part I find interesting "I eventually figured out how to get around that."
I'm not able to do that.
Comment 3 to.give.out 2021-12-12 00:46:36 UTC
(In reply to Telesto from comment #2)

> I have seen similar report reporting this crash also related to text
> alignment
> Not able to repro though..

Do you have the link to the similar report handy?
 
> This part I find interesting "I eventually figured out how to get around
> that."
> I'm not able to do that.

To be clear, I got around the auto-captialize function.  As far as I know, this has nothing to do with text alignment.  If you are interested in the auto-capitaliation part, let me know. 

I composed my initial post in a hurry, and I can see how it could be misinterpreted.  If we are focusing on the text alignment as the probable trigger for the crash, this is the relevant part of the second paragraph of my initial post:

"I had recently created the only merged cell in the attached document, and was editing the text in that cell. ... If I recall correctly, the very last thing I did before the crash was: Switched the text alignment back and forth between aligned to the left and centered."
Comment 4 to.give.out 2021-12-12 00:49:30 UTC
EOL = end-of-life?

repro = reproduce?
Comment 5 QA Administrators 2021-12-12 04:22:00 UTC Comment hidden (obsolete)
Comment 6 Julien Nabet 2021-12-16 20:29:57 UTC
Yes EOL is for "End Of Life" and "repro" for "reproduce".
Meanwhile, there have been 7.1.8 and 7.2.4 because of an CVE ("Common Vulnerabilities and Exposures").
Would it be possible you find a step by step process to reproduce the crash with 7.1.8 or 7.2.4?
Comment 7 to.give.out 2021-12-21 20:39:46 UTC
(In reply to Julien Nabet from comment #6)
> Yes EOL is for "End Of Life" and "repro" for "reproduce".
> Meanwhile, there have been 7.1.8 and 7.2.4 because of an CVE ("Common
> Vulnerabilities and Exposures").
> Would it be possible you find a step by step process to reproduce the crash
> with 7.1.8 or 7.2.4?

I have only seen this crash (with Calc) once, and I reported it kind of on an impulse.  Also, LibreOffice is not critical for me.  So I do not have time to play around with it.  Sorry to disappoint.

(I am also concerned that a more recent version may be more broken or broken in a more problematic way than the version I am using now.  Maybe a portable version of 7.1.8 or 7.2.4 would solve this concern?)
Comment 8 QA Administrators 2021-12-22 05:41:13 UTC Comment hidden (obsolete)
Comment 9 Julien Nabet 2021-12-22 09:47:20 UTC
Ok let's put this one to RESOLVED/INSUFFICIENTDATA.

Don't hesitate to reopen this tracker if you find the process to reproduce this with a recent LO version and after having applied this:
https://wiki.documentfoundation.org/QA/FirstSteps
Comment 10 to.give.out 2021-12-25 19:28:15 UTC
Ok.  A thought:  If the bug is useless if it is not from the most recent version, perhaps the "LibreOffice has crashed" dialogue text needs improvement.  Specifically, to explicitly state that you need to check the version of LibreOffice installed against the current version of LibreOffice before submitting a bug report.  If you guys are interested, I would be willing to contribute to the rewording, as time permits.