[Octave-bug-tracker] [bug #41552] GUI crashes with ""QSpiAccessible::accessibleEvent not handled"

[Mike Miller]

Update of bug #41552 (project octave):

                  Status:               Need Info => Wont Fix               

    _______________________________________________________

Follow-up Comment #11:

Right, I don't think we want to be doing this, always be wary when considering
overwriting user environment variables.

If Octave is a victim of problems with Qt's accessibility plugin, then so be
it, users should be advised how to turn that setting off until Ubuntu or Qt
get the problem fixed. The appropriate command to disable Qt a11y on modern
Debian and Ubuntu systems seems to be:


gsettings set org.gnome.desktop.interface toolkit-accessibility false


After setting that and logging out and back in (I'm not sure how or why it
gets set to true in the first place), the user's X session should no longer
have the QT_ACCESSIBILITY environment variable set.

If there is a reproducible crash in Octave that we can determine is due to
something that Octave is doing wrong, then that's worth fixing, but otherwise
I'd leave this as a won't fix. I haven't seen a crash yet, just lots of
debug/warning messages.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?41552>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/