Created attachment 179491 [details] Video capture of reproducing the bug This bug was filed from the crash reporting server and is br-4b15dcc1-d912-4c48-a60f-d709de170efe. ========================================= Attempting to drag a comment that is on a frozen row sometimes causes a crash. I see no pattern for when it crashes vs when nothing happens. Repeatedly trying to drag the comment usually causes a crash within 5 attempts. see attached video. the right-click menu doesn't show in the recording, when you see the cursor go down, I have right-clicked and selected 'edit comment'. When the video goes black, LibreOffice calc has crashed. also attached an ods spreadsheet with a frozen row and a comment on the top row. # steps to reproduce. 1. open comment-on-frozen-row.ods in calc 2. right click on cell R1C2 3. click 'edit comment' 4. position your mouse cursor over the left edge of the comment 5. if the cursor changes symbol to a cross of arrows, start dragging, move a bit to the left and let go of drag. then return to step 4. 6. if the cursor doesn't show the cross of arrows symbol left-click on the text in the comment then return to step 4. If the comment ever becomes unfocused and hides. return to step 2. It usually seems to crash within 5 attempts to drag the comment. # version information Version: 7.2.6.2 (x64) / LibreOffice Community Build ID: b0ec3a565991f7569a5a7f5d24fed7f52653d754 CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-GB (en_GB); UI: en-GB Calc: threaded
Created attachment 179492 [details] spreadsheet to use for testing
Please test with a clean profile, Menu/Help/Restart in Safe Mode
Created attachment 179505 [details] bug performed in safe mode I did "menu/help/restart in safe mode" and recorded the bug again. uploaded crash report: - id: br-947cbec8-63b1-4d9e-a0fb-4172e160d584 - signature: vcl::unohelper::DragAndDropWrapper::dragGestureRecognized(com::sun::star::datatransfer::dnd::DragGestureEvent const &)
I can't reproduce it in Version: 7.4.0.0.alpha0+ / LibreOffice Community Build ID: ab8d141967111ca81f4607db3618bb09214e42db CPU threads: 8; OS: Linux 5.10; UI render: default; VCL: x11 Locale: es-ES (es_ES.UTF-8); UI: en-US Calc: threaded
Please update your LibreOffice to 7.3.6 or 7.4.2 and try retest your problem by your steps
Dear jncressey, 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 jncressey, 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