Bug 111086 - Assertion failure after undo (!"EmptyProperties::SetObjectItemSet() should never be called")
Summary: Assertion failure after undo (!"EmptyProperties::SetObjectItemSet() should ne...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
6.0.0.0.alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Crash-Assert Undo-Redo
  Show dependency tree / graph
 
Reported: 2017-08-02 16:09 UTC by Telesto
Modified: 2024-09-26 03:16 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:

Attachments
Example file (216.84 KB, application/vnd.oasis.opendocument.presentation)
2017-08-02 16:10 UTC, Telesto 		Details
bt with debug symbols (gtk3) (9.10 KB, text/plain)
2017-08-03 22:02 UTC, Julien Nabet 		Details
bt with debug symbols (10.09 KB, text/plain)
2019-03-17 11:25 UTC, Julien Nabet 		Details
bts from Oops line (see previous bt) (2.44 KB, text/plain)
2019-03-17 11:33 UTC, Julien Nabet 		Details
Show Obsolete (1) View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2017-08-02 16:09:41 UTC 
Description:
Assertion failure after undo (!"EmptyProperties::SetObjectItemSet() should never be called")

Steps to Reproduce:
1. Open the attached file
2. Select all the sheets in the Slide Pane (CTRL+A)
3. Menu Slide -> Slide Master Design
4. Select a slide Design
5. Press OK
6. Undo the change (CTRL+Z)

Actual Results:  
Assertion failure after undo

Expected Results:
No Assert


Reproducible: Always

User Profile Reset: No

Additional Info:
Version: 6.0.0.0.alpha0+
Build ID: 9ca7bda2cc8b67c2d10fcb81cce8bfd4d8b79b09
CPU threads: 4; OS: Windows 6.19; UI render: default; 
TinderBox: Win-x86@39, Branch:master, Time: 2017-08-02_01:19:29
Locale: nl-NL (nl_NL); Calc: CL


User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0
Comment 1 Telesto 2017-08-02 16:10:09 UTC 
Created attachment 135078 [details]
Example file
Comment 2 Xisco Faulí 2017-08-02 16:55:19 UTC 
I can't reproduce it in

Version: 6.0.0.0.alpha0+
Build ID: 50799a721c7ddcf9475a1b79984ed64ddd7cdf57
CPU threads: 4; OS: Linux 4.8; UI render: default; VCL: gtk3; 
Locale: ca-ES (ca_ES.UTF-8); Calc: group

but I can in

Version: 6.0.0.0.alpha0+
Build ID: 1e87e93132f808ab95eab932b36bfe40d3cc607a
CPU threads: 1; OS: Windows 6.1; UI render: default; 
TinderBox: Win-x86@39, Branch:master, Time: 2017-07-25_06:09:29
Locale: es-ES (es_ES); Calc: group

WIN ONLY

I can't reproduce it in

Versión: 5.4.0.3
Id. de compilación: 7556cbc6811c9d992f4064ab9287069087d7f62c
Subproc. CPU: 1; SO: Windows 6.1; Repres. IU: predet.; 
Configuración regional: es-ES (es_ES); Calc: group

-> regression

@Jan-Marek: Might it be related to the scheduler changes?
Comment 3 Julien Nabet 2017-08-03 22:02:21 UTC 
Created attachment 135109 [details]
bt with debug symbols (gtk3)

On pc Debian x86-64 with master sources updated today + gtk3 + enable-dbgutil, I could reproduce this.
Comment 4 Aron Budea 2017-09-06 04:06:01 UTC 
Since the "good" version wasn't a debug build, it can't be established whether this is a regression (and can't be bibisected in Windows anyway), so removing regression-related keywords.
Comment 5 QA Administrators 2018-09-07 02:43:46 UTC Comment hidden (obsolete)
Comment 6 Julien Nabet 2019-03-17 11:25:59 UTC 
Created attachment 150020 [details]
bt with debug symbols

On pc Debian x86-64 with master sources updated today, I still reproduce the assert.
I noticed this too on console:
warn:legacy.osl:13439:13439:svx/source/svdraw/svdundo.cxx:337: OOps, something went wrong in SdrUndoAttrObj (!)
Comment 7 Julien Nabet 2019-03-17 11:33:58 UTC 
Created attachment 150021 [details]
bts from Oops line (see previous bt)

Seeing the bts, it seems there's a pb in list of actions in the array at #2  0x00007ffff4f73d30 in SfxListUndoAction::Undo() (this=0x55555d42d670) at /home/julien/lo/libreoffice/svl/source/undo/undo.cxx:1318
Comment 8 QA Administrators 2022-09-26 03:29:54 UTC Comment hidden (obsolete)
Comment 9 QA Administrators 2024-09-26 03:16:30 UTC 
Dear Telesto,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug