Bug 773066

Summary: [abrt] openoffice.org-brand-1:3.3.0-20.8.fc14: DNDEventDispatcher::fireDragExitEvent: Process /usr/lib/openoffice.org3/program/soffice.bin was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Dirk Hoffmann <hoffmann>
Component: openoffice.orgAssignee: Orphan Owner <extras-orphan>
Status: CLOSED INSUFFICIENT_DATA 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:7dedc4453d5198fea5194c6098226e766b1a0e7a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-27 09:39:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Dirk Hoffmann 2012-01-10 20:12:59 UTC 
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 43111 bytes
cmdline: /usr/lib/openoffice.org3/program/soffice.bin
component: openoffice.org
Attached file: coredump, 195780608 bytes
crash_function: Window::IsInputEnabled
executable: /usr/lib/openoffice.org3/program/soffice.bin
kernel: 2.6.35.14-106.fc14.i686.PAE
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 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1326225418
uid: 500

How to reproduce
-----
1. Edit a OOo Calc file
2. Close it
3. Crash
Comment 1 Dirk Hoffmann 2012-01-10 20:13:03 UTC 
Created attachment 551930 [details]
File: backtrace
Comment 2 Caolan McNamara 2012-01-10 20:49:57 UTC 
my experience is that calc doesn't crash on every edit :-) Are you able to reproduce this ? The backtrace suggests a drag and drop related problem, does that ring a bell ?
Comment 3 Eike Rathke 2012-01-10 22:08:23 UTC 
No bell rang, but that's OOo 3.3 on F-14, isn't that EOL anyway?
Comment 4 Dirk Hoffmann 2012-01-11 18:36:44 UTC 
(In reply to comment #2)
> my experience is that calc doesn't crash on every edit :-) 

I confirm. However it crashes too often when using it every day.

> Are you able to
> reproduce this ? The backtrace suggests a drag and drop related problem, does
> that ring a bell ?

I cannot reproduce it, and I did not have the impression that I dragged and dropped something. If the backtrace does not reveal an uninitialised variable or invalid pointer or somthing obvious, then I am afraid, I cannot be of more help.
Comment 5 Dirk Hoffmann 2012-01-11 18:38:52 UTC 
(In reply to comment #3)
> No bell rang, but that's OOo 3.3 on F-14, isn't that EOL anyway?

I upgraded from initial fc13 to fc14 with preupgrade. 

However, there are several tickets open that fc14 to fc15 or fc14 to fc16 (and even fc15 to fc16) does not work reliably. Therefore I will have to stay with fc14 until I find time to make a complete reinstall from scratch.

I do not see how your comment could be helpful for anybody.
Comment 6 Caolan McNamara 2012-03-27 09:39:39 UTC 
re "EOL" and "how [that] could be helpful". The thing is that once a release is EOL we're not even able to provide updates for it anymore, so if we were able to identify the bug we could only provide an update for non-EOL fedora releases.

In this case we can't reproduce it in a supported release :-(, I doubt the underlying problem is actually fixed, just can't reproduce it.