Launchpad has imported 10 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=84315.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2014-09-25T08:31:29+00:00 Rico Tzschichholz wrote:
Created attachment 106836
Example hsqldb database
Numeric are not correctly display and either an empty field or 0 is
shown.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1373928/comments/0
On 2014-09-25T08:31:54+00:00 Rico Tzschichholz wrote:
Created attachment 106837
Displayed with 4.2.6.3
Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1373928/comments/1
On 2014-09-25T08:32:13+00:00 Rico Tzschichholz wrote:
Created attachment 106838
Displayed with 4.3.2.2
Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1373928/comments/2
On 2014-09-25T08:34:00+00:00 Rico Tzschichholz wrote:
As reported to me this was working as expected in 4.3.1.2 as well.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1373928/comments/3
On 2014-09-25T09:16:46+00:00 Björn Michaelsen wrote:
UNCONFIRMED-NEW: was confirmed by an independent party.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1373928/comments/4
On 2014-09-25T09:22:11+00:00 Björn Michaelsen wrote:
Severity Critical unless this is a 4.3.0-4.3.2 regression.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1373928/comments/5
On 2014-09-25T11:23:20+00:00 Tim Passingham wrote:
I reported this to Rico this morning, assuming it was a new ubuntu
release problem. I was previously running 4.3.1.2 from the ubuntu ppa.
I was also running 4.3.2 development version direct from libreoffice to test
another issue, version:
Version: 4.3.2.0.0+ Build ID:
b2d54aa61607e477cb4b81f1a70e555ee3adb0af
TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:libreoffice-4-3, Time:
2014-08-20_23:12:37
This was OK, which is why I assumed it was an ubuntu release problem.
I am a little concerned. If this applies on all platforms, then no
databases at all will work with 4.3.2.2, with all that implies.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1373928/comments/6
On 2014-09-25T12:09:57+00:00 Tim Passingham wrote:
I have done a little more investigation.
First, on the libreoffice website 4.3.2.2 still seems to be a pre-
release, so I am a little surprised it was release to the ubuntu normal
release ppa.
Secondly, on Windows 64 bit I downloaded 4.3.2.2 from the LO website and
it is OK.
Thirdly, I thought I should download the linux deb 4.3.2.2 from the
libreoffice website. I did, and it works.
So after a very brief series of tests this appears to be an ubuntu
release problem, not a libreoffice problem. Please forgive me if I've
made an error in my checking somewhere, but this issue seemed so serious
for database users that I thought I should progress it as fast as
possible.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1373928/comments/7
On 2014-09-25T13:04:21+00:00 Björn Michaelsen wrote:
(In reply to comment #7)
First, on the libreoffice website 4.3.2.2 still seems to be a pre-release,
so I am a little surprised it was release to the ubuntu normal release ppa.
This PPA might contain the release candidate that is assumed to become the
final release even before it is declared so by the Document Foundation (e.g.
usually release candidate 2 for minor updates).
https://launchpad.net/~libreoffice/+archive/ubuntu/ppa
So nothing surprising there at all, if you read the PPA description.
Secondly, on Windows 64 bit I downloaded 4.3.2.2 from the LO website and it
is OK.
Thirdly, I thought I should download the linux deb 4.3.2.2 from the
libreoffice website. I did, and it works.
This is certainly interesting. Normally I would close the bug as NOTOURBUG here
then (because it would be a distro bug only). I have an idea about the reason
though, as I enabled mergedlibs on 4.3.2 and had to move some lib into it to
get rid of circular deps: dbtools -- which sounds like it could cause this
trouble.
Adding distro bug reference.
Reply at:
