ooqstart crashed with SIGSEGV in g_main_context_default()

Bug #158746 reported by Aurel Branzeanu
8
Affects Status Importance Assigned to Milestone
openoffice.org (Ubuntu)
Invalid
Undecided
Chris Cheney

Bug Description

Binary package hint: openoffice.org

I was trying to open an .xls file

ProblemType: Crash
Architecture: i386
Date: Tue Oct 30 18:09:48 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/lib/openoffice/program/ooqstart
NonfreeKernelModules: fglrx
Package: openoffice.org-core 1:2.3.0-1ubuntu5.1
PackageArchitecture: i386
ProcCmdline: /usr/lib/openoffice/program/ooqstart -calc /home/thunder/.fr-PdTPIR/PriceDoxy\ 30\ October\ 2007.xls
ProcCwd: /home/thunder
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: openoffice.org
Stacktrace:
 #0 0xb7e92d70 in g_main_context_default () from /usr/lib/libglib-2.0.so.0
 #1 0x0804d79f in main ()
StacktraceTop:
 g_main_context_default () from /usr/lib/libglib-2.0.so.0
 main ()
ThreadStacktrace:
 .
 Thread 1 (process 7821):
 #0 0xb7e92d70 in g_main_context_default () from /usr/lib/libglib-2.0.so.0
 #1 0x0804d79f in main ()
Title: ooqstart crashed with SIGSEGV in g_main_context_default()
Uname: Linux thunder-mobile 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev root scanner video

Revision history for this message
Aurel Branzeanu (thunder-riscom) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:main ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Chris Cheney (ccheney) wrote :

Is this problem reproducible and if so can you attach the xls file that causes the problem?

Thanks,

Chris Cheney

Changed in openoffice.org:
assignee: nobody → ccheney
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) 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:
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.