Bug 664288 - [abrt] openoffice.org-writer-1:3.2.0-12.33.fc13: __poll: Process /usr/lib/openoffice.org3/program/swriter.bin was killed by signal 6 (SIGABRT)
Summary: [abrt] openoffice.org-writer-1:3.2.0-12.33.fc13: __poll: Process /usr/lib/ope...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: 13
Hardware: i686
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:906ad37f65eb3dcd93861c082c0...
: 664731 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-19 17:07 UTC by Paul M. Summitt
Modified: 2011-01-22 18:01 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-01-06 16:28:52 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (1.14 KB, text/plain)
2010-12-19 17:07 UTC, Paul M. Summitt
no flags Details

Description Paul M. Summitt 2010-12-19 17:07:19 UTC
abrt version: 1.1.14
architecture: i686
cmdline: /usr/lib/openoffice.org3/program/swriter.bin -writer
comment: actually, nothing was happening at the time of the crash.  Was simply thinking about what to do next.
component: openoffice.org
crash_function: __poll
executable: /usr/lib/openoffice.org3/program/swriter.bin
kernel: 2.6.34.7-63.fc13.i686
package: openoffice.org-writer-1:3.2.0-12.33.fc13
rating: 4
reason: Process /usr/lib/openoffice.org3/program/swriter.bin was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
How to reproduce: editing document which included graphics
time: 1292772694
uid: 500

backtrace
-----
[New Thread 30035]
[New Thread 30026]
[New Thread 30039]
[New Thread 30040]
[New Thread 30041]
[New Thread 30042]
[New Thread 30043]
[New Thread 30044]
[New Thread 30045]
[New Thread 30046]
[New Thread 30048]
[New Thread 30049]
[New Thread 30061]
[New Thread 30027]
[New Thread 30030]
[New Thread 30032]
[New Thread 30033]
warning: "/var/cache/abrt-di/usr/lib/debug/.build-id/b0/92e943ad63f83804af87c5bc62b0c1a9610a8d.debug": separate debug info file has no debug info
warning: "/var/cache/abrt-di/usr/lib/debug/.build-id/de/72a6d25a3d3e3c8b8c2eaa2d50ad7fb046a2d6.debug": separate debug info file has no debug info
warning: "/var/cache/abrt-di/usr/lib/debug/.build-id/72/908c2613b36817a167220443e477d6daa86cb1.debug": separate debug info file has no debug info
Core was generated by `/usr/lib/openoffice.org3/program/swriter.bin -writer'.
Program terminated with signal 6, Aborted.
#0  0x00e7d416 in __kernel_vsyscall ()

Thread 17 (Thread 30033):
#0  0x00e7d416 in __kernel_vsyscall ()
No symbol table info available.
#1  0x0097cdf6 in __poll (fds=0xb526b890, nfds=2, timeout=-1)
    at ../sysdeps/unix/sysv/linux/poll.c:87

Timeout exceeded: 60 second, killing gdb

Comment 1 Paul M. Summitt 2010-12-19 17:07:21 UTC
Created attachment 469611 [details]
File: backtrace

Comment 2 Paul M. Summitt 2010-12-19 22:07:47 UTC
Package: openoffice.org-writer-1:3.2.0-12.33.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
Right click on the image
choose save graphics


Comment
-----
While saving an image that had been loaded into a document back out as an image.

Comment 3 Caolan McNamara 2010-12-20 09:49:55 UTC
Unfortunately the backtrace is truncated so its missing information.

I inserted a picture, and did right click, save as and successfully saved the image so I can't reproduce this.

Can you reproduce this ?, i.e. with a specific document.

Its possible that this might be related to the neon threading problems, if e.g. the document was a html document ?, or the images in it were links to http:// locations ?

Comment 4 Paul M. Summitt 2010-12-20 16:33:52 UTC
This has occurred at least twice now.  I noticed both times that the backtrace was truncated.  This truncation is not occurring on any other errors I am reporting.

Here is what I am doing.  First, a document was sent to me in .docx format containing screenshots of an application I have been asked to write help files for.  I had asked for jpgs of the screen shots but sometimes you have to dance with the lady that brung ya, you know.

I imported and converted the docx document into OpenOffice and saved it as an odt file.

Rather than wait for the individual screenshots to be re-shot and sent again I have been saving the images from the document by right-clicking on the image, choosing Save Graphics, changing to the directory where I am saving the images, and then saving it as jpg.

Because of the propriety of the application development, I can not send you the original docx file.  Before I quit using the products of a certain company I had experience problems with the docx format (even within their own applications) and this may be part of the issue here.  Still, it is a pain to have this issue completely crass OpenOffice and my having to start over each time.

I have checked and the images were saved into the docx document, not as links.

Please let me know if there is anything else I can assist with.  Love OpenOffice and Love Fedora.  Happy to contribute of my time toward the solving of issues such as these.

Comment 5 Caolan McNamara 2010-12-20 16:58:28 UTC
Not much I can without a reproducer or a guaranteed route-to-reproduce or at least a stack.

Feel free to email me privately a document which reproduces this. Otherwise maybe we'll get lucky and get a reproducer independently eventually.

Comment 6 Paul M. Summitt 2010-12-20 19:35:29 UTC
Understood.  While it occurred three times yesterday while I was working, I have not had a crash today so far knock on wood.  We'll just have to wait and see I guess as I do not have  Microsoft Office 2010 (or any other Microsoft Product nowadays) and therefore can not create a document to send to you.  Thanks.

Comment 7 David Tardon 2010-12-21 14:14:20 UTC
*** Bug 664731 has been marked as a duplicate of this bug. ***

Comment 8 Paul M. Summitt 2010-12-21 15:50:11 UTC
Package: openoffice.org-writer-1:3.2.0-12.33.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1.  Click File Menu
2.  Click Save

Had 2 documents open and one spreadsheet.  All went down.  All recovered.

Comment
-----
The Backtrace fails on OpenOffice everytime.

Comment 9 Caolan McNamara 2011-01-06 16:28:52 UTC
Can't reproduce this one :-( Typically right click and save as works. If you've got a reproducer you can't share publicly feel free to email it to me directly.

Comment 10 Paul M. Summitt 2011-01-22 18:01:13 UTC
I just submitted another backtrace, again truncated.  It happens on multiple documents.


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