As previously reported in ticket #71237 and #118269, the Ctrl+Alt+C supposed to add a comment is not working. In my case, it does not have any effect, whether in Writer, Impress or Calc. Adding a comment using other means (like the mouse button) works without any issue. This occurs on Windows 11 Family 22H2 (22621), with a Microsoft Natural Ergonomics 4000 keyboard and the CMS (Canadian Multilingual) keyboard layout. It persists after rebooting and upgrading (from 7.0). The information below is incorrect about the Windows version. Version: 7.5.4.2 (X86_64) / LibreOffice Community Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6 CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: fr-CA (fr_CA); UI: fr-FR Calc: threaded
Sounds a lot like bug 38891. Can you please see if: - other Ctrl + Alt shortcuts don't work? - when you use those shortcuts with the cursor on the page (in Writer), do you get some character input, or absolutely nothing happens? See also the meta bug 107244. Thank you!
Thanks to you Stéphane I am using the CSA layout, which does not assign any character to Alt Car + C : https://fr.wikipedia.org/wiki/CAN/CSA_Z243.200-92#/media/Fichier:KB_Canadian_Multilingual_Standard_comment-fr.svg The only other shortcut using Ctrl+Alt which I can see is the one for the extension manager, Ctrl+Alt+E, which also does not work. However, that is because CAN/CSA has the Euro symbol € on level 3 for E. That being said, I figured out that Ctrl+Alt+C did have an effect, ie removing focus from the window. That is because a utility was globally catching that combination. It is BenQ's Display Pilot which uses that shortcut to switch color mode: https://defkey.com/benq-display-pilot-shortcuts For reference, here are other programs which catch Ctrl+Alt+C: https://defkey.com/what-means/ctrl-alt-c I am not sure what can be done with this issue. Hopefully there is a way for LibreOffice to poll which combinations are globally caught and react appropriately.
(In reply to Filipus Klutiero from comment #2) > The only other shortcut using Ctrl+Alt which I can see is the one for the > extension manager, Ctrl+Alt+E, which also does not work. However, that is > because CAN/CSA has the Euro symbol € on level 3 for E. Right, which would be the issue many users hit, tracked in bug 119676 > That being said, I figured out that Ctrl+Alt+C did have an effect, ie > removing focus from the window. That is because a utility was globally > catching that combination. It is BenQ's Display Pilot which uses that > shortcut to switch color mode: > https://defkey.com/benq-display-pilot-shortcuts Not sure much can be done here, as we can't cater for all the other software catching shortcuts before LO does. Will ask in the dev channel.
(In reply to Stéphane Guillou (stragu) from comment #3) > (In reply to Filipus Klutiero from comment #2) > > The only other shortcut using Ctrl+Alt which I can see is the one for the > > extension manager, Ctrl+Alt+E, which also does not work. However, that is > > because CAN/CSA has the Euro symbol € on level 3 for E. > > Right, which would be the issue many users hit, tracked in bug 119676 Ah, indeed. Thanks again Stéphane > > That being said, I figured out that Ctrl+Alt+C did have an effect, ie > > removing focus from the window. That is because a utility was globally > > catching that combination. It is BenQ's Display Pilot which uses that > > shortcut to switch color mode: > > https://defkey.com/benq-display-pilot-shortcuts > > Not sure much can be done here, as we can't cater for all the other software > catching shortcuts before LO does. > Will ask in the dev channel. Thanks. It's more about managing conflicts than "catering" for other software. Visually, shortcut hints could be displayed in gray when a conflict is detected. However, to detect them, the OS needs to allow polling for handlers.
(In reply to Filipus Klutiero from comment #4) > It's more about managing conflicts than "catering" for other > software. Visually, shortcut hints could be displayed in gray when a > conflict is detected. However, to detect them, the OS needs to allow polling > for handlers. I'll go with tagging this bug with "needsDevAdvice", as I'm out of my depth here. I know Caolán has fixed a few shortcut issues in the past. Any opinion about the above, Caolán?
The problem sounds familiar to me. Pressing CTRL+ALT+C inserts the copyright symbol (©) in Writer & Calc if I set the language to Dutch with a QWERTY/USA keyboard configuration. If I set the language to English + keyboard configuration USA it works as expected. I'm also using a Microsoft Natural Ergonomics 4000 keyboard. Just a coincidence??
(In reply to Telesto from comment #6) > [...] > > I'm also using a Microsoft Natural Ergonomics 4000 keyboard. Just a > coincidence?? Yes, that's just a coincidence. The Dutch layout will generate that symbol no matter what physical keyboard is used. Thank you for that point Should these 2 issues (conflict with Display Pilot and the Dutch keyboard layout) be treated separately or as a single one?
Dear Philippe Cloutier, 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
(In reply to QA Administrators from comment #8) > Dear Philippe Cloutier, > > 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. It is unclear what you mean by "open bugs", and why you mention that in the ticket of a bug which is not considered confirmed, but I fail to see any change on: > Version: 25.2.6.2 (X86_64) / LibreOffice Community > Build ID: 729c5bfe710f5eb71ed3bbde9e06a6065e9c6c5d > CPU threads: 8; OS: Windows 11 X86_64 (10.0 build 26200); UI render: Skia/Raster; > VCL: win > Locale: fr-CA (fr_CA); UI: fr-FR