Created attachment 116184 [details] crash when copying contents from one form to another form This crash is occured two times one after another. I have tried to copy the contents of one form which are combined with one table to another form and to assign the new contents to the another table. Following steps: 1) Open a database (HSQLDB) with at least two tables and two forms, the contents of one form are combined with a table. 2) Open both two forms. 3) Select the contents of one form with the mouse and copy them to the second form via drag and drop. Perhaps the new contents must be edited --> the crash occured.
Hello Christian, Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Created attachment 116201 [details] backtrace for this kind of crash Hello, I have made a backtrace for this kind of crash. For reproducing this, it could be necessary to edit something in the form navigator of the new created form.
Created attachment 116202 [details] example Hello, I have uploaded the example database of bug 91357. I hope, it can be reproduced with it. My original database, which causes the crash, has about 100 tables and is too large for uploading and contains all my work ;)
Can not reproduce with LO 4.3.3, win7
Created attachment 116205 [details] new example I could reproduce it with this example database and LO 4432. Following steps: 1) Open both forms (Demo 1 and Demo 2) in edit mode, not normally. 2) Select the contents of form 'Demo 1' and copy them to clipboard (Ctrl-C) 3) Paste the contents in form 'Demo 2' (Ctrl-V) 4) Open form navigator of form 'Demo 2' 4.1) Select all items unter 'demo 1' and move them to 'demo 2' (Delete 'demo 1') 6) Close form 'Demo 1' 7) Do something with the main window or form 'Demo 2' (resize it, press a button in main window or whatever) I have got the crash.
(In reply to christian_kuhn from comment #5) > Created attachment 116205 [details] > new example > > I could reproduce it with this example database and LO 4432. Following steps: > I can confirm crash with LO 4.4.3, win7
** 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.1.5 or 5.2.1 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-20160920
Created attachment 128703 [details] message, when LO crashed I can reproduce this crash with the uploaded example. I use LibreOffice Version: 5.2.1.2 Build-ID: 31dd62db80d4e60af04904455ec9c9219178d620 and Windows 10. But now the behaviour of the crash has changed: if I try to close the form demo1 after I have copied the contents of it to the form demo2, I get a message box with the content 'SEH exception: ACCESS VIOLATION'. Then Base hangs and I must close it with the task manager. Best regards, Christian
(In reply to christian_kuhn from comment #5) > Created attachment 116205 [details] > new example > > I could reproduce it with this example database and LO 4432. Following steps: > > 1) Open both forms (Demo 1 and Demo 2) in edit mode, not normally. > 2) Select the contents of form 'Demo 1' and copy them to clipboard (Ctrl-C) > 3) Paste the contents in form 'Demo 2' (Ctrl-V) > 4) Open form navigator of form 'Demo 2' > 4.1) Select all items unter 'demo 1' and move them to 'demo 2' (Delete 'demo > 1') > 6) Close form 'Demo 1' > 7) Do something with the main window or form 'Demo 2' (resize it, press a > button in main window or whatever) > > I have got the crash. Would it be possible to have a more simple use case? Indeed, in step 2 Select the contents of form "Demo 1" : There's no "select all" option, if I try to select all the elements with mouse, it doesn't work, it only selects Demo 1 text. Is it mandatory to select every element of Demo 1? in step 4.1) in navigator, how to access elements from demo 1 ?
Created attachment 139438 [details] bt with debug symbols On pc Debian x6-64 with master sources updated some days ago, I could reproduce this.
Christian: re reading https://bugs.documentfoundation.org/show_bug.cgi?id=91761#c5, I could reproduce this, sorry for the previous post.
** 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
On pc Debian x86-64 with master sources updated today and trying to follow https://bugs.documentfoundation.org/show_bug.cgi?id=91761#c5, I don't reproduce this anymore. Idem with LO Debian package 6.1.5.2 Christian: could you give a try to last LO version 6.2.4?
Hello, I downloaded the example from this page and tried it with: Version: 6.2.4.2 (x64) Build-ID: 2412653d852ce75f65fbfa83fb7e7b669a126d64 I could not reproduce the crash. I have resized the window and moved and manipulated the copied content. Best regards, Christian
Thank you for your feedback, let’s put this one to WorksForMe