Hello, Since the last LibreOffice update in openSuse Tumbleweed, I get version 5.0.1.2. I have a x86_64 machine. Writer crashes each time I press the space bar. So, completely unusable. Here is the console output. BR user@computer:~/Bureau> libreoffice ** (soffice:15756): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (soffice:15756): GLib-GObject-WARNING **: gsignal.c:3406: signal name 'selection_changed' is invalid for instance '0x22efa00' of type 'OOoAtkObjCompTxt' ** (soffice:15756): WARNING **: missing get indicator state ** (soffice:15756): WARNING **: Unknown event notification 36 user@computer:~/Bureau>
A precision : Calc crashes once I press a key to enter data on existing files. Not on a new file ! With a new file, I still get warnings in the console. Once this new file is saved, and reopened, no problem. If I open an existing file, creating the problem, and save it as another one, the problem persists. Difficult to find a way to get back use of my data. Is anything changed in the file format ? BR ** (soffice:16426): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (soffice:16426): GLib-GObject-WARNING **: gsignal.c:3406: signal name 'selection_changed' is invalid for instance '0x204d1a0' of type 'OOoAtkObjCompTxt' ** (soffice:16426): WARNING **: Invalidate all children called ** (soffice:16426): WARNING **: Unknown event notification 36 ** (soffice:16426): WARNING **: missing get indicator state ** (soffice:16426): WARNING **: Unknown event notification 36 ** (soffice:16426): WARNING **: Unknown event notification 36 ** (soffice:16426): WARNING **: missing get indicator state ** (soffice:16426): WARNING **: Unknown event notification 36 ** (soffice:16426): WARNING **: missing get indicator state
Take an .ods file with the problem. Save it with another name. Close Calc. Reopen this second file. Try to modify it. It crashes. Then Reopen it. Select everything, delete the content (Suppr key). Save it. Close Calc. Reopen this second file. You can modify the content in the normal way. I'll try to send a "buggy" file whitout any private content if I find one
For Writer now : It doesn't crash when editing, saving, modifying a completely new file.
For the test, if you have any accessibility options enabled, could you disable them and try again?
Hi. I disabled everything in Accessibility options in LibreOffice (all was checked, except the first one), and restart. Still crash in Writer and Calc. :(
I meant on your Linux env not on LO.
Ok. I'm using xfce4. After verification, all options are already inhibited in xfce4 settings. Nothing particular in Yast. What else. French keyboard and locate.
@scaalpbug: Would be great if you could provide a backtrace of the crash: https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace Also please report if exporting SAL_USE_VCLPLUGIN=gtk before running LO makes any difference. Thanks.
Also, you can give a try after having renamed your LO directory profile (see https://wiki.documentfoundation.org/UserProfile#GNU.2FLinux)
Changing to NEEDINFO until the requested information is provided.
Noted instructions. Just one note : travelling past days, I saw that this bug do not occur on my laptop (same architecture, same LibreOffice version, same Linux distribution, also up-to-date)
Created attachment 119003 [details] backtrace, document editing, crash after entering few characters Crash after entering few characters LibreOffice profile was deleted at previous launch (no effect) OpenSuse Tumbleweed, up to date as 2015-09-24 LibreOffice Version: 5.0.1.2.0+ / Build ID: 00m0(Build:2) / Locale : fr-FR (fr_FR.utf8)
As requested, a backtrace attached. Profile deletion didn't change anything. Thanks
Thanks for the backtrace. As I said, the workaround is to do export SAL_USE_VCLPLUGIN=gtk. (The easiest way is to add it to your .bash_profile, and logout-login for the change to take effect.) *** This bug has been marked as a duplicate of bug 94013 ***