Bug 79264 - Editing text triggers false record modified warning
Summary: Editing text triggers false record modified warning
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
(earliest affected) release
Hardware: x86-64 (AMD64) Linux (All)
: medium minor
Assignee: Not Assigned
Depends on:
Reported: 2014-05-26 14:39 UTC by Wil Hepwortth
Modified: 2015-09-04 03:01 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Wil Hepwortth 2014-05-26 14:39:49 UTC
I have a table which contains a TEXT field.  Editing this text field causes odd behaviour when edited.  If the text is changed to a non-zero length string, attempting to close the form triggers the unsaved changes dialog.  If the text is set to a zero length string, this is not triggered.  If a non-zero length string is entered and then navigate to another record, the dialog is not issued.

I am using SQLite ( and the ODBC connector (http://www.ch-werner.de/sqliteodbc/ - 0.997).


Create table
CREATE TABLE tblProject (
	description TEXT NOT NULL,
	comments TEXT

Create two records with nothing in the comments.

Create a form bound to tblProject and a control bound to comments,

Enter a non-zero length string, save the record and close the form.  This will trigger the dialog.

Repeat the previous step, but before closing, navigate to another record.  No dialog is triggered.

Open the record with the non-zero length string.  Change the text to zero length, save the record and close the form.  No dialog is triggered.
Comment 1 Julien Nabet 2014-10-11 15:02:39 UTC
Perhaps I missed something but on pc Debian x86-64 with 4.3.2 Debian package, I don't reproduce this. (Mysql + jdbc)

Could you give a try to last stable LO version 4.3.2?
Comment 2 Alex Thurgood 2015-01-03 17:38:44 UTC
Adding self to CC if not already on
Comment 3 QA Administrators 2015-07-18 17:36:21 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.

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

Warm Regards,
QA Team

This NEEDINFO message was generated on: 2015-07-18
Comment 4 QA Administrators 2015-09-04 03:01:39 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID 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 FDO
Message generated on: 2015-09-03