Bug 801708 - [abrt] openoffice.org-brand-1:3.3.0-20.8.fc14: X11SalData::XIOErrorHdl killed by signal 6 (SIGABRT)
[abrt] openoffice.org-brand-1:3.3.0-20.8.fc14: X11SalData::XIOErrorHdl killed...
Product: Fedora
Classification: Fedora
Component: openoffice.org (Show other bugs)
i686 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Orphan Owner
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-03-09 03:44 EST by gjf
Modified: 2012-03-09 05:42 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-03-09 05:42:35 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (54.05 KB, text/plain)
2012-03-09 03:44 EST, gjf
no flags Details

  None (edit)
Description gjf 2012-03-09 03:44:26 EST
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
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".
Comment 1 gjf 2012-03-09 03:44:42 EST
Created attachment 568856 [details]
File: backtrace
Comment 2 gjf 2012-03-09 03:47:22 EST
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".
Comment 3 Caolan McNamara 2012-03-09 05:42:35 EST
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

Note You need to log in before you can comment on or make changes to this bug.