Bug 611375 - [abrt] crash in oslDoCopyFile (SIGBUS)
[abrt] crash in oslDoCopyFile (SIGBUS)
Status: CLOSED DUPLICATE of bug 601621
Product: Fedora
Classification: Fedora
Component: openoffice.org (Show other bugs)
13
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Caolan McNamara
Fedora Extras Quality Assurance
abrt_hash:d4c3928411b4064d56ef54e5367...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-07-04 22:51 EDT by Greg Trounson
Modified: 2010-07-05 17:22 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-07-05 04:01:24 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (63.43 KB, text/plain)
2010-07-04 22:51 EDT, Greg Trounson
no flags Details

  None (edit)
Description Greg Trounson 2010-07-04 22:51:31 EDT
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/openoffice.org3/program/scalc.bin -calc /mnt/random/Archive/DataArchives/Benchmarks/matlab5000.ods
comment: Seems to only occur on larger files, or those with charts in them.
component: openoffice.org
crash_function: write
executable: /usr/lib64/openoffice.org3/program/scalc.bin
global_uuid: d4c3928411b4064d56ef54e5367141908847bf90
kernel: 2.6.33.5-124.fc13.x86_64
package: openoffice.org-calc-1:3.2.0-12.25.fc13
rating: 4
reason: Process /usr/lib64/openoffice.org3/program/scalc.bin was killed by signal 7 (SIGBUS)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Open command line
2. oocalc <some large file>
3.
Comment 1 Greg Trounson 2010-07-04 22:51:33 EDT
Created attachment 429453 [details]
File: backtrace
Comment 2 Caolan McNamara 2010-07-05 04:01:24 EDT
I bet that /mnt/random/Archive/... is mounted over samba, right ?

*** This bug has been marked as a duplicate of bug 601621 ***
Comment 3 Greg Trounson 2010-07-05 17:22:40 EDT
Yes, that's right. Interestingly, the file seems to open correctly this morning, even from the same location.

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