Description: I can create a macro and a push button OK, but when I try to "assign" the button to a macro by right clicking on the button in design mode. Then go to control> events>mouse button pressed then when I select macro the ods file i"m working on crashes or shuts down. when I try to reopen it it asks me to restore the file. Cannot get the button to assign to a macro. I just installed Libre Office 6.1 from 6.0 and that did not fix the malfunction. I can run the macro manually tho, so the actual macro works. Thanks. Steps to Reproduce: 1. I try to "assign" the button to a macro by right clicking on the button in design mode. 2. Then go to control> events>"mouse button pressed" then when I select "macro" the ods file i"m working on crashes shuts down Libre Office calc.. Actual Results: Libre Office calc shuts down. When I reload it a dialog box appears telling me it will recover to the last used ods file. Expected Results: Should have assigned a macro to a push button. Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: OpenGL Results: Don't really know what this all means, here are the results of glxinfo | grep OpenGL OpenGL vendor string: X.Org R300 Project OpenGL renderer string: ATI RS480 OpenGL version string: 2.1 Mesa 18.0.5 OpenGL shading language version string: 1.20 OpenGL extensions: OpenGL ES profile version string: OpenGL ES 2.0 Mesa 18.0.5 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16 OpenGL ES profile extensions: I am running a Gateway laptop model MX6437 32bit 1.5G memory. I know it's old but runs mint well. Maybe processor isn't powerful enough to run certain things. Getting a newer 64bit machine soon. Just curious to see if I can make a macro button or not on thia machine.
Created attachment 148603 [details] Dialog box on recovering file
Hello, Thank you for filing the bug. Please send us a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO', so please do change it back to 'UNCONFIRMED' once you have attached a document. (Please note that the attachment will be public, remove any sensitive information before attaching it.) How can I eliminate confidential data from a sample document? https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F Thank you works for me in Version: 6.3.0.0.alpha0+ Build ID: 3fa4674615b747e219afe5bf0a9b689df3840439 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: x11;
Created attachment 148609 [details] LO file in question about failing macro button assignment. Here is the small experimental file I've been working on for y'all to try. If it works for you then maybe my machine can't Handel making macro buttons.
There should be 2 macros in macrosLO.ods. One for deleting the other for typing. I can run either macro manually OK, but just can't assign a button to either one.
No matter which menu I use, if it has a macro button to press to take me to the available macros to assign to a button It makes the ods file crashes. I can never get to a list if macros to assign to anything, buttons key strokes ETC. Also if I go to tools>macros>Run Macro, pressing that will crash the ods file to crash.
I can't reproduce it in Version: 6.1.4.2 Build ID: 1:6.1.4-0ubuntu0.16.04.1~lo2 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: group threaded I can assign both macros to the button click action. Does it work if you disable OpenGl ? -> https://wiki.documentfoundation.org/OpenGL I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the issue is still present
Unchecked openGL but issue is still present. Actually unchecked everything in the openGL menu but problems remain. Should I try and select openGL and see what happens?
(In reply to Rickie from comment #7) > Unchecked openGL but issue is still present. Actually unchecked everything > in the openGL menu but problems remain. Should I try and select openGL and > see what happens? Could you please try in safe mode ? Go to menu Help - Restart in Safe Mode ?
Restarted in safe mode and it did the same thing. Made no difference at all. When selecting the Macro assign button, LO calc file crashes/closes.
Created attachment 148661 [details] OpenGL information via terminal "glxinfo | grep OpenGL"
Created attachment 148662 [details] File in question
If you test using an appimage of 6.3 or even 6.4, does it also crash: https://libreoffice.soluzioniopen.com/ ?
(In reply to Buovjaga from comment #12) > If you test using an appimage of 6.3 or even 6.4, does it also crash: > https://libreoffice.soluzioniopen.com/ ? Setting to NEEDINFO
Dear Rickie, 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 Rickie, 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