Bug 842342
Summary: | [abrt] gnumeric-1.10.17-1.fc16: ole_init_info: Process /usr/bin/gnumeric-1.10.17 was killed by signal 7 (SIGBUS) | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Tuc <sellentuch> | ||||||||
Component: | gnumeric | Assignee: | Huzaifa S. Sidhpurwala <huzaifas> | ||||||||
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
Severity: | unspecified | Docs Contact: | |||||||||
Priority: | unspecified | ||||||||||
Version: | 16 | CC: | belegdol, huzaifas, terra | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | x86_64 | ||||||||||
OS: | Unspecified | ||||||||||
Whiteboard: | abrt_hash:8565b610ca0e90353e1f92081e74a5033ee96a61 | ||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2013-02-13 14:49:02 UTC | Type: | --- | ||||||||
Regression: | --- | Mount Type: | --- | ||||||||
Documentation: | --- | CRM: | |||||||||
Verified Versions: | Category: | --- | |||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||
Embargoed: | |||||||||||
Attachments: |
|
Description
Tuc
2012-07-23 14:23:51 UTC
Created attachment 599793 [details]
File: maps
Created attachment 599794 [details]
File: dso_list
Created attachment 599795 [details]
File: backtrace
I cannot test it myself since I'm already on F-17 (and thus gnumeric-1.11.x). Morten, do you have any ideas? I suspect the operative words are "Windows share" and that this is really version independent. I cannot test environment, though. //fs1/GROUPS 2044720126 1997814010 46906116 98% /g sudo mount -t cifs -o username=fred,domain=example,rw,uid=1000,gid=1000 //fs1/GROUPS /g File came off that drive. It was in use, there was some sort of lock file in the directory, and I think Windows has some sort of lock too. I cheated and removed the disk lock, but still blew up. Once the user stopped using the file on his system, I was able to access it fine. This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |