Created attachment 169603 [details] salary problems when editing reports when using want to work with create report in libreoffice base, it crashes and I completely exit the program
Created attachment 169666 [details] information
@jorojmaqui : I am testing on : Version: 7.0.4.4 Build ID: 841d27ff4cd6850c43bdd7333f8373cae686520d CPU threads: 8; OS: Mac OS X 11.2; UI render: default; VCL: osx Locale: fr-FR (fr_FR.UTF-8); Langue IHM : fr-FR Calc: threaded I notice that the test file contains macros. If I activate the macros on loading the ODB, I get an error message : Error #1 (An exception occurred : ) at line 1302 in OpenConnection Is it possible to test the problem of editing a report without having activated the macro environment ? Please provide detailed steps for testing, for example, which report are we supposed to be opening / editing ?
Trying to test with LO Vanilla from Collabora as provided via the Apple AppStore leads to the following error message : firebird_sdbc error: *lock manager error *failed to create database /Users/alex/Library/Containers/com.collabora.libreoffice-free/Data/Library/Application Support/LibreOfficeVanilla/4/user/temp/lu17362qz8l.tmp/lu17362qz8u.tmp/firebird.fdb *Exiting before completion due to errors caused by 'isc_service_query'
Tested with: Version: 7.1.0.1 Build ID: b585d7d90ab863bf29b2d110c174c0c2a98f3ee4 CPU threads: 8; OS: Mac OS X 10.16; UI render: default; VCL: osx Locale: fr-FR (fr_FR.UTF-8); UI: en-US Calc: threaded 1) Open ODB file. 2) Open Report named R3xSALARIOSxIRPF 3) No crash.
so: windows 10.0 build 19041 libreoffice community 7.1.1 (x86) cpu:4 vcl:win IU:skia/rej interface: ES If you spend a while copying fields, attaching fields and deleting, the program breaks disabling experimental functions also exits
[Automated Action] NeedInfo-To-Unconfirmed
By placing a field in the report that breaks libreoffice
Sounds similar to bug 134195
FWIW, that bug report is also specific to behaviour reported on WinOS
Suspect that this is a duplicate of bug 139340, in which case we can confirm that bug report, and it would be Windows specific.
(In reply to Alex Thurgood from comment #10) > Suspect that this is a duplicate of bug 139340, in which case we can confirm > that bug report, and it would be Windows specific. Sorry, ignore this, commented on wrong bug.
The program breaks again with Libreoffice 7.1.2.1 on Windows 10 Crash report again
The program breaks again with Libreoffice 7.1.2.2 on Windows 10 Crash report again
Libreoffice 7.1.3.2 Crash report
https://crashreport.libreoffice.org/stats/crash_details/fdcdbbcf-69a7-4907-bc9a-a402c167288e
@joro : according to the crash report, you have set a listener somewhere in your report, and switching from that listener to another (or releasing it), is causing a crash in the rptuilo library. Is there any basic code execution associated with your report creation ? Looking at the crash report detail : comphelper::OInterfaceContainerHelper2::forEach<com::sun::star::view::XSelectionChangeListener,<lambda_d58ac2fab180795b2081e04b15f6c6f1> So, which selection change (XSelectionChangeListener, presumably made with the mouse) is causing this to happen ? Seems linked to the header identified in : \comphelper\interfacecontainer2.hxx at line 266 Not much else I can say, I'm afraid.
thank you
Mi pregunta es: en sistema linux este error no existe? Si es así podría seguir con mi programa en linux hasta que este error esté resulto en Windows My question is: in linux system this error does not exist? If so, I could continue with my program in linux until this error is resolved in Windows
(In reply to jorojmaqui from comment #18) > > My question is: in linux system this error does not exist? > If so, I could continue with my program in linux until this error is > resolved in Windows Sometimes Report Builder crashes under Linux, but without possibility to get a real reason for it. So I prefer the following method: After some Minutes of working with ReportBuilder I will save the report and save the *.odb-file. So the changed content won't be lost. Creating a report is unstable, but executing a report, which has already been created, will work well.
I have installed libreoffice 7.1.4.2 on Ubuntu and it gives me the same problem with the reports of this database, except that the error that occurs can be sent. crash
LibreOffice and MS Office do not use the same format for their files by default. As we have seen, LibreOffice uses ODF. For their part, older versions of MS Office use a closed format (DOC, XLS, etc.) that only Microsoft knows in depth. Unlike the previous format, this can be considered an open format (like ODF) and has become an ISO/IEC 29500 international standard. While the latest versions of LibreOffice and MS Office offer compatibility for all of these formats - and many more - the truth is that they are not perfect, which often means that the files in the program are not perfect. one program doesn't look the same in another. Of course, this is more serious in the case of LibreOffice, as it is less used than MS Office. https://slitherio.online
Hello When will this problem be fixed?
Created attachment 178576 [details] report_sql_breaks
(In reply to jorojmaqui from comment #23) > Created attachment 178576 [details] > report_sql_breaks This last report is different to what you reported in comment 5 (copying/adding/removing fields). This last report relates to a crash caused by entering and exiting the SQL list dialog after having edited the query. As we do not know what the complete query is (we can't see it in the report), we can't tell whether the new issue is due to the query itself, or some other problem with the use of the SQL list functionality. Please open a separate bug report for this. The current issue that you initially reported can not be fixed because no one has managed to reproduce it, mainly because you didn't provide any instructions on what exactly to do in order to see the behaviour you were reporting. General instability of the report builder is known, as Robert has pointed out in comment 19. The problem is to identify which particular behaviour causes any given crash.
Thank you for reporting the bug. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Dear jorojmaqui, 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 INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO 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 MassPing-NeedInfo-Ping
Dear jorojmaqui, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA 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 our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp