Created attachment 87883 [details] Today Problem description: Crash when diagramm Steps to reproduce: 1. Make new table 2. Calculate sum(or average) 3. Attempt to build Diagramm sums or averages. 4. Crash. Current behavior: Crash Expected behavior: Not crash Operating System: Windows 7 Version: 4.1.2.3 release
Thank you for your bug report, I CAN'T reproduce this bug running Version: 4.1.3.1 Build ID: b42498da0e3f91b17e51b55c8295ec4f8f22087 and Version: 4.1.2.3 Build ID: 40b2d7fde7e8d2d7bc5a449dc65df4d08a7dd38 on Mac osx 10.8.5. Maybe this is a Windows only bug, or maybe I did something wrong in the file. Would there a possibility that you could attach a test file so we can test it again. Thank you in advance kind regards, Thomas
Same platform (LibO 4.1.2.3 on Win7), unable to reproduce the bug
I have windows, 64-bit, i tried make graph 5 times, but each try ended by crash (
Дмитрий could you please attach the file that crashed so we can test that file out. Thank you in advance. kind regards, Thomas
I dont know, what i must send?
I have windows7, 64-bit, LO 4.1.2.3 and the system crash if I select some cells in order to insert chart. Without selecting cell the chart has been inserted.
(In reply to comment #5) > I dont know, what i must send? attach your file please.
(In reply to comment #7) > (In reply to comment #5) > > I dont know, what i must send? > > attach your file please. Which file??
(In reply to comment #8) > (In reply to comment #7) > > (In reply to comment #5) > > > I dont know, what i must send? > > > > attach your file please. > > Which file?? your file which you created and tested.
(In reply to comment #8) > (In reply to comment #7) > > (In reply to comment #5) > > > I dont know, what i must send? > > > > attach your file please. > > Which file?? file that you created and tested.
file here: https://mega.co.nz/#!0YdSVBQI!Kl_SnWb5azmU0M7JxqC1HWqUdmsipHMhoHPi1PaiJ68
Could you please just attach the sample document to this bugzilla entry, rather than going through some cloud solution which wants to install 50 megs of dubious code in order to download a 300k example.
(In reply to comment #12) > Could you please just attach the sample document to this bugzilla entry, > rather than going through some cloud solution which wants to install 50 megs > of dubious code in order to download a 300k example. I can't. Dont added and i used cloud disk. There info for you.
Created attachment 88072 [details] Crash log Mac osx 10.9
I have downloaded the file from Mega and I can reproduce this bug running Version: 4.1.3.1 Build ID: b42498da0e3f91b17e51b55c8295ec4f8f22087 OS: Mac osx 10.9.
Thomas: would it be possible you attach the file to the bugtracker?
Дмитрий do you have no problems if I attach the file that I downloaded on Mega and upload it to this bug?
(In reply to comment #17) > Дмитрий do you have no problems if I attach the file that I downloaded on > Mega and upload it to this bug? its ok. i cant do it, unknown for me error appear
Created attachment 88167 [details] Test file
Sorry for not having responded before, I expected a Calc file but if it's an odt, I must say I don't know how to reproduce this since I know very few about tables + calculus on Writer. (even with the steps given in the description).
Can not reproduce this. Setting to NEEDINFO until we have exact reproduce steps. Might this be resolved already in 4.2.3.3?
"Can not reproduce this. Setting to NEEDINFO until we have exact reproduce steps. Might this be resolved already in 4.2.3.3?" WHAT INFO??? Im send you screenshot and file, there no more things to add. And no, in new version Libre Office this error still appear, im check it. And i changed from NeedInfo, because there all files for reproduction.
Steps to reproduce: 1. Go to the last page. 2. Select the most right column of the table (the one with the purple color). 3. Try to add a chart using the menu Insert->Object->Chart... Actual results: An empty message box with 'Fatal Error' in its title, followed by a closing of the entire app (it doesn't crash for me). Tested with master (fb0ca7eff0e16fa8dd1a4c8d75fef23830903a3f) under Fedora 20 (64-bit).
I think this has something to do with merged cells. 1. New Text Document. 2. Insert Table 2 columns x 3 rows. 3. Merge cells A1 and B1 in first row. 4. Select cells B2 and B3. 5. Insert → Object → Chart. Expected Result: Chart Wizard. Results: Empty dialogue with “LibreOffice 4.4 Fatal er” title and crash. Windows Vista 64 Version: 4.4.3.2 Build ID: 88805f81e9fe61362df02b9941de8e38a9b5fd16
Created attachment 115756 [details] console logs On pc Debian x86-64 with master sources updated today and enable-dbgutil, I could reproduce this after having followed Gordo's step by step process. I attached console logs I got.
** 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 127467 [details] backtrace master 5.3 from Windbg.txt
** 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.4.1 or 5.3.6 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-20170929
Confirmed fatal error crash on Windows 10 using Gordo's procedure. Version: 6.0.2.1 (x64) Build ID: f7f06a8f319e4b62f9bc5095aa112a65d2f3ac89 CPU threads: 4; OS: Windows 6.1; UI render: default; Locale: en-US (en_US); Calc:
Dear Дмитрий, 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://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
No more crash. Please retest. Version: 7.2.0.4 / LibreOffice Community Build ID: 9a9c6381e3f7a62afc1329bd359cc48accb6435b CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded
I reproduced crash in 7.3+. One needs to get crash with old version to confirm the steps and than to try master.
Dear Дмитрий, 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
I'm not able to repro with steps from comment 0, comment 23, or comment 24, using the following: Version: 24.2.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: ab37ac87d860fd5cd3b32b35df90dfbcba6dafb6 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded(In reply to QA Administrators from comment #33) Please provide updated test files/repro steps.
Dear Дмитрий, 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 Дмитрий, 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