Bug 126038 - Old Pivot table crashes - new tables can not create
Summary: Old Pivot table crashes - new tables can not create
Status: RESOLVED DUPLICATE of bug 125808
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.2.4.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-21 12:41 UTC by Ferry Toth
Modified: 2019-06-24 09:02 UTC (History)
1 user (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 Ferry Toth 2019-06-21 12:41:03 UTC
With LibO 6.2.4.2 refreshing one of my 10 year old pivot tables results in a crash (both Windows and Linux)

We found the issue not happening in 6.2.3.2.

This happens with a pivot table created from a data source, in our case a table from postgresql.

Trying to create a new pivot table from a psql data source shows there are no columns to select from.

Creating a pivot table from a selection of cells in a spreadsheet seems to work.

This can be easily reproduced as LibO comes with a bibliography database. Trying to create a pivot table from bibliography shows also no columns to select from.

As a long time LibO user I am noting certain areas repeatedly to regress:
* file open / print dialog boxes
* pdf import /export
* document signing
* postgres (native interface)
* pivot tables.

And each time the irritation causes almost an heart attack of frustration.

May be we could prevent this by making sure patches in these areas received real world testing prior to incorporating into the release?
Comment 1 Julien Nabet 2019-06-21 13:58:22 UTC
It should be fixed in 6.2.5 (it should be released first week of July, see https://wiki.documentfoundation.org/ReleasePlan/6.2).

Meanwhile, you can revert to 6.2.3 to avoid some heart attack of frustration.

If you still reproduce this with future 6.2.5, don't hesitate to reopen this tracker.

*** This bug has been marked as a duplicate of bug 125808 ***
Comment 2 Ferry Toth 2019-06-24 08:25:50 UTC
Unfortunately reverting to 6.2.3 is not so easy, as 6.2.4 is installed during regular (K)ubuntu updates.

For others in the same situation:

Downloading from www.libreoffice.org: Fresh == 6.2.4. Still == 6.1.6.

Still has the added bonus that when on Kubuntu and Intel GPU, OpenGL is used for rendering by default, but that results in unreadable screen. And the only way to fix is start from the command line in safe mode :-(
Comment 3 Julien Nabet 2019-06-24 08:31:45 UTC
(In reply to Ferry Toth from comment #2)
> Unfortunately reverting to 6.2.3 is not so easy, as 6.2.4 is installed
> during regular (K)ubuntu updates.
> 
You may find some help here:
https://askubuntu.com/questions/138284/how-to-downgrade-a-package-via-apt-get
(I didn't test this).

> For others in the same situation:
> 
> Downloading from www.libreoffice.org: Fresh == 6.2.4. Still == 6.1.6.
> 
> Still has the added bonus that when on Kubuntu and Intel GPU, OpenGL is used
> for rendering by default, but that results in unreadable screen. And the
> only way to fix is start from the command line in safe mode :-(
This link may help:
https://wiki.documentfoundation.org/QA/FirstSteps#Graphics-related_issues_.28OpenGL.29
Comment 4 Ferry Toth 2019-06-24 09:02:48 UTC
Ah yes, 6.2.4.2 comes from the repo disco-updates, while disco still contains 6.2.2. So we cna downgrade to 6.2.2.

The best way is to use aptitude, because there is a whole family of packages to downgrade and aptitude does a better job of resolving the dependencies. It will forget to downgrade libreoffice-common though, so you need to do that separately. 

And then pin 6.2.2 packages in Synaptic to prevent further updates for the time being.

Thanks!