Bug 66193 - IDE: Code disappears
Summary: IDE: Code disappears
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: BASIC (show other bugs)
(earliest affected) release
Hardware: Other macOS (All)
: medium critical
Assignee: Not Assigned
Whiteboard: BSA
: 65669 (view as bug list)
Depends on:
Reported: 2013-06-26 07:42 UTC by Dieter Burkhardt
Modified: 2014-07-08 17:17 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Base with Macros (177.14 KB, application/vnd.oasis.opendocument.database)
2013-06-26 07:42 UTC, Dieter Burkhardt
Base file with correct running macros (279.53 KB, application/vnd.oasis.opendocument.database)
2013-06-26 08:17 UTC, Dieter Burkhardt

Note You need to log in before you can comment on or make changes to this bug.
Description Dieter Burkhardt 2013-06-26 07:42:11 UTC
Created attachment 81448 [details]
Base with Macros

Problem description: After Editing Code it can happen , that the code from the modules disappears. I had no crash it happens also when I close the document in a normal way.
In the attached Basedocument the Library Ausmass the Modules are empty

Steps to reproduce:
1. ....
2. ....
3. ....

Current behavior:

Expected behavior:

Operating System: Mac OS X
Version: release
Comment 1 Dieter Burkhardt 2013-06-26 08:17:01 UTC
Created attachment 81450 [details]
Base file with correct running macros

I have changed the dialog ausmass/Ausmass_Dlg and afterwards the code in BaukostenplanDB/Dlg has disappeared
Comment 2 Dieter Burkhardt 2013-06-26 08:18:16 UTC
I have to go back to the older release
Comment 3 Julien Nabet 2013-07-02 21:33:18 UTC
*** Bug 65669 has been marked as a duplicate of this bug. ***
Comment 4 Julien Nabet 2013-07-02 21:34:55 UTC
Could you try to rename your LO directory profile (see https://wiki.documentfoundation.org/UserProfile) and give it a try?
Perhaps it could be caused by buggy remnants things.
Comment 5 Dieter Burkhardt 2013-07-06 15:17:09 UTC
I have made an reload of the release
I renamed my LO directory (i coudent find any 'my macros')

After changing and saveing a dialog mask the code of the local document macros
is parial disapeared. in some libraries the modules are available but the modules are empties

Where are the macros of a local document?
Comment 6 Julien Nabet 2013-07-21 07:01:21 UTC
Dieter: sorry for the delay, I was on vacation without any computer.
Thank you for your feedback. To answer you, if you change the extension of the file and replace it by zip, you may unzip the file and take a look to its content.
I'm not an expert but I think Macros are in Basic subdirectory (+ Dialogs?)

I unzipped both zip renamed files and compared the directories, here's the result:
< ./Basic/Allgemein/Common_Dlg.xml
< ./Basic/Allgemein/Common_PDF.xml
< ./Basic/Allgemein/Dialog_BKP.xml
< ./Basic/Allgemein/Forms.xml
< ./Basic/Allgemein/Search.xml
< ./Basic/Allgemein/SqlByName.xml
< ./Basic/Allgemein/Utilities.xml
< ./Basic/AuftragnehmerDB/Sql.xml
< ./Basic/Auftragnehmer/Module1.xml
< ./Basic/BaukostenplanDB/BKP.xml
< ./Basic/BaukostenplanDB/Dlg.xml
< ./Basic/BaukostenplanDB/Search.xml
< ./Basic/BaukostenplanDB/Sql_old.xml
< ./Basic/Baukostenplan/Dialog_Edit_BKP.xml
< ./Basic/Baukostenplan/Edit_BKP.xml
> ./Basic/Dialog/script-lb.xml
< ./Basic/FinanzRepDB/Ausmass.xml
< ./Basic/FinanzRepDB/BKP.xml
< ./Basic/FinanzRepDB/Common.xml
< ./Basic/FinanzRepDB/Kopf.xml
< ./Basic/FinanzRepDB/Vertrag.xml
< ./Basic/FinanzRepDB/Zahlungen.xml
< ./Basic/FinanzReport/FinanzReportPDF.xml
< ./Basic/FinanzReport/Module1.xml
< ./Basic/Vertrag/Dialog.xml
< ./Basic/Vertrag/Erfassen.xml
< ./Basic/Vertrag/Forms.xml
< ./Basic/WildWest/Ausmass_alt.xml
< ./Basic/WildWest/BKP_Input.xml
< ./Basic/WildWest/FinReport_Erfassen_alt.xml
< ./Basic/WildWest/LoadDB_New.xml
< ./Basic/WildWest/LoadDB.xml
< ./Basic/WildWest/TableCopy.xml
< ./Basic/WildWest/Test.xml
< ./Basic/Zahlungen/Dialog.xml
< ./Basic/Zahlungen/Erfassen.xml
< ./Basic/Zahlungen/Forms.xml
< ./Basic/Zahlungslauf/Dialog.xml
< ./Basic/Zahlungslauf/Erfassen.xml
< ./Basic/Zahlungslauf/ZahlungsLaufPDF.xml
< ./Basic/ZZOldFinanzRep/Dialog_Edit_FinRep.xml
< ./Basic/ZZOldFinanzRep/FinanzReportPDF.xml
< ./Basic/ZZOldFinanzRep/FinReport_Erfassen.xml
< ./Basic/ZZOldFinanzRep/Module1.xml
< ./Basic/ZZOldFinanzRep/Rep_Object.xml
< ./Basic/ZZOldFinanzRep/SchaetzungPDF.xml
< ./Dialogs/BaukostenplanDB/Search_Dlg.xml
< ./Dialogs/Baukostenplan/Edit_BKP_Scr.xml
< ./Dialogs/Dialog/Test.xml
> ./Dialogs/FinanzReport/dialog-lb.xml
< ./Dialogs/Vertrag/Vertrag_Dlg.xml
< ./Dialogs/Zahlungen/Zahlungs_Dlg.xml
< ./Dialogs/Zahlungslauf/getZahlung_Dlg.xml
< ./Dialogs/Zahlungslauf/Zahlungslauf_Dlg.xml
< ./Dialogs/ZZOldFinanzRep/Edit_FinRep_Scr.xml
Comment 7 retired 2013-11-22 17:59:19 UTC
Dieter, could you check and see if LO improves anything?

Setting to NEEDINFO until more detail is provided.

After providing the requested info, please reset this bug to UNCONFIRMED. Thanks :)
Comment 8 retired 2013-11-22 18:00:17 UTC
Also were you abel to test what Julien suggested in comment #6.
Comment 9 QA Administrators 2014-06-01 21:29:47 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
Comment 10 QA Administrators 2014-07-08 17:17:36 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