| Summary: | [abrt] darktable-0.8-8.fc14: Process /usr/bin/darktable was killed by signal 4 (SIGILL) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mike Parker <mikethepsych> | ||||||
| Component: | darktable | Assignee: | Edouard Bourguignon <madko> | ||||||
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 14 | CC: | madko | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | abrt_hash:d8cd8a154b0b7b303cf88bd5faa09fdbcffb13f6 | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2011-05-23 19:56:11 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
|
Description
Mike Parker
2011-04-29 21:39:08 UTC
Created attachment 495870 [details]
File: backtrace
The backtrace seems completely different from your previous bug #700486 I will try to reproduce this bug. Have you clean all previous files from other darktable version like /home/Mike/.config/darktable/library.db before running darktable? As suggested, I removed my old library.db. Issue still persists - I still see "darktable was killed by signal 4 (SIGILL)" in ABRT. Not really able to comment on different backtrace. From a user perspective, both versions appear to exhibit identical behaviour when crashing.... FYI, I have my suspicions that the issue *may* be related to the 0.8-X version having a dependency on the newer libexiv2.so.10 whereas older versions of darktable used libexiv2.so.9. Since upgrading the libexiv2 package to bring in libexiv2.so.10, I've seen a bug in gthumb related to the Exiv2::Internal::TiffDirectory::doWrite function (bug #700518). It might be nothing/unrelated, but I thought I'd let you know. Additional data: Invoking darktable 0.8-8 from the command prompt sees the following returned to STDOUT/ERR: sqlite3 error: /builddir/build/BUILD/darktable-0.8/src/common/collection.c:447, function dt_collection_update_query(): no such table: selected_images sqlite3 error: /builddir/build/BUILD/darktable-0.8/src/common/collection.c:448, function dt_collection_update_query(): no such table: selected_images sqlite3 error: /builddir/build/BUILD/darktable-0.8/src/common/collection.c:449, function dt_collection_update_query(): no such table: selected_images [image_cache_read] failed to recover the cache from `/home/Mike/.cache/darktable/mipmaps' Illegal instruction (core dumped) Created attachment 499923 [details]
More informative gdb backtrace
*** Bug 700486 has been marked as a duplicate of this bug. *** Hi Mike, Could you try with http://koji.fedoraproject.org/koji/getfile?taskID=3087454&name=darktable-0.8-11.fc14.x86_64.rpm Is it still crashing with SIGILL? Edouard, 0.8-11 seems to have resolved the issue - I no longer see the SIGILL crash and darktable appears to function fine. I'll let you close the bug with the appropriate status. Many thanks, Mike |