Bug 158444 - Fontwork text cannot be edited after first size change or edit
Summary: Fontwork text cannot be edited after first size change or edit
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Draw (show other bugs)
Version:
(earliest affected)
7.6.3.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-11-29 19:15 UTC by Jens
Modified: 2024-07-18 03:15 UTC (History)
4 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 Jens 2023-11-29 19:15:11 UTC
Description:
Insert a fontwork text.
Change the text using F2 - it works.
Change the size of the fontwork.
Press F2 again.
Now when you type the letters are partially replaced, sometimes the cursor seems to jump around randomly, it is not possible to edit the text properly.

Steps to Reproduce:
See above.

Actual Results:
See above.

Expected Results:
See above.


Reproducible: Always


User Profile Reset: No

Additional Info:
[Information automatically included from LibreOffice]
Locale: de
Module: DrawingDocument
[Information guessed from browser]
OS: Linux (All)
OS is 64bit: yes
Comment 1 Regina Henschel 2023-11-29 23:07:47 UTC
I get no problems entering edit mode with F2 key and then changing the text. Tested with Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 9602f8a9318dd4d3409856e2ae06abe96e72b51b
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-US
Calc: CL threaded
Comment 2 Dayana James 2023-12-12 11:55:34 UTC
I am not able to reproduce it. There is no changes happened to the font work when pressing the F2 key.
Tested with Version: 24.2.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: 0ddd9f7e055a0c1ecb120de3e40c3fdb8373e9dc
CPU threads: 4; OS: Windows 10.0 Build 22000; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL threaded
Comment 3 raal 2023-12-12 17:42:38 UTC
No repro with Version: 24.2.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: 0f82e9d42822e627edd1fb3b3c87e1f8a22136a4
CPU threads: 4; OS: Linux 6.2; UI render: default; VCL: gtk3
Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US
Calc: threaded
Comment 4 Stéphane Guillou (stragu) 2023-12-19 15:24:51 UTC
Can't reproduce either in Draw:

Version: 7.6.4.1 (X86_64) / LibreOffice Community
Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

Jens, seeing that 4 contributors could not reproduce, can you please:
- test again with a new profile (or in safe mode)
- if you can still reproduce, give more precise steps (including which Fontwork preset was used) and possibly attach an example document, and a screenshot showing the issue.

Thank you!
Comment 5 QA Administrators 2024-06-17 03:15:55 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2024-07-18 03:15:52 UTC
Dear Jens,

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