Bug 98282

Summary: Database table not editable in writer/calc - additional printing problem
Product: LibreOffice Reporter: csbugs <bugs>
Component: UIAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED INSUFFICIENTDATA    
Severity: normal CC: bugs, ilmari.lauhakangas
Priority: medium    
Version: 5.0.4.2 release   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
Crash report or crash signature: Regression By:
Attachments: Big column titles in preview and print

Description csbugs 2016-02-29 19:27:27 UTC
Created attachment 123087 [details]
Big column titles in preview  and print

SuSE just sent LO 5.0.4.2 to me via openSUSE-13.2 regular updates.

I have a writer doc showing the contents of an external PostgreSQL table. This database table is not editable any more - i.e. I cannot select font or font size.

In addition, if I try to print my existing writer document, the column titles are shown in amazing huge letters - this disappears when "printing to file", so I have to attach a screenshot of the printing dialog which has the problem even in the preview - besides a layout problem when pulled larger.

If I choose to add a new table control without using the wizard, no columns appear in the table after connecting the control to a database table, though they do when using the wizard.

The wizard has the problem that it has no choice for the data source, it simply uses whatever database I chose last time. So I have to use it twice when changing data source: first add a table with the wizard which is connected to the last data source. Then editing the data source in the control's properties, only to  remove it afterwards. Then I can use the wizard to generate a table connected to the right data source and with columns.


Everything tested with fresh user profiles and happens both in Writer and Calc. Possibly the same bug as reported in bug 96808.
Comment 1 csbugs 2016-02-29 20:39:26 UTC
Problems were not present in openSuSE's version of LO 4.4.5.2, persists in (openSUSE's version of) LO 5.0.5.2.

In openSUSE's current version of 5.1.0.3 for openSUSE 13.2 which is labelled 5.1.0.3-390.1 some of the problems seem to be gone: the per column settings are accessible again. But the the font settings problem and the printing issue persists.

Regards
Comment 2 Buovjaga 2016-03-17 11:48:01 UTC
Does this only happen with your external DB or also with LibreOffice's own embedded DB? I'm just thinking it will be very hard for QA to test..

Set to NEEDINFO.
Change back to UNCONFIRMED after you have provided the information.
Comment 3 Alex Thurgood 2016-06-03 10:21:43 UTC
@csbugs : we need a sample ODB file and, if I have understood the report correctly, a copy of the Writer file you are using as your report document. Also please indicate which font is being used in the Writer document (there are known issues with Libertine, for example)
Comment 4 csbugs 2016-06-03 12:02:38 UTC
Hi, thanks for caring.

I'll see whether I can put together a testcase odb and reproduce this thing, but as the real thing is a bit more complicated - like most real life things :) - I'm not sure where to find the necessary time. So it may take a  bit...
Comment 5 QA Administrators 2016-12-07 12:58:32 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2017-01-31 00:25:12 UTC
Dear Bug Submitter,

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-20170131