Bug 711797 - [abrt] openoffice.org-writer-1:3.3.0-20.5.fc14: to_int_type: Process /usr/lib64/openoffice.org3/program/swriter.bin was killed by signal 7 (SIGBUS)
Summary: [abrt] openoffice.org-writer-1:3.3.0-20.5.fc14: to_int_type: Process /usr/lib...
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:1d359f84209a534a669cac16771...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-08 14:18 UTC by Nicolas De Amicis
Modified: 2011-06-09 08:54 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-09 08:54:37 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (164.84 KB, text/plain)
2011-06-08 14:18 UTC, Nicolas De Amicis 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Nicolas De Amicis 2011-06-08 14:18:03 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 168794 bytes
cmdline: /usr/lib64/openoffice.org3/program/swriter.bin -writer
component: openoffice.org
Attached file: coredump, 245714944 bytes
crash_function: to_int_type
executable: /usr/lib64/openoffice.org3/program/swriter.bin
kernel: 2.6.35.13-91.fc14.x86_64
package: openoffice.org-writer-1:3.3.0-20.5.fc14
rating: 4
reason: Process /usr/lib64/openoffice.org3/program/swriter.bin was killed by signal 7 (SIGBUS)
release: Fedora release 14 (Laughlin)
time: 1307540531
uid: 500

How to reproduce
-----
1.Try to edit a pdf with openoffice
2.
3.
Comment 1 Nicolas De Amicis 2011-06-08 14:18:06 UTC 
Created attachment 503708 [details]
File: backtrace
Comment 2 Caolan McNamara 2011-06-08 14:34:53 UTC 
Can you attach the .pdf which triggered this. 

Though with a SIGBUS I'd suspect something wrong with some physical media, e.g. a usb key pulled out and/or bad disk. Could also check your /var/log/messages for anything logged around the same time as your crash.
Comment 3 Nicolas De Amicis 2011-06-09 05:42:09 UTC 
I use Fedora at work, the PDF is confidential. You are right, the PDF is on a windows share, mounted by autofs. I have copied this PDF in my home and now I can edit this PDF.

In /var/log/messages, I have this lines before crash:
kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT
kernel: CIFS VFS: Send error in read = -13
Comment 4 Caolan McNamara 2011-06-09 08:54:37 UTC 
Can't really do anything about that then really.
Note You need to log in before you can comment on or make changes to this bug.