Bug 117577 - Crash in: SfxItemPool::GetFrozenIdRanges() const in Linux from 5.4
Summary: Crash in: SfxItemPool::GetFrozenIdRanges() const in Linux from 5.4
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.4.0.0.alpha0+
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-12 10:28 UTC by opensuse.lietuviu.kalba
Modified: 2020-05-20 03:40 UTC (History)
2 users (show)

See Also:
Crash report or crash signature: ["SfxItemPool::GetFrozenIdRanges() const"]


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description opensuse.lietuviu.kalba 2018-05-12 10:28:23 UTC
This bug was filed from the crash reporting server and is br-9123ed89-a773-4516-88ce-769ce0de7834.
=========================================

I worked with https://bugs.documentfoundation.org/show_bug.cgi?id=117576 bug.
I simply closed all opened documents, that I was working for very long time without closing program (I suspended computer to RAM many times). There was no error while closing. 
After restarting LibreOffice, it just proposed to send this bug report.
Comment 1 Dieter 2018-05-12 16:27:08 UTC
Summary of crash signature shows, that it's only a linux issue => I changed hardware from 'All' to 'Linux'
Comment 2 Xisco Faulí 2018-06-15 08:44:36 UTC
Still reproducible in 6.0.4.2. This is a crash starting in 5.4 series...
Comment 3 Xisco Faulí 2018-06-15 08:48:27 UTC
Dear opensuse.lietuviu.kalba@gmail.com,
- have you been able to reproduce it again?
- Do you remember using the printer before the crash?
Comment 4 opensuse.lietuviu.kalba 2018-06-15 09:39:14 UTC
I did not reproduced this bug. The cause is unknown for me.
I can not associate this bug with physical printing. However I have real printer, and from time to time use it, though usually I don't print directly from LibreOffice. However I can not state, that it is not related to hardware/physical/real printing. But, indeed I very often I print to PDF from LibreOffice.
Comment 5 Xisco Faulí 2018-12-13 11:45:50 UTC
A new major release of LibreOffice is available since this bug was reported.
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 6 QA Administrators 2019-06-12 02:58:33 UTC Comment hidden (obsolete)
Comment 8 Dieter 2019-10-21 09:04:38 UTC
It seems as this is fixed, because there is no crash report wirth this signature in LO 6.3 [1]. So 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. Change to RESOLVED WORKSFORME, if the problem went away.



[1] https://crashreport.libreoffice.org/stats/signature/SfxItemPool::GetFrozenIdRanges()%20const
Comment 9 QA Administrators 2020-04-19 03:36:26 UTC Comment hidden (obsolete)
Comment 10 QA Administrators 2020-05-20 03:40:42 UTC
Dear opensuse.lietuviu.kalba,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp