Bug 664469

Summary: [abrt] BasicManager::GetGlobalUNOConstant killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Horst H. von Brand <vonbrand>
Component: libreofficeAssignee: Caolan McNamara <caolanm>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: caolanm, dtardon, ltinkl
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:49c0f36f7b79978db14c92971853b61e88c53084
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-01-13 11:27:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Horst H. von Brand 2010-12-20 14:21:18 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/libreoffice/program/soffice.bin -quickstart -nologo -nodefault
component: libreoffice
executable: /usr/lib64/libreoffice/program/soffice.bin
kernel: 2.6.37-0.rc6.git0.1.fc15.x86_64
package: libreoffice-core-3.3.0.1-4.fc15
reason: Process /usr/lib64/libreoffice/program/soffice.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 15 (Rawhide)
time: 1292854564
uid: 500

comment
-----
The quickstarter (i.e., the icon on the Gnome panel) was up.

It crashed with oowriter, afterwards the same commando worked fine (and did show the splashscreen).

How to reproduce
-----
1. Booted the machine
2. "oowriter SomeFile.docx" in a gnome-terminal
3.
Comment 1 Horst H. von Brand 2010-12-20 14:21:21 UTC 
Created attachment 469770 [details]
File: backtrace
Comment 2 Caolan McNamara 2010-12-20 14:30:42 UTC 
Can you attach the .docx which may have triggered this initially.
Comment 3 Horst H. von Brand 2010-12-28 19:43:52 UTC 
Sorry, can't. The file had (somewhat) confidential contents. Besides, it isn't easy to find out what crashes (seems to happen just the first time after boot that I use OOo).
Comment 4 Caolan McNamara 2011-01-13 11:27:41 UTC 
Without symbols I can't tell if the pointer to a basicmanager is itself invalid or if the basicmanager is corrupt :-(

My guess is that this is possibly related to the auto-migration of the user's basic libraries in the profile dirs.