[ooo-build] .xlsx filetype does not save charts

[mlissner]

Binary package hint: openoffice.org

STR:
 - create a new document
 - spend a few hours making charts in it
 - save it as .xlsx
 - reopen it
 - note that all the charts are gone
 - try desperately to recover them
 - fail
 - curse (loudly)

The above is essentially what I just did, and now I have to recreate all of the charts in my document. I have no idea if this happens every time or not, but it's a huge data loss, and very frustrating.

There is a warning about things not being saved unless ods format is used, but if charts on the whole aren't saved at all, that's BAD, BAD, BAD. Is there something we can do to prioritize fixing this?
---
Architecture: i386
DistroRelease: Ubuntu 10.04
NonfreeKernelModules: fglrx
Package: openoffice.org-core 1:3.2.0-7ubuntu4
PackageArchitecture: i386
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Tags: lucid
Uname: Linux 2.6.32-22-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[mlissner (mlissner-michaeljaylissner)]

I meant to mention, I filed this bug in the OOo bug tracker originally, and after being lectured by them, I've been informed that this is likely an Ubuntu bug. The original bug, filed as "RESOLVED, INVALID," is here, fwiw: http://www.openoffice.org/issues/show_bug.cgi?id=110124

[Chris Cheney (ccheney)]

[This is an automatic notification.]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:

apport-collect 539770

This will help us to find and resolve the problem. Bear in mind that you may need to install the python-launchpadlib package from the universe repository. Additionally, when prompted to give apport-collect permissions for Launchpad you will need to give it at least the ability to "Change Non-Private" data as it will be adding information to your bug report. Thanks in advance!

When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[mlissner (mlissner-michaeljaylissner)]

I ran the above code, but got the error:
% apport-collect 539770
The authorization page:
   (https://edge.launchpad.net/+authorize-token?oauth_token=7dX92fGHdNbhPsFqNxwp&allow_permission=WRITE_PRIVATE)
should be opening in your browser. After you have authorized
this program to access Launchpad on your behalf you should come
back here and press <Enter> to finish the authentication process.

Package openoffice.org not installed and no hook available, ignoring

[Chris Cheney (ccheney)]

Try:

apport-collect -p openoffice.org-core 539770

Thanks,

Chris

[mlissner (mlissner-michaeljaylissner)]

apport information

[Chris Cheney (ccheney)]

Upstream reminded me normal OOo can' t write xlsx at all so this is an ooo-build issue.

[Ben Andersen (ben72)]

Not sure if this is the same issue. Opening the attached xlsx-file using Ubuntu 10.04 or 10.10, the images are in the wrong places, it's a mess. This worked in Ubuntu 9.10 where they were nicely layed out. My wife was not happy after the recent upgrade to 10.04 when she found out she couldn't use the file to do her order due tonight.

Luckily I could load it in 9.10 live and save as a ods-file and she could then use it on Ubuntu 10.04..

But I'm reporting it here because it doesn't work in 10.10 either so maybe it's something that needs looking into.

[penalvch (penalvch)]

mlissner, could you please attach a .ods document that when saved as .xlsx demonstrates this problem? Does LibreOffice work for you?

[mlissner (mlissner-michaeljaylissner)]

Sorry, I can't. The docs that had this issue are long gone. Not sure if I can reproduce it.

[penalvch (penalvch)]

mlissner, we are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!