Bug 801708

Summary: [abrt] openoffice.org-brand-1:3.3.0-20.8.fc14: X11SalData::XIOErrorHdl killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: gjf <goujunfeng>
Component: openoffice.orgAssignee: Orphan Owner <extras-orphan>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: caolanm, extras-orphan
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:41402cf9640e65d6859b10eb6e9db82c3e3a39b8
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-09 10:42:35 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 gjf 2012-03-09 08:44:26 UTC
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 55346 bytes
cmdline: /usr/lib/openoffice.org3/program/soffice.bin -quickstart -nologo -nodefault
component: openoffice.org
Attached file: coredump, 40263680 bytes
crash_function: OUString
executable: /usr/lib/openoffice.org3/program/soffice.bin
kernel: 2.6.35.6-45.fc14.i686
package: openoffice.org-brand-1:3.3.0-20.8.fc14
rating: 4
reason: Process /usr/lib/openoffice.org3/program/soffice.bin was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1321481576
uid: 500

How to reproduce
-----
1.When I use computer after "hibernate".
2.
3.

Comment 1 gjf 2012-03-09 08:44:42 UTC
Created attachment 568856 [details]
File: backtrace

Comment 2 gjf 2012-03-09 08:47:22 UTC
Package: openoffice.org-brand-1:3.3.0-9.3.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.when I use computer  after "hibernate".
2.
3.

Comment 3 Caolan McNamara 2012-03-09 10:42:35 UTC
crash resulting from a X11SalData::XIOErrorHdl, i.e. connection to X server died. IIRC we fixed the actual "crash" in later release, but that's only cosmetic as no app can survive loss of connection in any particularly useful way