soffice.bin crashed with SIGABRT in JNI_interface_type_info()

Bug #788267 reported by penalvch
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
libreoffice (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: libreoffice

1) lsb_release -rd
Description: Ubuntu 11.04
Release: 11.04

2) apt-cache policy libreoffice-calc
libreoffice-calc:
  Installed: 1:3.3.2-1ubuntu5
  Candidate: 1:3.3.2-1ubuntu5
  Version table:
 *** 1:3.3.2-1ubuntu5 0
        500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages
        100 /var/lib/dpkg/status
     1:3.3.2-1ubuntu4 0
        500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages

3) What is expected to happen in LibreOffice Calc via the Terminal:

cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/586599/+attachment/1407325/+files/ooCPUbug.ods && localc -nologo ooCPUbug.ods

Tools -> Macros -> Run Macro -> under Library click ooCPUbug.ods -> Standard -> Module1 -> under Macro name click MYFUNC -> RUN button wait a minute or two then close the file and it does not crash.

4) What happens instead is it crashed.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: libreoffice-core 1:3.3.2-1ubuntu5
ProcVersionSignature: Ubuntu 2.6.38-9.43-generic 2.6.38.4
Uname: Linux 2.6.38-9-generic i686
NonfreeKernelModules: fglrx
Architecture: i386
Date: Wed May 25 14:10:12 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: /usr/lib/libreoffice/program/soffice.bin -calc -nologo ooCPUbug.ods
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: libreoffice
StacktraceTop:
 JNI_interface_type_info () from /usr/lib/ure/lib/libjava_uno.so
 os::abort(bool) () from /usr/lib/jvm/java-6-openjdk/jre/lib/i386/client/libjvm.so
 VMError::report_and_die() () from /usr/lib/jvm/java-6-openjdk/jre/lib/i386/client/libjvm.so
 JVM_handle_linux_signal () from /usr/lib/jvm/java-6-openjdk/jre/lib/i386/client/libjvm.so
 signalHandler(int, siginfo*, void*) () from /usr/lib/jvm/java-6-openjdk/jre/lib/i386/client/libjvm.so
Title: soffice.bin crashed with SIGABRT in JNI_interface_type_info()
UpgradeStatus: Upgraded to natty on 2011-05-14 (11 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

Revision history for this message
penalvch (penalvch) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 JNI_interface_type_info () from /usr/lib/ure/lib/libjava_uno.so
 os::abort(bool) () from /usr/lib/jvm/java-6-openjdk/jre/lib/i386/client/libjvm.so
 VMError::report_and_die() () from /usr/lib/jvm/java-6-openjdk/jre/lib/i386/client/libjvm.so
 JVM_handle_linux_signal () from /usr/lib/jvm/java-6-openjdk/jre/lib/i386/client/libjvm.so
 signalHandler(int, siginfo*, void*) () from /usr/lib/jvm/java-6-openjdk/jre/lib/i386/client/libjvm.so

Changed in libreoffice (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
penalvch (penalvch) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - Precise Pangolin.

This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please do steps 1 and 2 of the SRU Procedure [1] to bring the need to a developer's attention.

[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

lsb_release -rd
Description: Ubuntu precise (development branch)
Release: 12.04

apt-cache policy libreoffice-writer
libreoffice-writer:
  Installed: 1:3.5.1-1ubuntu1
  Candidate: 1:3.5.1-1ubuntu1
  Version table:
 *** 1:3.5.1-1ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
        100 /var/lib/dpkg/status

visibility: private → public
Changed in libreoffice (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.