GNOME Bugzilla – Bug 540124
Orca couldn't read the warning message of theme.
Last modified: 2009-01-21 15:58:13 UTC
Please describe the problem: Orca couldn't read the warning message of theme. Steps to reproduce: 1. Launch orca by clicking "Launch ->All Applications->Universal Access->Orca Screen Reader And Magnifier". 2. Right click the desktop, select "Desktop Backgroud". 3. Go to the "Theme" tab, and select "LargePrint" by <Tab> and arrow key. Then it will popup the warning message as follows: The theme will not look as intended because the required icon theme "LargePrint" isn't installed. Actual results: Orca couldn't read the warning message. Expected results: Orca should read the warning message. Does this happen every time? Yes. Other information: Operating system: Solaris_Nevada_92+Vermillion_93
I cannot reproduce the warning message dialog, and have tried several things to force it to appear. So...can you please create an Orca debug log that captures the events associated with this problem? The instructions can be found at http://live.gnome.org/Orca/Debugging, and please post the resulting log here as an attachment. Thanks!
Created attachment 113893 [details] Orca debug log
Comment on attachment 113893 [details] Orca debug log Orca debug log is attached here
Thanks! At line 2373 in the debug file, I see this traceback: Traceback (most recent call last):
+ Trace 202327
ObjectEvent self.listeners[key](event)
teChanged state = orca_state.locusOfFocus.getState()
This is due to the locusOfFocus being set to None due to the nautilus window deactivation at line 2173. After that, the gnome-appearance-properties app then seems to build up its dialog and ultimately issues a window-activated event and a focus event, but not before it issues the state changed event. I think all we might need to do in this case is just include a defensive check for locusOfFocus not being None.
Created attachment 114206 [details] [review] Patch to check for locusOfFocus == None in onStateChanged This patch checks to make sure locusOfFocus exists before doing work with it in onStateChanged. Since I cannot reproduce the bug, can you please try building/installing Orca with this patch and testing it ye.guo?
Orca still couldn't read the warning message after I builded and installed it with the patch.
How did you get your system into a state where the LargePrint theme was messed up? I've tried hard to do this on purpose, but cannot seem to achieve the desired effect of messing my machine up. :-(
Hi Will, we will re-test this bug with vermillion_95 and give update by then. Hoping gnome-appearance-properties working well on build 95.
Created attachment 116083 [details] Screenshot While testing on Ubuntu, I came across the following dialog -- I highlighted the message in red. This message appears in the same dialog as the theme selection dialog instead of a separate popup dialog -- is this what you are observing?
(In reply to comment #9) > Created an attachment (id=116083) [edit] > Screenshot If this is indeed it, what we're getting as notification that this message appeared is the following event: vvvvv PROCESS OBJECT EVENT object:state-changed:showing vvvvv OBJECT EVENT: object:state-changed:showing detail=(1,0) app.name='gnome-appearance-properties' name='None' role='filler' state='enabled horizontal sensitive showing visible' relations='' ^^^^^ PROCESS OBJECT EVENT object:state-changed:showing ^^^^^ The filler that appears ends up having a filler which in turn has another filler which in turn has two icons and a label. One of the icons doesn't seem to be visible whereas the other is the warning icon. The label is the warning text that is shown. We could potentially write some code to detect that a filler has suddenly appeared in an already showing filler and then automatically speak icons and labels it might find underneath that filler. Alternatively, we could potentially just call this bad UI design and request that the app pops up a real error dialog. As an example, I'm guessing that in all my attempts to reproduce this problem, I was looking for an error dialog and never noticed the message.
Closing as WONTFIX. We looked at this and decided it's not mandatory to automatically present this information to the user. The user can still browse for it if needed, however.