Bug 145298 - Keyboard Shortcuts partially unassignable with LibreOffice Writer
Summary: Keyboard Shortcuts partially unassignable with LibreOffice Writer
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.1.6.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Shortcuts-Accelerators
  Show dependency treegraph
 
Reported: 2021-10-24 16:58 UTC by Dircules
Modified: 2026-01-04 03:11 UTC (History)
3 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 Dircules 2021-10-24 16:58:52 UTC
Description:
Some assignments for keys don't work. I noticed that
Tools > Customize > Keyboard > Strg+Alt+PgUp -> Modify
Tools > Customize > Keyboard > Strg+Alt+PgDn -> Modify
Tools > Customize > Keyboard > Strg+Alt+Shift+PgUp -> Modify
Tools > Customize > Keyboard > Strg+Alt+Shift+PgDn -> Modify
don't make any effect.
Similar customizings however, like Strg+Alt+Pos1, but also Alt+Shift+PgUp, work as expected.
I didn't perform an extensive survey on which combinations are concerned, but I think you should check the whole thing on occasion. Thank you.

And while you're at it: I wonder why some keys are excluded from customization? For instance, I badly miss combinations like "Ctrl+Alt++", and "Ctrl+Alt+-".

Steps to Reproduce:
1. Menu Tools > Customize, Tab Keyboard 
2. Scroll down to one of the mentioned Combinations, e.g. Ctrl+Alt+PgUp
3. Select any function (best one where the effect should be immediateliy visible)
4. Click "Modify" and "OK".
5. Test your assignment and prepare to cry.

Actual Results:
Nothing happened.

Expected Results:
Assignment of a key combination to a certain function.


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
Version: 7.1.6.2 (x64) / LibreOffice Community
Build ID: 0e133318fcee89abacd6a7d077e292f1145735c3
CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: default; VCL: win
Locale: de-DE (de_DE); UI: de-DE
Calc: threaded
Comment 1 Rainer Bielefeld Retired 2021-10-31 10:23:56 UTC
REPRODUCIBLE with Installation of Version:7.2.1.2 (x64); Build ID: 87b77fad49947c1441b67c559c339af8f3517e22; CPU threads: 12; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win; Locale: de-DE (de_DE); UI: de-DE; Calc: threaded - My nnormal User Profile
1. open 1 Page Writer document
2. ˋTools → Customize → Keyboard → <Ctrl+Alt+PageUp> → RecordMacro → Modifyˊ
   » function appears in shortcut list
3. [ok]
4. <Ctrl+Alt+PageUp>
   Expected: Macro recording dialog appears
   Actual:   Nothing                                                  😥

Additional Test:
redo from (1), but for shortcut <Alt+0>
Expected = actual = Macro recording dialog appears in step 4

Additional info:
================
a) Assigning works fine for CALC:
11. open 1 Page Writer document
12. ˋTools → Customize → Keyboard → <Ctrl+Alt+PageUp> → RecordMacro → Modifyˊ
   » function appears in shortcut list
13. [ok]
14. <Ctrl+Alt+PageUp>
   Expected: Macro recording dialog appears
   Actual:   as expected                                             👌

b) not yet tested for Draw, Impress, ...

c) Already broken in Version: 6.4.7.2 (x64)
  I can't tell whether that ever die work.

d) Related to "Bug 143096 - Numerous offered keyboard shortcuts do not work 
   in Linux and MacOS"?

e) Related to "Bug 49091 - UI: Alt-Left, Alt-Right keyboard shortcuts
   ineffective"?
Comment 2 Dircules 2021-11-02 16:11:18 UTC
In addition to this bug, it is to critizize that some default keyboard shortcuts are occupied but not listed in Tools > Custompize > Keyboard.
For instance, I assigned Shift+Alt+Right to a macro which inserts a right arrow (Wingdings 3, char 0x67) into the text.  And it works fine unless your cursor position is within a table. Here, the shortcut Shift+Alt+Right will decrease the horizontal size of the table cell.
Double seizures should not be possible as they lead to inconsistency, or at least surprising behavior.
Comment 3 daniilmedvedev 2022-12-06 11:50:30 UTC Comment hidden (spam)
Comment 4 Dieter 2022-12-19 08:23:10 UTC
Status NEW because of comment 1
Comment 5 joseph999 2023-05-15 09:22:33 UTC Comment hidden (spam)
Comment 6 bishopcara23 2023-07-18 10:55:59 UTC Comment hidden (spam)
Comment 7 daybossnew@gmail.com 2023-07-25 09:05:31 UTC Comment hidden (spam)
Comment 8 : davidharis 2023-07-28 05:00:29 UTC Comment hidden (spam)
Comment 9 maserlorry12 2023-08-22 06:39:25 UTC Comment hidden (spam)
Comment 10 nigelglobel21 2023-08-22 09:26:59 UTC Comment hidden (spam)
Comment 11 doerobert129 2023-09-16 11:59:31 UTC Comment hidden (spam)
Comment 12 shakeshackmenu01 2024-01-04 05:10:04 UTC Comment hidden (spam)
Comment 13 QA Administrators 2026-01-04 03:11:00 UTC
Dear Dircules,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug