I have observed that if I delete records from the Thunderbird AddressBook, these deletes seems not to be updated in Base. I am using LibreOffice 4.2.8.2 with Ubuntu 14.04, but have experienced the same with Windows 7. By looking at the content of the abook.map in ./thunderbird, deleted records are still there, but are not shown when retrieving the addresses directly from Thunderbird. If I export the AddressBook from Thunderbird to a ldif file, delete abook.map and import the ldif file, the records are correct. I guess that there is some issue in how Thunderbird stores the data in abook.map and how LibreOffice reads it.
(In reply to patufet99 from comment #0) > By looking at the content of the abook.map in ./thunderbird, deleted records > are still there, but are not shown when retrieving the addresses directly > from Thunderbird. > So Thunderbird isn't deleting the record but will only set them to something like unvisible in the GUI. Base shows the whole data, which are currently there. Why should this be a bug of LO-Base?
I cannot judge if this is a bug of LO Base or a problem of Thunderbird as I do not know the insights of how the data is stored in the abook.map file. I just filed the bug in the hope that the info could be useful to somebody!
I have found some additional information here: http://mozilla.6506.n7.nabble.com/thunderbird-address-book-mork-deleted-rows-and-distribution-list-question-td182838.html But it is not clear for me if the problem lies in the way that the mork database handles deleted records or in the LO Base parser.
@David : any idea whether this is a mork driver integration problem, or more to do with the way TB handles deleted records ?
(In reply to Alex Thurgood from comment #4) > @David : any idea whether this is a mork driver integration problem, or more > to do with the way TB handles deleted records ? This is indeed a good question, TBH I don't know (yet). One information wasn't mentioned in this report: What operation system is used? In case of Windows, our mork dirver wasn't used at all. But ancient seamonkey mozilla driver was used. Note, that this driver was removed on master. Since 5.1 our native mork driver will be used on both 32 and 64 bit Windows platform.
In windows I used Win7 64 bit, Thunderbird 38.4.0. And LibreOffice 5.0.4.2.
(In reply to patufet99 from comment #6) > In windows I used Win7 64 bit, Thunderbird 38.4.0. And LibreOffice 5.0.4.2. What bitness version of LibreOffice are you using? * 32 bit: ancient seamonkey mozilla driver is used (was removed on master) * 64 bit: mork driver is used But anyway, someone could test it on Linux and report here there result. On Linux we always use mork driver in latest LO releases.
LO 5.0.4.2, 64 bit. As mentioned on my original post with Ubuntu 14.04 the behaviour is the same. Ubuntu is 64 bit as well.
Confirming on Version: 5.2.0.0.alpha0+ Build ID: 21f152a52397bf99364e5dc5ba9519e11452f260 CPU Threads: 2; OS Version: -; UI Render: default; Locale : fr-FR (fr.UTF-8) OSX 10.11.2 I created a new entry in a TB addressbook (personal addresses) that had no other entries. I then created a new ODB file that connected to the TB address book. When I opened the ODB file, I can see the single entry in the personal address table. I then closed LibreOffice and went back to Thunderbird. Opened the address book manager and deleted the single address in it. Next, I reopened the ODB file and double clicked on the table "personal'. It opened to show the deleted entry, i.e. it hadn't been changed / removed accordingly.
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.2.5 or 5.3.0 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170306
Bug still present in LO 6.0.2.1
** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Not quite sure how to fill one of these comments out (e.g. what status it should have - so left as NEW), but I can confirm that deleted records from the Thunderbird AddressBook still show up in the Base database created when generating labels from a mailing list. I am using Version: 6.2.8.2 (x64) Build ID: f82ddfca21ebc1e222a662a32b25c0c9d20169ee CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; Locale: en-GB (en_GB); UI-Language: en-GB Calc: threaded
Dear patufet99, 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
Shouldn't we close this bug? Thunderbird addressbook isn't connectable any more. You have to use a connection through SQlite instead. See Bug 138715
(In reply to Robert Großkopf from comment #15) > Shouldn't we close this bug? Thunderbird addressbook isn't connectable any > more. You have to use a connection through SQlite instead. See Bug 138715 Probably, but does the problem also exist when using sqlite over ODBC? If it does, then this bug report should probably remain open.