After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 456304 - [blocked] Where am I command not handling text selection in gnome-terminal correctly when Numpad-+ is double clicked.
[blocked] Where am I command not handling text selection in gnome-terminal co...
Status: RESOLVED NOTGNOME
Product: orca
Classification: Applications
Component: general
2.19.x
Other Linux
: Normal normal
: ---
Assigned To: Joanmarie Diggs (IRC: joanie)
Orca Maintainers
Depends on: 456639
Blocks:
 
 
Reported: 2007-07-12 17:02 UTC by Rich Burridge
Modified: 2018-02-08 12:49 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Rich Burridge 2007-07-12 17:02:19 UTC 
Steps to reproduce.

1/ Start Orca.
2/ Start gnome-terminal
3/ Select some text in gnome-terminal. I did this by vi'ing a
   text file and then click-drag-releasing the mouse over part of
   the text.
4/ Double click Numpad-+

The selected text is not spoken.

See also Orca bug #409731 which is affected by this problem.
Comment 1 Rich Burridge 2007-07-13 15:56:13 UTC 
I started Orca and gnome-terminal. I used the mouse to select a word in the terminal by double clicking it.

Setting debugging to LEVEL_OFF in where_am_I.py, and double
pressing Numpad-Enter gives the following output:

whereAmI:           
  label=                   
  name=Terminal            
  role=terminal                 
  mnemonics=['', '']        
  parent label=           
  parent name=                  
  parent role=filler           
  double-click=True
  orca-key=False
_getTextContents: caretOffset=1433, nSelections=1
_getTextSelections: getNSelections:  1
_getTextSelection: selection start=1433, end=1433
_getTextSelection: selected text=<>
newLine: <>
first text utterances=['', 'terminal', '']
SPEECH OUTPUT: ''
SPEECH OUTPUT: 'terminal'
SPEECH OUTPUT: ''
text utterances=['selected', '']
SPEECH OUTPUT: 'selected'

The interesting part here is that it correctly thinks there is
a selection, but when you call:

        for i in range(0, nSelections):
            [startOffset, endOffset] = textObj.getSelection(i)

in _getTextSelection() in where_am_I.py, it returns bogus results.
No matter what I select in the terminal window, I get back a start and
end offset of 1433.

This looks like yet another vte bug. I'll file that next and block
this one against it. 

I haven't marked bug #409731 as depending on this one. I think we
should close that separately if it's working for other things, like
gedit, Evolution and OOo Writer.
Comment 2 Willie Walker 2009-06-17 14:25:50 UTC 
Just adding a response to get this off our "bugs without a response" list.  Silly, I know, but it's needed since there was only one commenter on this.
Comment 3 Joanmarie Diggs (IRC: joanie) 2010-09-14 08:10:24 UTC 
This bug is still present and still blocked by the vte bug.
Comment 4 Joanmarie Diggs (IRC: joanie) 2018-02-08 12:46:54 UTC 
Closing blocked bugs because we need the issue fixed in the blocker.