This bug was filed from the crash reporting server and is br-9cbafd09-d3b3-413c-91e7-18baf28d031d. ========================================= This crash occurred instantly after I clicked on the button to disable the Mendeley Desktop's LibreOffice extension in extension manager. I'm not sure it is related to this specific extension or if it is a problem because I had Mendeley Desktop's extension active and also Zotero's one which serves the same purpose. Both are software solutions to manage your literature and bibliography in a professional way.
I talk about this two bars on the bottom of the Writer: see 'two_bars_screenshot.jpg'. Sometimes the bars move, depending on if you are inside an enumeration. So if you click on the next search result button, you could get into an enumeration. If you click again on the same position of your mouse - simply because you wanna go to the next result again - you click on the formatting option below just. This is hard to fix and I'm not sure how it is done better. If you still don't know what I mean, I have to try to describe it completely different. It's hard to explain to be honest.
Please ignore comment #2 because I posted that comment to the wrong issue. Sorry for that!
is it possible to use the Mendeley plugin for free? if so, from where can I download it ?
You can download the software for free at the main page of this site and this link will show you where the install button for the extension is: https://www.mendeley.com/guides/using-citation-editor/01-installing-citation-plugin
Created attachment 141270 [details] Mendeley extension I downloaded from here and extracted: https://www.mendeley.com/download-desktop/ In the Linux version it was in share/mendeleydesktop/openOfficePlugin I could not repro the crash on Linux. Will try on Windows next. Arch Linux 64-bit Version: 6.1.0.0.alpha0+ Build ID: d4c0e7ef2b7f7e3cb36996bad72ac255b630beb4 CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on April 8th 2018 Arch Linux 64-bit Version: 6.0.2.1.0+ Build ID: 6.0.2-1 CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group
No problem on Windows either. Note that I did not have the Mendeley desktop installed - only the extension. I hope this is enough. After all, they say "To use Mendeley you’ll need to register" Version: 6.0.3.2 (x64) Build ID: 8f48d515416608e3a835360314dac7e47fd0b821 CPU threads: 4; OS: Windows 10.0; UI render: default; Locale: fi-FI (fi_FI); Calc: group
Try to install Zotero (https://www.zotero.org/) additionally next to Mendeley. Maybe the conflict happens if both is active and you disable Mendeley.
Created attachment 141282 [details] Zotero extension No problem on Win even with Zotero alongside.
It may have nothing to do with the bug opener's report but I had a crash in 5.4 with the same crash summary today: br-60f430c8-da3e-4863-8b3d-23f058bcfd38 Reason was the revert/undo of a bunch of copying and formatting actions from an ODF file which formatting was destroyed by MSO Word.
https://crashreport.libreoffice.org/stats/signature/BigPtrArray::Index2Block%28unsigned%20__int64%29 shows 2349 reports, Windows x64. Not likely to be caused by not so frequent Mendeley. Mendeley has some long-standing bugs, we need volunteers to triage them.
(In reply to Thomas Lendo from comment #9) > It may have nothing to do with the bug opener's report but I had a crash in > 5.4 with the same crash summary today: > br-60f430c8-da3e-4863-8b3d-23f058bcfd38 > > Reason was the revert/undo of a bunch of copying and formatting actions from > an ODF file which formatting was destroyed by MSO Word. Hi Thomas Lendo, it would be really nice if you could try to reproduce it again... having steps to reproduce it is key in order to fix this crash...
(In reply to Xisco Faulí from comment #11) Xisco, my crashes are caused by bug 117215 or/and bug 117444. I've no Mendeley extension installed.
There is no crash with this signature in LO 6.2. (see https://crashreport.libreoffice.org/stats/signature/_GSHandlerCheck_SEH). Clemens, can you still 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. Change to RESOLVED WORKSFORME, if the problem went away.
Sorry, previous comment should belong to bug 116689.
Triaging bug 126583 I saw, that there is no crash report in LO 6.2.5 with the signature ["BigPtrArray::Index2Block(unsigned __int64)"]. So is this bug fixed or still reproducible in latest version?
Dear Clemens Prill, 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 Clemens Prill, 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