Bug 699881 - [abrt] framework::ToolBarManager::DropdownClick
Summary: [abrt] framework::ToolBarManager::DropdownClick
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:54df9257dfd47c05b6e44a54c9f...
: 729823 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-26 20:01 UTC by Dirk Hoffmann
Modified: 2011-10-27 10:08 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-27 10:08:34 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (45.20 KB, text/plain)
2011-04-26 20:01 UTC, Dirk Hoffmann
no flags Details

Description Dirk Hoffmann 2011-04-26 20:01:22 UTC
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 46289 bytes
cmdline: /usr/lib/openoffice.org3/program/soffice.bin
comment: Normal operation, worked on other files before.
component: openoffice.org
Attached file: coredump, 252907520 bytes
executable: /usr/lib/openoffice.org3/program/soffice.bin
kernel: 2.6.35.12-88.fc14.i686.PAE
package: openoffice.org-brand-1:3.3.0-20.5.fc14
rating: 4
reason: Process /usr/lib/openoffice.org3/program/soffice.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1303845366
uid: 500

How to reproduce
-----
1. Edit a JPG file in Draw
2. Edit a new (empty) file in Writer
3. Copy image after cropping from Draw to Writer.
4. Trying to anchor copied image in Writer "as character"

Comment 1 Dirk Hoffmann 2011-04-26 20:01:25 UTC
Created attachment 495024 [details]
File: backtrace

Comment 2 David Tardon 2011-04-27 04:47:23 UTC
You tried to change the anchor by clicking on Change Anchor on the Picture toolbar, right? Did you really just click on the As Character radio button? Or did you "miss" it and clicked somewhere else (where?), or pressed any button, or whatever? The stack looks like the toolbar was removed while the click was being processed. Because the Picture toolbar is contextual, this happens every time the currently selected picture is deselected or removed. But this should not be possible when the toolbar is in use, e.g., when a dropdown list is shown.

Comment 3 Dirk Hoffmann 2011-04-28 05:09:58 UTC
First of all thank you for the quick reaction. After submitting more than a dozen bug reports about OOo without ever getting an answer, I was not expecting a reaction and rather filled the abrt dialogue automatically. Unfortunatly I could not honour your reaction by an equally quick answer.

Your analysis is exact to the point. I should mention that I had a rather large (several Mpxl) image in the Draw instance, and the OOo application had become less responsive after I had cropped the image and switched from the Writer to the Draw instance and back. Therefore I cannot exclude that, after clicking on the anchor menu and the "as character" item (as you correctly assumed), the application had become unresponsive for a couple of seconds and I tried to go already back to the Draw application with the intention to free some memory there by closing the Draw window.

Hence the dropdown menu may or may not have been visible any more, while I attempted to go away from the Writer (where I used the menu). I do not remember, but with a sufficiently big picture (and too small system/memory for that) you may be able to reproduce it. Your explanation that a lock is missing on such a condition (picture deselected due to window switch) is very plausible. I hope this helps you to fix it.

Comment 4 Caolan McNamara 2011-06-17 15:31:17 UTC
Hmm, are we able to reproduce this, or do something about it ?

Comment 5 David Tardon 2011-08-11 05:53:20 UTC
*** Bug 729823 has been marked as a duplicate of this bug. ***

Comment 6 David Tardon 2011-10-27 10:08:34 UTC
I tried to run it under valgrind again, with the same (lack of) luck as the last time.


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