Bug 155139 - conflict with fcitx input
Summary: conflict with fcitx input
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.3.7.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-05-03 18:38 UTC by calidion
Modified: 2023-12-02 03:16 UTC (History)
1 user (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 calidion 2023-05-03 18:38:37 UTC
Description:
Sometimes unable to input Chinese characters like ",。、"。
Close and reopen will solve this problem.
But soon it will show up again.

Actual Results:
There is no clear step by step instructions on reproducing it.

Expected Results:
There is no clear step by step instructions on reproducing it.


Reproducible: Sometimes


User Profile Reset: No

Additional Info:
There is no clear step by step instructions on reproducing it.
Comment 1 Julien Nabet 2023-05-04 06:06:22 UTC
Please upgrade to 7.4.6 or brand new LO 7.5.2 and give a new try.
Indeed 7.3 branch is EOL.
Comment 2 QA Administrators 2023-11-01 03:14:18 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2023-12-02 03:16:33 UTC
Dear calidion,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA 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 our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp