Bug 589431 - [abrt] crash in IA__gdk_xid_table_lookup_for_display
[abrt] crash in IA__gdk_xid_table_lookup_for_display
Product: Fedora
Classification: Fedora
Component: openoffice.org (Show other bugs)
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Caolan McNamara
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-05-06 02:47 EDT by Manoj Kumar Suyal
Modified: 2010-05-14 05:58 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-05-14 05:58:47 EDT
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 (66.46 KB, text/plain)
2010-05-06 02:47 EDT, Manoj Kumar Suyal
no flags Details

External Trackers
Tracker ID Priority Status Summary Last Updated
Launchpad 158960 None None None Never
Red Hat Bugzilla 588107 None None None Never

  None (edit)
Description Manoj Kumar Suyal 2010-05-06 02:47:28 EDT
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/lib/openoffice.org3/program/scalc.bin -calc file:///home/manoj/Desktop/ATTENDANCE%20for%20the%20month%20of%20april%202010.xls
component: openoffice.org
crash_function: IA__gdk_display_get_type
executable: /usr/lib/openoffice.org3/program/scalc.bin
global_uuid: 6a8baae726399eee6f735bea71568c6801ca7f3e
package: openoffice.org-calc-1:3.1.1-19.28.fc12
rating: 4
reason: Process /usr/lib/openoffice.org3/program/scalc.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
Comment 1 Manoj Kumar Suyal 2010-05-06 02:47:33 EDT
Created attachment 411841 [details]
File: backtrace
Comment 2 David Tardon 2010-05-06 03:43:36 EDT
Did that crash happen just after you started the app or after some action of yours (like connecting a new monitor)? Is it reproducible?
Comment 3 David Tardon 2010-05-14 05:58:47 EDT
Feel free to reopen if you can tell us how to reproduce this.

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