Bug 80364 - UI: ctrl+shift+space not working in linux
Summary: UI: ctrl+shift+space not working in linux
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
4.2.4.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Shortcuts-Accelerators
  Show dependency treegraph
 
Reported: 2014-06-22 20:24 UTC by Tom Agnew
Modified: 2017-10-25 12:47 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tom Agnew 2014-06-22 20:24:07 UTC
Ctrl+shift+space should highlight the current column.  It works under windows, but not linux.
Comment 1 Julien Nabet 2014-06-22 20:28:34 UTC
On pc Debian x86-64 with 4.2.4.2 LO Debian package, I don't reproduce this.

Did you install any LO specific extensions?
Do you have accessibility enabled?
Could you rename your LO directory profile (see https://wiki.documentfoundation.org/UserProfile#GNU.2FLinux) and give it a try?
Comment 2 Yousuf Philips (jay) (retired) 2014-06-22 20:59:56 UTC
Hi Tom,

I'm running Linux Mint and it works fine for me. What linux distro are you running?
Comment 3 QA Administrators 2015-01-10 18:06:18 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2015-02-11 19:48:21 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. 
Please do not:
a) respond via email 
b) update the version field in the bug or any of the other details on the top section of FDO

Message generated on: 2015-02-11