| Summary: | gnumeric fails to start - undefined symbol: go_direction_get_name | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | dan-fedora |
| Component: | gnumeric | Assignee: | Huzaifa S. Sidhpurwala <huzaifas> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 14 | CC: | belegdol, huzaifas |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-06-14 21:30:05 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
dan-fedora
2011-06-14 20:49:35 UTC
Well, I am unable to reproduce this - gnumeric starts for me on both f14 x86_64 and f15 x86_64. Please try the following: $ rpm -V gnumeric Which version of goffice do you have installed? ah, ok $ rpm -V gnumeric $ rpm -q goffice gnumeric goffice-0.8.14-1.fc14.x86_64 gnumeric-1.10.15-2.fc14.x86_64 ^ this fails $ sudo yum update goffice ... Updating : goffice-0.8.15-1.fc14.x86_64 Cleanup : goffice-0.8.14-1.fc14.x86_64 ^ this works Looks like something went south on your system. Is it gnumeric working after goffice update? Ah, that's what I meant by "this works". The latest gnumeric package works after I updated goffice. How this machine got to this point: goffice package was installed June 7th (through yum) gnumeric package was installed today (June 14th) (through yum) I suppose one way to prevent this from happening to other people is to hard-code the version check in gnumeric spec. Such as: Requires: goffice >= 0.8.15 Since gnumeric and goffice are most of the time released together, I usually push them as one update. I can consider hardcoding the dependency with the next release. |