[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #41552] GUI crashes with ""QSpiAccessible::acc

From: Mike Miller
Subject: [Octave-bug-tracker] [bug #41552] GUI crashes with ""QSpiAccessible::accessibleEvent not handled"
Date: Wed, 19 Feb 2014 23:39:16 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/32.0.1700.123 Safari/537.36

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:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]