Created attachment 102065 [details] crash-report 4242 Problem description: Steps to reproduce: 1. insert image (png) Current behavior: crash at the moment i click "open" Expected behavior: Operating System: Mac OS X Version: 4.2.4.2 release
try installing new 4.2.5.2 and tell if issue persists
WORKSFORME in Version: 4.3.0.1 Build ID: 9ed0c4329cf13f882dab0ee8b9ecd7b05e4aafbb Is this bug still valid / reproducible with the latest LO release? 4.3RC1: http://www.libreoffice.org/download/pre-releases/ Please also try resetting your user profile and let us know if that helps: https://wiki.documentfoundation.org/UserProfile Please REOPEN should the problem then still persist for you.
(In reply to comment #1) > try installing new 4.2.5.2 and tell if issue persists seems to work with LO 4.2.5.2 thanks
Created attachment 102207 [details] impress crash-log 4162
hi there, sadly i got the same problem again, impress crashs trough different actions (e.g. adding effect, foramating image...) i tryed to reset user profile, also tryed different lo versions without success. still got sudden crash.
Hi js, did you try LO 4.3.0.2? Not sure if this is the same problem, since you say it is triggered by different action?
(In reply to comment #6) > Hi js, did you try LO 4.3.0.2? Not sure if this is the same problem, since > you say it is triggered by different action? Hi, no haven't tried LO 4.3 yet, but i think i've got a hint what causes the crashes: it only occures when dragon dictate (Version 3.0.4) is running. If i close dictate, everything is going fine. any idea what is going on? thanks a lot
--> js@skjuz.de so is there a conflict between that Dragon Dictate software and LibO, right? does it affects only Impress or even Writer and Calc?
(In reply to comment #8) > --> js@skjuz.de > so is there a conflict between that Dragon Dictate software and LibO, right? > does it affects only Impress or even Writer and Calc? hi, yes seems to be a conflict between those two programms. Writer crashes also, haven't tried Calc. Right now i can only reproduce the crash in Impress by inserting a image-file. even that is not always reproduceable. there must be some other factors, i haven't pointed out yet. i'm going to find out what else exactly causes a crash. i added the last crash-log, produced in impress, by inserting a image-file, while nuance dragon-dictate was running (in sleep mode, means i'm working with keyboard & mouse not with voice-control, dictate should not do anything in that mode). thanks a lot
Created attachment 102324 [details] impress crash-log while running dictate 4252 caused by inserting an image, while dictate was running (see post for details)
Ok I changed summary notes. I think you should also open a bug report in Nuance Dragon Dictate technical support as well, since the bug could be on their side.
(In reply to comment #11) > Ok I changed summary notes. I think you should also open a bug report in > Nuance Dragon Dictate technical support as well, since the bug could be on > their side. i've tried LO 4.3.0.2 still the same problem. I've also opened a support-ticket at nuance. i hope it can be fixed, cause i love LO, but need to work with dictate cause of a handicap. thank you
Hi, as fare as i can see it must have to do something with the OS X Accessibility-Support. If i turn it of, while Dictate is running, everything is fine. But i can't start Dictate without Accessibility-Support enabled. Maybe this is helpful.
Hi, now i've got a nother crash, that can be reproduced, this time in writer: dictate is running in sleep-mode (no matter, if Accesability-Support is activeted or not) 1) open exsisting odt-file 2) save as rtf => rtf-file is saved but LibO crashs if dictate is closed no crash occures. - OS X 10.9.3 - Nuance Dragon Dictate Deutsch Version 3.0.4 (12658) - LibreOffice Version: 4.3.0.2 => crash-log attached greetings js
Created attachment 102719 [details] writer crash-log 432
REOPENED is reserved for a bug that: 1. a developer has marked as FIXED; 2. a developer is assigned to the bug that is marked as FIXED; In this case the bug report was never independently confirmed so correct status is UNCONFIRMED. Thanks!
This sounds very much like the old accessibilty crashes we had with VoiceOver and certain accessibility tools.
Adding Jorend as he knows much more about this than I do.
(In reply to comment #18) > Adding Jorend as he knows much more about this than I do. Can't help here sadly. I don't use this tool, and I even don't know how to use it.
(In reply to comment #19) > (In reply to comment #18) > > Adding Jorend as he knows much more about this than I do. > > Can't help here sadly. I don't use this tool, and I even don't know how to > use it. Oh well, sorry about cc'ing you then :-)
--> js@skjuz.de is the issue still present with LO 4.3.2.2 which has been released recently?
I would think that it is pretty safe to say that DD invokes something in the accessibility API that LO can not handle ;-)
Each time, the log shows this : 7 com.apple.CoreFoundation 0x00007fff837758d9 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 41 8 com.apple.CoreFoundation 0x00007fff8377584e __CFRunLoopDoSource1 + 478 9 com.apple.CoreFoundation 0x00007fff83766886 __CFRunLoopRun + 1830
Well the LO run loop seems to complain that a Source1 type function is called, but LO doesn't know what to do with it ? Source1 function calls come from outside applications or user input according to the Apple dev reference, so it could be that DD is asking for something and LO has no means to respond and so dies ? As I'm not a dev, all just speculation.
Seems worthwhile confirming though, as those reports have come from four different versions of LO and are all highly similar
This is only likely to get fixed by someone who has: - a debug build ; - on OSX ; - and Dragon Dictate Not very likely at the moment
Any update with last stable LO version 5.0.3? If there's still a crash, it could be interesting to know if it's the same bt or not. (Of course, ideally, a bt with debug symbols could be even more useful)
** 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.6 or 5.2.3 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-20170103
*** Bug 107303 has been marked as a duplicate of this bug. ***
So, rather unsurprisingly, with our obsolete/incomplete assistive technology support, this bug is still happening.
Bug 107303 reports the crash against LO 5.3
I originally reported bug #107303, which this seems to be addressing. I just bought a brand new machine and tried everything again. It is still crashing, sometimes just sitting there doing nothing, but often when I try to save or print the file. I am enclosing the source .odt file and Apple crash report. MacOS 10.12.6, Libre Office 5.3.4.2. While I had Dragon on my old machine, I have not yet loaded it onto this machine, and the crash is still occurring. I do have Accessibility turned on for Quickeys, Default Folder, Dropbox, IshowU (screen recorded). Is temporarily turning off Accessibility for these apps a workaround to avoid this crash until it is fixed?
*** Bug 115095 has been marked as a duplicate of this bug. ***
** 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
Libre Office has had a longstanding bug that makes it crash whenever a Mac user has the Accessibility feature turned on of allowing other programs to "control your computer". This bug is still present in Libre Office 6.2. It is likely responsible for many other Libre Office bug reports from unsuspecting users. You can see the option under System Preferences > Security and Privacy > Privacy tab and Accessibility option on sidebar. The option is, "Allow the apps to control your computer". If you don't have that turned on for any apps, LO works fine. However, increasing numbers of programs do use that option. I have it turned on for: Default Folder X (file and folder cache) Dragon (speech reco) Dropbox (cloud file system) IShowU (screen recorder) Quickeys (macro program) LO is unreliable in the presence of this option, often crashing and rendering it unusable. Turning on and off this option for multiple programs takes a fair bit of work, so is not feasible on an everyday basis for most users. Nor is abandoning every program that needs this option. This should really be fixed. Otherwise you will see an attrition of your Mac user community as people keep on running into this bug and not understanding the cause, they will blame LO. It's a shame, but I have abandoned everyday use of LO because of this. I would like to go back.
Given that Nuance has decided to abandon support for the macOS version of Dragon Dictate, it seems unlikely that this bug will ever be adressed.
(In reply to Alex Thurgood from comment #36) > Given that Nuance has decided to abandon support for the macOS version of > Dragon Dictate, it seems unlikely that this bug will ever be adressed. See the product discontinuation notice issued by Nuance: https://www.nuance.com/dragon/support/professional-individual-for-mac-eol.html# Dragon Dictate on Mac is thus EOL. I seriously doubt that anyone will invest the resources to make an EOL product work nicely with LO when it can't even work nicely with the OS on which it is supposed to run.
Alex: IMH the problem isn't Dragon Dictate but is more general. It seems to me that accessibility part in LO is quite broken. So this one may be put to WONTFIX but hope that someone will tackle accessibility pbs instead of seeing another feature not completely implemented in next GSOC.
(In reply to Julien Nabet from comment #38) > Alex: IMH the problem isn't Dragon Dictate but is more general. It seems to > me that accessibility part in LO is quite broken. > So this one may be put to WONTFIX but hope that someone will tackle > accessibility pbs instead of seeing another feature not completely > implemented in next GSOC. Hi Julien, Yes, I agree, and I believe that we already have several bug reports relating to accessibility, including VoiceOver. See for example, our meta bug 555571
Should this bug be closed based on comment 36?
Yes, the issue is not Dragon anymore, so this specific bug need not be addressed, as per comment #39. But the larger issue of app "accessibility" in MacOS still stands, and is important to the future of Libre Office for Mac. See my comment #35 (and #38) for details. Increasingly, Mac apps do turn on this "accessibility" feature, which crashes LO. This problem is intermittent and took me a long time to track down. Mac users will encounter it inadvertently and blame LO and give up. I would love to return to everyday use of LO but I can't because of this. I do think it is urgent to fix for the Mac community.
(In reply to Henry Lieberman from comment #41) > > But the larger issue of app "accessibility" in MacOS still stands, and is > important to the future of Libre Office for Mac. See my comment #35 (and > #38) for details. Increasingly, Mac apps do turn on this "accessibility" > feature, which crashes LO. This problem is intermittent and took me a long > time to track down. Mac users will encounter it inadvertently and blame LO > and give up. I would love to return to everyday use of LO but I can't > because of this. I do think it is urgent to fix for the Mac community. Interestingly, I get a more stable experience out of dictating into Google Workspace documents via Chrome... Even Word for Mac has a dictation feature (at least in its current iteration). Setting as WONTFIX. As I have already mentioned, we have a meta bug (tdf#55571) for all of the accessibility related issues.