Bug 143603 - Opening a simple presentation has UNDO active
Summary: Opening a simple presentation has UNDO active
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
4.4.0.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, regression
Depends on:
Blocks: Undo-Redo ODF-Flat
  Show dependency treegraph
 
Reported: 2021-07-29 12:36 UTC by Mike Kaganski
Modified: 2023-09-13 03:17 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
A very simple FODP (771 bytes, application/vnd.oasis.opendocument.presentation)
2021-07-29 12:36 UTC, Mike Kaganski
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Kaganski 2021-07-29 12:36:40 UTC
Created attachment 173947 [details]
A very simple FODP

Opening the attached presentation makes Impress activate UNDO button with two elements: "Delete Text Frame" and "Delete Title text".
Comment 1 BogdanB 2021-07-29 13:01:46 UTC
Confirm with
Version: 7.1.5.2 (x64) / LibreOffice Community
Build ID: 85f04e9f809797b8199d13c421bd8a2b025d52b5
CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win
Locale: ro-RO (ro_RO); UI: en-US
Calc: threaded

Also in
Version: 7.2.0.1.0+ (x64) / LibreOffice Community
Build ID: 2a265bdda19d86437c6eb4d8deb0057d5b45e97f
CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win
Locale: ro-RO (ro_RO); UI: en-US
Calc: threaded
Comment 2 Aron Budea 2021-07-31 00:33:40 UTC
This is a regression from the following commit, bibisected using repo bibisect-44max.

https://cgit.freedesktop.org/libreoffice/core/commit/?id=32c28a6d131284c1602f57a8220d1b736b538288
author		Maxime de Roucy <mderoucy@linagora.com>	2014-01-07 09:31:11 +0100
committer	Caolán McNamara <caolanm@redhat.com>	2014-06-25 10:00:50 +0000

Resolves: #i74651# remove image via should change document state
Comment 3 QA Administrators 2023-09-13 03:17:21 UTC
Dear Mike Kaganski,

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