Red Hat Bugzilla – Bug 1397992
[fix available] Crash in calc after closing dialog box with a11y enabled
Last modified: 2017-08-01 08:21:15 EDT
Created attachment 1223393 [details] backtrace Description of problem: Libreoffice calc crashes after closing dialog box. This seems to only happen on system which was upgraded to 7.3 and with existing user. With clean install or new user the issue is not reproducible. console output [snip]: (soffice:8177): GLib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed (soffice:8177): GLib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed (soffice:8177): GLib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed (soffice:8177): GLib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed (soffice:8177): GLib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed ... ** (soffice:8177): WARNING **: Unknown event notification 34 ** (soffice:8177): WARNING **: Unknown event notification 35 ** (soffice:8177): WARNING **: Unknown event notification 34 ** (soffice:8177): WARNING **: Unknown event notification 35 ** (soffice:8177): WARNING **: Unknown event notification 34 ** (soffice:8177): WARNING **: Unknown event notification 35 Version-Release number of selected component (if applicable): libreoffice-5.0.6.2-3.el7 gtk2-2.24.28-8.el7 How reproducible: 100% Steps to Reproduce: 1. Load spreadsheet (ods) 2. Go to Sort dialog; Data > Sort 3. Click Cancel Actual results: Crash - recovery dialog Expected results: No crash Additional info:
I have seen that backtrace before I think
This crashes for some users and not for others can I confirm my suspicion that the difference is that gsettings get org.gnome.desktop.interface toolkit-accessibility is true for the crashing config and false for the not-crashing config. If this is the case then a temporary workaround may be (unless the user needs a11y support of course) is to gsettings set org.gnome.desktop.interface toolkit-accessibility false
Created attachment 1223794 [details] I suspect this will fix it My proposed patch, but I need to build and test this.
(In reply to Caolan McNamara from comment #2) > This crashes for some users and not for others can I confirm my suspicion > that the difference is that > > gsettings get org.gnome.desktop.interface toolkit-accessibility > > is true for the crashing config and false for the not-crashing config. > > If this is the case then a temporary workaround may be (unless the user > needs a11y support of course) is to > > gsettings set org.gnome.desktop.interface toolkit-accessibility false I can confirm that with "toolkit-accessibility" key set to false, I'm not able to reproduce the crash.
yeah, proposed patch works
I can confirm the crash is fixed. There are still warnings present in console output. ** (soffice:11703): WARNING **: Invalidate all children called (soffice:11703): GLib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed (soffice:11703): GLib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed (soffice:11703): GLib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed (soffice:11703): GLib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed ** (soffice:11703): WARNING **: Unknown event notification 34 ** (soffice:11703): WARNING **: Unknown event notification 35 ** (soffice:11703): WARNING **: Unknown event notification 34 ** (soffice:11703): WARNING **: Unknown event notification 35 ** (soffice:11703): WARNING **: Unknown event notification 34 ** (soffice:11703): WARNING **: Unknown event notification 35 (soffice:11703): GLib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed (soffice:11703): GLib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:1975