Bug 115191 - EDITING: Impress not set size properly on basic shapes
Summary: EDITING: Impress not set size properly on basic shapes
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
5.4.4.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-24 10:56 UTC by alexis6307
Modified: 2019-06-08 03:05 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Video evidence (923.32 KB, video/mp4)
2018-01-24 10:56 UTC, alexis6307
Details

Note You need to log in before you can comment on or make changes to this bug.
Description alexis6307 2018-01-24 10:56:57 UTC
Created attachment 139323 [details]
Video evidence

In LibreOffice Impress when I set a basic shape, for example, a square or rectangle, if I try to set a different size it doesn't retain the size number but the shape retains visually size.

Please see the video attached for best comprehension.
Comment 1 Buovjaga 2018-02-13 09:51:16 UTC
It works OK for me. Please try with 6.0.1

If you are on Linux, a quick way to test is https://www.libreoffice.org/download/appimage

Arch Linux 64-bit
Version: 6.0.1.1
Build ID: 6.0.1-1
CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: kde4; 
Locale: fi-FI (fi_FI.UTF-8); Calc: group

Set to NEEDINFO.
Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away.
Comment 2 alexis6307 2018-02-13 12:05:17 UTC
Still failing, I have tested this in 3 different Linux computers.
Comment 3 Buovjaga 2018-02-15 16:10:02 UTC
Please copy and paste here the contents of your Help - About. This allows us to know more about your system.

I just re-tested again also with gtk3 and gtk2 backends, but no problem.

Please also try: Help - Restart in safe mode and then Continue in safe mode without doing anything else.
Comment 4 Xisco Faulí 2018-02-15 17:58:05 UTC
I can't reproduce it in

Version: 6.0.1.1
Build ID: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1
CPU threads: 4; OS: Linux 4.13; UI render: default; VCL: gtk3; 
Locale: ca-ES (ca_ES.UTF-8); Calc: group

Please, provide the info from Help - About LibreOffice and in safe mode.
Comment 5 alexis6307 2018-02-16 10:21:20 UTC
Hi guys,

Bug still persists, I'm in safe mode, info version:

Versión: 6.0.1.1
Id. de compilación: 6.0.1-1
Subprocs. CPU: 8; SO: Linux 4.15; Repres. IU: predet.; VCL: gtk3; 
Configuración regional: es-ES (es_ES.utf8); Calc: group

System properties:
OS: Arch Linux x86_64
Host: All Series
Kernel: 4.15.3-1-ARCH
DE: Xfce
WM: Xfwm4
CPU: Intel i7-4790 (8) @ 4.000GHz
GPU: Intel Haswell Desktop
Comment 6 raal 2018-09-13 20:55:15 UTC
Works for me Version: 6.2.0.0.alpha0+
Build ID: 433fce6571d4b9121374047324a7d2d2722ac3e4
CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk3;
Comment 7 Xisco Faulí 2018-10-17 17:30:44 UTC
Dear Reporter,
Could you please try to reproduce it with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version.
Comment 8 QA Administrators 2019-05-08 17:31:10 UTC Comment hidden (obsolete)
Comment 9 QA Administrators 2019-06-08 03:05:54 UTC
Dear alexis6307,

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