Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#41935 - [abiword] shift-control-direction-key text selection no longer functional

Attached to Project: Arch Linux
Opened by Clayton Hardiman (cjazz) - Thursday, 11 September 2014, 14:38 GMT
Last edited by Jan de Groot (JGC) - Tuesday, 17 February 2015, 13:12 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Jan de Groot (JGC)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

Any keyboard combination using shift-control no longer selects text, which means the keyboard can no longer be used to select text by word or paragraph or to the beginning or end of text. Control-direction key moves the cursor as expected, and shift-direction key selects text, but they fail to work in combination. This is such a common convention for word processors and text editors that I have come to use it constantly and almost instinctively, including in my browser as I wrote this bug report. I filed a bug upstream in January (Bugzilla Bug 13596), and Abisource developers were kind enough to produce a working patch in February, which I have attached below.

Additional info:
* package version(s) Version 3.0.0-3. I believe the regression dates back at least to version 2.92.
* config and/or log files etc.


Steps to reproduce:
   abiword_shift_control_selecti... (1.5 KiB)
This task depends upon

Closed by  Jan de Groot (JGC)
Tuesday, 17 February 2015, 13:12 GMT
Reason for closing:  Fixed
Comment by Clayton Hardiman (cjazz) - Saturday, 17 January 2015, 13:30 GMT
Perhaps this bug should be closed. It is corrected upstream in version 3.0.1, and version 3.0.0.3, which includes the bug, has been flagged out of date. Therefore, updating to the 3.0.1 should correct the bug.

Loading...