GNOME Bugzilla – Bug 659240
Orca claims selected items are unselected in the Nautilus icon view
Last modified: 2012-02-20 20:10:16 UTC
Created attachment 196716 [details] Debug file with show perhaps why happening the described problem Dear Developers, Hopefuly following problems is not GTK3 specific bugs: When I moving the desktop icons with arrow keys, Orca spokening wrong selection state for actual selected desktop icon (spokening not selected state, but this is not true for actual highlighted icon), and where am I command spokening invalid selection count and position index values. Reproducation steps, if your desktop have multiple icons: 1. Activate the desktop. 2. Move desktop icons with arrow keys. You will be hear always the actual selected icon is unselected, but I think this is not true. 3. Look what informations spokening where am I command for actual highlighted desktop icon. The spokened selection count and position index values will be invalid. I attaching the required debug.out file. In debug.out file I found following traceback error messages: generate braille for focused app.name='nautilus' name='Ubuntu 11.10 telepítése' role='icon' state='focused selectable' relations='' (args={'formatType': 'focused', 'role': <enum ATSPI_ROLE_ICON of type Role>, 'mode': 'braille', 'recursing': True}) using '(includeContext and (ancestors + (rowHeader and [Region(" " + asString(rowHeader))]) + (columnHeader and [Region(" " + asString(columnHeader))]) + (radioButtonGroup and [Region(" " + asString(radioButtonGroup))]) + [Region(" ")]) or []) + [Component(obj, asString(((label + displayedText + imageDescription) or name) + roleName))] + (nodeLevel and [Region(" " + asString(nodeLevel))])' GENERATION TIME: 0.0005 ----> includeContext=True PREPARATION TIME: 0.0009 generate braille for focused app.name='nautilus' name='Ikonnézet' role='layered pane' state='focused' relations='' (args={'formatType': 'focused', 'role': <enum ATSPI_ROLE_LAYERED_PANE of type Role>, 'mode': 'braille', 'includeContext': False, 'recursing': True}) using '[Component(obj, asString(label + displayedText + value + roleName + required))]' GENERATION TIME: 0.0006 ----> label=[] GENERATION TIME: 0.0007 ----> displayedText=['Ikonn\xc3\xa9zet'] Traceback (most recent call last):
+ Trace 228474
globalsDict[arg] = self._methodsDict[arg](obj, **args)
return [self._script.utilities.textForValue(obj)]
minimumIncrement = (value.maximumValue - value.minimumValue) \
Atspi.Value.minimumValue = property(fget=lambda x: exwrap(Atspi.Value.get_minimum_value, x))
raise LookupError LookupError
Attila
I can confirm this in Rawhide. And it's not limited to the Desktop. It seems to be true for Nautilus icon view (which the desktop you describe is one example). Bah. Investigating further.... Thanks for the report!!
And the problem seems to be that the reported states for the selected icon are: * focused * selectable In addition to the other missing states, we have know way to know it's selected. And this is something we'd like to know accurately because one can navigate amongst icons and have them focused but not selected. Mike Gorse had mentioned he was working on fixing some Gtk+ 3 related regressions in Nautilus. I do not recall what those regressions were. So adding him to the CC list for input before I go off and file a Nautilus or Gtk+ bug he's already fixing. But this is not an Orca bug I'm afraid. Thanks for the report!
I have a Nautilus patch attached to BGO#650897 that I submitted at the last minute to fix that and other issues; awaiting review. The original patch for BGO#650904 had an Orca work-around that I was hoping we wouldn't need...
Thanks for the update Mike! Given that I spent a couple of hours this weekend hunting down a significant "Orca bug" which actually turned out to be an old hack breaking as a result of a recent and sane change made in Orca, I am incredibly reluctant to add new workarounds in Orca. Therefore... Have you pinged the Nautilus team about fixing the bug where it belongs fixed?
Joanie, selection related Nautilus bug fix works correct. Before I opening tomorrow new bugreport for Orca, I write my experiences for new Nautilus version (in Oneiric now 3.1.92-0Ubuntu2 version are packaged). Now, if I doing Orca where am I output, the selected icon count are right, but the actual position index value is not. For example, if the desktop have one icon, the actual where am I reported icon position number is 0. If checked the speak child position check box in Orca preferences dialog, Orca doesn't spokening position index values with Nautilus icon view. You experiencing similar results? Anybody already reported a similar speak child position related problem with new Nautilus related? If not, tomorrow morning I generating a debug.out file with shows what happening if I do where am I operation for Nautilus icon view, and what happening if checked the speak child position check box with Orca preferences dialog. Attila
This problem seems to have been fixed in Nautilus. I can no longer reproduce it. *** This bug has been marked as a duplicate of bug 650897 ***