Bug 128604 - Base UI - Incomplete border line in table design panel - KDE/QT
Summary: Base UI - Incomplete border line in table design panel - KDE/QT
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
6.2.8.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-11-05 08:57 UTC by Nukool Chompuparn
Modified: 2020-01-06 16:05 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
For normal adding field one by one, it is normal. (69.19 KB, image/jpeg)
2019-11-05 08:58 UTC, Nukool Chompuparn
Details
But deleting field, the border line is partly missing. (62.57 KB, image/jpeg)
2019-11-05 09:00 UTC, Nukool Chompuparn
Details
Sometimes, they are gone. (18.30 KB, image/jpeg)
2019-11-05 09:01 UTC, Nukool Chompuparn
Details
SAL_USE_VCLPLUGIN=gen (21.03 KB, image/jpeg)
2019-12-03 07:45 UTC, Nukool Chompuparn
Details
6.3.3.2.-0+ & gtk3 (35.68 KB, image/png)
2019-12-26 09:09 UTC, Nukool Chompuparn
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nukool Chompuparn 2019-11-05 08:57:32 UTC
Description:
The broder line of blank triangle in front of each field is missing. Please see images in next comments. 

Steps to Reproduce:
1.Open LO Base
2.Select > Create table in design view
3.

Actual Results:
1. For normal adding fields, such border lines are ok.
2. But delete fields, such border lines deviated.

Expected Results:
It should not change.


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 Nukool Chompuparn 2019-11-05 08:58:52 UTC
Created attachment 155515 [details]
For normal adding field one by one, it is normal.
Comment 2 Nukool Chompuparn 2019-11-05 09:00:37 UTC
Created attachment 155516 [details]
But deleting field, the border line is partly missing.
Comment 3 Nukool Chompuparn 2019-11-05 09:01:19 UTC
Created attachment 155517 [details]
Sometimes, they are gone.
Comment 4 Alex Thurgood 2019-11-06 10:08:04 UTC
Looks like a GTK issue to me.

No repro on macOS 10.15 for example with 

Version: 6.3.1.2
Build ID: b79626edf0065ac373bd1df5c28bd630b4424273
Threads CPU : 4; OS : Mac OS X 10.15.1; UI Render : par défaut; VCL: osx; 
Locale : fr-FR (fr_FR.UTF-8); Langue IHM : fr-FR
Calc: threaded
Comment 5 Alex Thurgood 2019-11-13 07:09:34 UTC
@Nukool : please provide:

- Linux distribution and version
- whether or not you are using the Linux distrib-provided version of LO
- which VCL backend is being used (see the About dialog in LO)
Comment 6 Nukool Chompuparn 2019-11-14 04:01:20 UTC
(In reply to Alex Thurgood from comment #5)
> @Nukool : please provide:
> 
> - Linux distribution and version
> - whether or not you are using the Linux distrib-provided version of LO
> - which VCL backend is being used (see the About dialog in LO)


I do not use Windows OS.

OS: Fedora 31 Workstation KDE Plasma Desktop from Spins https://spins.fedoraproject.org/en/kde/

Present Linux kernel : 5.3.11

I do not use LO by default from distribution, but I use the stable version 6.2.8.2-2 for it is the best for my needs.( I use the BASIC Editor, and 6.2.8.2-2 is the latest version that the characters is not black when edit.)


Version: 6.2.8.2
Build ID: f82ddfca21ebc1e222a662a32b25c0c9d20169ee
CPU threads: 4; OS: Linux 5.3; UI render: default; VCL: kde5; 
Locale: en-US (en_US.UTF-8); UI-Language: en-US
Calc: threaded

Thank you so much in advance.
Comment 7 Alex Thurgood 2019-11-26 09:04:15 UTC
In all likelihood then a KDE VCL issue.

If you start LO from a terminal with 

SAL_USE_VCLPLUGIN=gen

does the problem go away ?
Comment 8 Nukool Chompuparn 2019-12-03 07:45:04 UTC
(In reply to Alex Thurgood from comment #7)
> In all likelihood then a KDE VCL issue.
> 
> If you start LO from a terminal with 
> 
> SAL_USE_VCLPLUGIN=gen
> 
> does the problem go away ?

There was nothing happened. Please see next attachment.
Comment 9 Nukool Chompuparn 2019-12-03 07:45:28 UTC
Created attachment 156260 [details]
SAL_USE_VCLPLUGIN=gen
Comment 10 Alex Thurgood 2019-12-03 10:29:16 UTC
You also need to start LibreOffice from the command line when you use SAL_USE_VCLPLUGIN, e.g.:

SAL_USE_VCLPLUGIN=gen /path/to/soffice

It might also be required to at least have the libreoffice GTK3 package installed as well.
Comment 11 Nukool Chompuparn 2019-12-05 03:24:10 UTC
(In reply to Alex Thurgood from comment #10)
> You also need to start LibreOffice from the command line when you use
> SAL_USE_VCLPLUGIN, e.g.:
> 
> SAL_USE_VCLPLUGIN=gen /path/to/soffice
> 
> It might also be required to at least have the libreoffice GTK3 package
> installed as well.

I am using Fedora 31 Workstation KDE Desktop from Spins.
Comment 12 QA Administrators 2019-12-05 04:27:23 UTC Comment hidden (obsolete)
Comment 13 Nukool Chompuparn 2019-12-26 09:08:15 UTC
Yes, it needs gtk3.
I have installed Fedora 31 Workstation with GNOME and bundled LibreOffice 6.3.3.2.0+, this version is gtk3.
The border lines are perfect.
Please see attached image.
Comment 14 Nukool Chompuparn 2019-12-26 09:09:23 UTC
Created attachment 156781 [details]
6.3.3.2.-0+ & gtk3
Comment 15 Alex Thurgood 2019-12-27 08:07:48 UTC
I would be inclined to mark this as a packaging bug for Fedora, ie. NOTOURBUG

@Caolan : ideas ?
Comment 16 Caolán McNamara 2020-01-06 09:40:54 UTC
"I would be inclined to mark this as a packaging bug for Fedora, ie. NOTOURBUG"

I don't see why its a "packaging bug" it looks very like its a bug in our KDE vclplug. The gtk3 one is the default in stock Fedora, but this is the KDE spin.
Comment 17 Robert Großkopf 2020-01-06 16:05:59 UTC
Could confirm the buggy behavior for
Version: 6.2.6.2
CPU-Threads: 6; BS: Linux 4.12; UI-Render: Standard; VCL: kde5; 
(OpenSUSE 15.1 64bit rpm Linux)

Couldn't reproduce it with
Version: 6.3.4.2
CPU-Threads: 6; BS: Linux 4.12; UI-Render: Standard; VCL: kde5; 
(OpenSUSE 15.1 64bit rpm Linux)

Last Version the bug could reproduced here is LO 6.3.0.4
Since LO 6.3.1.2 the bug has gone.
All tested on the same system OpenSUSE 15.1

I would prefer to set this one on Worksforme, because we don't know what has ben changed the behavior.