Bug 568655 - [abrt] crash in ImpEditView::dragOver
Summary: [abrt] crash in ImpEditView::dragOver
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:5761784ad0fd2ccd34524100fd1...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-26 09:29 UTC by Justin Noah
Modified: 2010-03-23 23:36 UTC (History)
3 users (show)

Fixed In Version: openoffice.org-3.1.1-19.28.fc12
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-03-23 23:36:36 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (53.52 KB, text/plain)
2010-02-26 09:29 UTC, Justin Noah
no flags Details


Links
System ID Private Priority Status Summary Last Updated
OpenOffice.org 109713 0 None None None Never
OpenOffice.org 109743 0 None None None Never

Description Justin Noah 2010-02-26 09:29:24 UTC
abrt 1.0.7 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/lib/openoffice.org3/program/simpress.bin -impress file:///home/justin/Desktop/Project/PPT/Complete.odp
comment: I was working on homework, copying and pasting slides, text, and images. I don't know of anything specific that caused the crash. I believe I was pasting somthing at the time. Whether slide or text, not sure, but it wasn't an image, I know that.
component: openoffice.org
executable: /usr/lib/openoffice.org3/program/simpress.bin
kernel: 2.6.31.12-174.2.19.fc12.i686.PAE
package: openoffice.org-impress-1:3.1.1-19.26.fc12
rating: 4
reason: Process /usr/lib/openoffice.org3/program/simpress.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. Do anything in impress for a while and this will happen.
2. Specifically around copying data from slide to slide and copying slides
3.

Comment 1 Justin Noah 2010-02-26 09:29:26 UTC
Created attachment 396503 [details]
File: backtrace

Comment 2 Caolan McNamara 2010-02-26 09:59:20 UTC
I suspect you were dragging and dropping. Very difficult to do anything about this unless it can be reproduced in some predictable way.

Comment 3 Caolan McNamara 2010-02-26 14:28:12 UTC
I can't get it to crash with various dragging and drop efforts. Do you have a reproducible route to get a crash ?

Comment 4 Justin Noah 2010-02-26 17:33:06 UTC
(In reply to comment #3)
> I can't get it to crash with various dragging and drop efforts. Do you have a
> reproducible route to get a crash ?    

This bug was improperly moved to the drag and drop issue. As I had stated, the crash occurred from copying slides and/or slide objects. What I left out (sorry) was that it was from one project to another. Basically, I had one ODP open, and either a PPT or PPTX (that I really cannot remember) and was copying slides from the PPT(X) to the ODP. At which point it crashed, I literally hit Ctrl+V to paste.

---
The previous seems dumb I know, but I was basically adding a bunch of slides from several PPT and PPTX sources into one presentation.
---

I can't really give anything easily reproducible because I was doing that over and over, but it seemed to happen one time seemingly 'randomly'. After the crash I started to Ctr+A, Ctrl+C the data on the slide from the PPT(X) rather than right-click copying from the list view (default on the left) and then just pasting the data onto a new slide in the odp without any more crashes.

Comment 5 Caolan McNamara 2010-03-01 12:59:31 UTC
It definitely crashed in drag and drop code. Might not have been intentional, but that's where it happened. Got it to happen once here with the same crash

Comment 6 Justin Noah 2010-03-01 21:23:53 UTC
(In reply to comment #5)
> It definitely crashed in drag and drop code. Might not have been intentional,
> but that's where it happened. Got it to happen once here with the same crash    

That's really weird because I do know what dragging and dropping is and I sincerely do not recall using it at the time. Anyway, is there anything I can do as a user to help any further?

Comment 7 Caolan McNamara 2010-03-02 16:44:18 UTC
Plausible fix checked in and submitted upstream. Will be in >= 3.1.1-19.27 if there is another update for F-12

Comment 8 Justin Noah 2010-03-02 18:23:09 UTC
(In reply to comment #7)
> Plausible fix checked in and submitted upstream. Will be in >= 3.1.1-19.27 if
> there is another update for F-12    

Does this fix by chance fix the sluggishness of OOo Impress that is viewed after working in the application for a while? Or is that just some memory leak somewhere else? (Sorry for the noob question, just hoping OOo gets better overall).

Comment 9 Caolan McNamara 2010-03-02 19:53:37 UTC
This fix couldn't have any measurable impact on performance one way or another.

Comment 10 Fedora Update System 2010-03-03 08:49:59 UTC
openoffice.org-3.2.0-12.9.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/openoffice.org-3.2.0-12.9.fc13

Comment 11 Fedora Update System 2010-03-05 03:33:45 UTC
openoffice.org-3.2.0-12.9.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 12 Fedora Update System 2010-03-17 11:06:07 UTC
openoffice.org-3.1.1-19.28.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/openoffice.org-3.1.1-19.28.fc12

Comment 13 Fedora Update System 2010-03-18 03:26:59 UTC
openoffice.org-3.1.1-19.28.fc12 has been pushed to the Fedora 12 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update openoffice.org'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/openoffice.org-3.1.1-19.28.fc12

Comment 14 Fedora Update System 2010-03-23 23:35:54 UTC
openoffice.org-3.1.1-19.28.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.


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