Bug 132443 - Background of the Field headers of the Table Controls are white instead of grey
Summary: Background of the Field headers of the Table Controls are white instead of grey
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
6.4.3.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-04-26 20:14 UTC by Rob Westein
Modified: 2020-12-09 03:40 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:
Regression By:


Attachments
screenshots 6.4.3.2 and 6.3.5.2 both installed on Mint 19.3 (53.37 KB, application/vnd.oasis.opendocument.text)
2020-04-26 20:17 UTC, Rob Westein
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Rob Westein 2020-04-26 20:14:52 UTC
Description:
Backgroundcolor of the Field headers of the Table Controls are white instead of grey.

Seen it in version 6.4.3.2 but its working fine in 6.3.5.2
Seen in Ubuntu 18.04 and Mint 19.3 with fresh installed 6.4.3.2


Steps to Reproduce:
Open a form in Design or View mode

Actual Results:
see differences in form (see attached document)

Expected Results:
see differences in form (see attached document)


Reproducible: Always


User Profile Reset: Yes



Additional Info:
-
Comment 1 Rob Westein 2020-04-26 20:17:09 UTC
Created attachment 159971 [details]
screenshots 6.4.3.2 and 6.3.5.2 both installed on Mint 19.3

difference of versions...
Comment 2 Alex Thurgood 2020-05-07 07:15:42 UTC
@Rob:

No repro for me with

Version : 6.4.3.2
Build ID : 747b5d0ebf89f41c860ec2a39efd7cb15b54f2d8
Threads CPU : 8; OS : Mac OS X 10.15.4; UI Render : par défaut; VCL: osx; 
Locale : fr-FR (fr_FR.UTF-8); Langue IHM : fr-FR
Calc: threaded


Is this related to the PPA, or Snap, that you are using ? 
Default LO on Ubuntu 18.04 and Mint 19.3 is not LO64x, so I'm assuming you've installed the version from some other source.
Comment 3 Rob Westein 2020-05-08 05:57:15 UTC
On Ubuntu 18.04 I installed it via the PPA. Due to some other issues I will remove this PPA installation.

The version that works on Mint (6.3) was installed via DEB.
4.6 was installed via SNAP / Ubuntu Software...

So you suggest to not use SNAP or PPA?
Comment 4 QA Administrators 2020-05-09 03:47:08 UTC Comment hidden (obsolete)
Comment 5 Rob Westein 2020-05-10 07:48:07 UTC
also seen this problem with LO version 7.
In Windows 10 it looks OK.
Comment 6 Alex Thurgood 2020-05-10 16:48:46 UTC
(In reply to Rob Westein from comment #3)
> On Ubuntu 18.04 I installed it via the PPA. Due to some other issues I will
> remove this PPA installation.
> 
> The version that works on Mint (6.3) was installed via DEB.
> 4.6 was installed via SNAP / Ubuntu Software...
> 
> So you suggest to not use SNAP or PPA?

No, but they often come with their own additionnel problems, which are not necessarily introduced by the LO development team.
Comment 7 Xisco Faulí 2020-05-11 10:44:55 UTC
Does it happen if you launch LibreOffice from commandline with  SAL_USE_VCLPLUGIN=gen  ?
Comment 8 QA Administrators 2020-11-08 04:19:09 UTC Comment hidden (obsolete)
Comment 9 QA Administrators 2020-12-09 03:40:22 UTC
Dear Rob Westein,

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