Bugzilla – Bug 596324
[Milestone 5] Update to OpenOffice_org-calc-extensions-3.2.0.99.2-1.4.x86_64 fails
Last modified: 2010-04-15 14:12:07 UTC
zypper hangs at Installing: OpenOffice_org-calc-extensions-3.2.0.99.2-1.4 [18%] top shows "unopkg.bin" using 100% CPU strace shows write(1, "\n\nYour input was not correct. Pl"..., 58) = 58 read(0, "", 4096) = 0 write(1, "\n\nYour input was not correct. Pl"..., 58) = 58 read(0, "", 4096) = 0 ... After a couple of minutes, zypper terminates with terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Aborted
It appears similar with the issue reported: https://bugzilla.novell.com/show_bug.cgi?id=595550 Petr, I didn't reproduce this on SLED 11 by clean install/upgrade from 3.2.1beta1 to beta2. I tried to unregister the extensions in calc-extensions package and re-register them using: unopkg add -v --shared /usr/lib64/ooo3/share/extension/install/ConvertTextToNumber-1.3.2.oxt unopkg add -v --shared /usr/lib64/ooo3/share/extension/install/NLPSolver.oxt unopkg add -v --shared /usr/lib64/ooo3/share/extension/install/numbertext-0.7.1.oxt unopkg add -v --shared /usr/lib64/ooo3/share/extension/install/WatchWindow_1.1.2.oxt However it doesn't help to call out the license agreement, all of them are installed directly with normal verbose feedback. Please let me know if we need OpenSuse 11.3 to investigate the problem. Thank you!
Instead of getting an OpenSuse build, I downloaded the calc-extension from the opensuse 11.3 repo: http://download.opensuse.org/factory/repo/oss/suse/x86_64/OpenOffice_org-calc-extensions-3.2.0.99.2-1.4.x86_64.rpm Finally reproduced the problem, it happens on registering the extension: ConvertTextToNumber-1.3.2.oxt From my attemption, no problem was found for other 3 Calc extensions. In comparison with the OOo beta2 build I got, there's an extra <registration> tag added in the description.xml of the above version ConvertTextToNumber-1.3.2.oxt.
It looks like a duplicate of the bug #595550. I have seen that it repeatedly asked to confirm the license. It explains the 100% CPU usage, ... *** This bug has been marked as a duplicate of bug 595550 ***