unopkg.bin crashed with SIGSEGV in start_thread()

Bug #268065 reported by lishuangxing
16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openoffice.org (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: openoffice.org

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/openoffice/program/unopkg.bin
NonfreeKernelModules: nvidia
Package: openoffice.org-core 1:2.4.1-8ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/lib/openoffice/program/unopkg.bin add --shared /usr/lib/openoffice/program/mailmerge.py -env:UserInstallation=file:////tmp/tmp.EACMbR9945 -env:UNO_JAVA_JFW_INSTALL_DATA=$ORIGIN/../share/config/javasettingsunopkginstall.xml -env:JFW_PLUGIN_DO_NOT_CHECK_ACCESSIBILITY=1
ProcEnviron:
 PATH=/usr/lib/openoffice/program:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
 LANG=zh_CN.GB2312
 SHELL=/bin/bash
Signal: 11
SourcePackage: openoffice.org
StacktraceTop:
 ?? () from /usr/lib/openoffice/program/libuno_cppu.so.3
 ?? () from /usr/lib/openoffice/program/libuno_cppu.so.3
 ?? () from /usr/lib/openoffice/program/libuno_cppu.so.3
 ?? () from /usr/lib/openoffice/program/libuno_sal.so.3
 start_thread () from /lib/tls/i686/cmov/libpthread.so.0
Title: unopkg.bin crashed with SIGSEGV in start_thread()
Uname: Linux 2.6.27-2-generic i686
UserGroups:

Revision history for this message
lishuangxing (lishuangxing06) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? () from /usr/lib/openoffice/program/libuno_cppu.so.3
?? () from /usr/lib/openoffice/program/libuno_cppu.so.3
?? () from /usr/lib/openoffice/program/libuno_cppu.so.3
?? () from /usr/lib/openoffice/program/libuno_sal.so.3
start_thread () from /lib/tls/i686/cmov/libpthread.so.0

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Andreas Moog (ampelbein) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

Changed in openoffice.org:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Chris Cheney (ccheney) wrote :

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!

Changed in openoffice.org:
importance: Medium → Undecided
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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