Bug 146616 - Dead keys not recognized in comments in Writer
Summary: Dead keys not recognized in comments in Writer
Status: RESOLVED DUPLICATE of bug 145580
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.2.4.1 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-01-06 13:36 UTC by matf
Modified: 2022-06-13 11:58 UTC (History)
0 users

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 matf 2022-01-06 13:36:35 UTC
Description:
I use us-intl with dead keys as xkb layout on Linux and it has worked fine for years, but since a few weeks or months, dead keys have stopped working in comments in Writer. They work fine in the main body of text, they are just ignored in comments. In Calc, dead keys work everywhere, including comments, so I'm not sure what is wrong. 

Apart from LibreOffice, the dead keys work in all programs I tried, Writer's comments are really the only place where I found such an issue.

My distribution is Solus 4.3 (rolling and up to date) with kernel 5.14.21-210.current x86_64 and LibreOffice 7.2.4.1 20(Build:1). I update my distribution and packages every week, so I am not sure when the bug appeared in Writer, but it should be a matter of max 2 or 3 months before this version.

I am unsure at the moment if the issue comes from LibreOffice sources or from the package that is provided in the Solus repository. It could also be a local issue, but since the issue only occurs in Writer and not other programs, not even other LibreOffice programs, I'm unsure how it would be a local system setting.



Steps to Reproduce:
1. Open a new document LibreOffice Writer
2. Press Ctrl+Alt+C to create a new comment
3. Type dead keys and profit.

The issue occurs even if the new document has not been saved yet, so it should not be related to the extension.

Actual Results:
Dead keys are not registered.

Expected Results:
They should be registered, just like they are out of comments.


Reproducible: Always


User Profile Reset: Yes



Additional Info:
Version: 7.2.4.1 / LibreOffice Community
Build ID: 20(Build:1)
CPU threads: 4; OS: Linux 5.14; UI render: default; VCL: gtk3
Locale: en-GB (en_GB.utf8); UI: en-GB
Calc: threaded
Comment 1 Timur 2022-01-14 12:31:41 UTC
I don't know what "dead keys" but I guess you mean "with modifier" so that would be a duplicate. Please search before reporting. .

*** This bug has been marked as a duplicate of bug 145580 ***
Comment 2 matf 2022-01-14 12:51:45 UTC
Dead keys are this: https://en.wikipedia.org/wiki/Dead_key#Electronic_keyboards

These are not the same as characters typed with a modifier (which work absolutely fine for me in comments). I am not sure this is the same issue, I don't experience 145580.
Comment 3 matf 2022-01-14 12:53:52 UTC
Actually 145580 mentions both characters typed as dead keys (the first comment with the example on "ã") and characters typed with a modifier key. I only experience the first part, which suggests both symptoms may have different causes.
Comment 4 Timur 2022-01-14 14:35:17 UTC
You need to wait someone to test. 
But if it started in 7.2.3, it's likely a duplicate. 
So better to be duplicated, and checked on fix.
Comment 5 padovani 2022-03-23 14:14:11 UTC
Hi, 

I have the same issue in comments not allowing me to introduce diachritics that demand the use of dead keys. For example: using a PT-BR (ABNT) keyboard that has the "ç" key: it introduces the character without problems in comment balloons. However, I can't introduce "é" by using the usual sequence using this keyboard: "´" + "e".

Note: I can paste comments with those diachritics or use them in document's body.

Further info about my system:

Version: 7.2.6.2 / LibreOffice Community
Build ID: 20(Build:2)
CPU threads: 8; OS: Linux 5.16; UI render: default; VCL: gtk3
Locale: pt-BR (en_US.UTF-8); UI: en-US
7.2.6-1
Calc: threaded
Comment 6 padovani 2022-03-23 14:15:46 UTC Comment hidden (obsolete)
Comment 7 Timur 2022-06-13 10:26:00 UTC
There were some fixes in bug 145580 from LO 7.2.7 and in bug from 7.4.0.
Can you retest?
Comment 8 matf 2022-06-13 11:55:45 UTC
I no longer experience the issue in 7.3.3.2 and this is such a relief! Thanks a lot to the team for the fix.
Comment 9 Timur 2022-06-13 11:58:38 UTC
So probably a duplicate.

*** This bug has been marked as a duplicate of bug 145580 ***