Bug 801708 - [abrt] openoffice.org-brand-1:3.3.0-20.8.fc14: X11SalData::XIOErrorHdl killed by signal 6 (SIGABRT)
Summary: [abrt] openoffice.org-brand-1:3.3.0-20.8.fc14: X11SalData::XIOErrorHdl killed...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Orphan Owner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:41402cf9640e65d6859b10eb6e9...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-09 08:44 UTC by gjf
Modified: 2012-03-09 10:42 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-03-09 10:42:35 UTC
Type: ---
Embargoed:

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

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
Note You need to log in before you can comment on or make changes to this bug.