| Summary: | [abrt] darktable-0.8-3.fc14: dt_control_init: Process /usr/bin/darktable was killed by signal 4 (SIGILL) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Andre Dierker <asew54> | ||||||||
| Component: | darktable | Assignee: | Edouard Bourguignon <madko> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 14 | CC: | dwmw2, elad, freddog_de, madko, pavel1r | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | abrt_hash:0d849c8d8fed20527179e1cf398460897f31f24f | ||||||||||
| Fixed In Version: | darktable-0.8-11.fc14 | Doc Type: | Bug Fix | ||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2011-05-30 22:28: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
Andre Dierker
2011-02-20 13:06:33 UTC
Created attachment 479761 [details]
File: backtrace
Were you using darktable before updating to 0.8? Seems there is a problem with you db (/home/fozz/.config/darktable/library.db). Could you try to temporary rename the directory .config/darktable and start darktable again? Can't reproduce the problem. If i rename the directory it ends with some sqlite errors. 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 Ungültiger Maschinenbefehl (Speicherabzug geschrieben) it works fine again with the last nightly build from http://dt-nightly.hamsterkollektivet.se/fedora/14/x86_64/packages/ a downgrade via yum brings back the problem, and yes i used it before 0.8. Even without the .config/darktable directory darktable fails to start? I'm trying to reproduce your problem but darktable keeps working fine. If the problem is not here with darktable-0.8-6.git.df251e2.fc14.x86_64.rpm, it means there is a patch (between stable release and df251e2 commit) we can extract from the git and apply on the 0.8 stable release. We just have to find it out. with both .config/darktable and .gconf/apps/darktable deleted darktable wont start. a new(?) backtrace with both directories deleted. https://bugzilla.redhat.com/show_bug.cgi?id=679175 *** Bug 679175 has been marked as a duplicate of this bug. *** Andre, could you try this package => http://www.linuxed.net/~madko/fedora/darktable-0.8-4.gitdf251e2.fc14.x86_64.rpm I've included 3 patches from the git snapshot df251e2, I hope this will work for you. no sorry its still the same, but now abrt doesn't tell me about the crash. So with the same source code as the package darktable-0.8-6.git.df251e2.fc14.x86_64.rpm from http://dt-nightly.hamsterkollektivet.se/fedora/14/x86_64/packages/ it's still crashing. I'll check the compile options. Andre, have you tried with latest darktable package 0.8-6? I downgradet it from git builds and there are no more crashes in 0.8-6 from fedora-testing. Sorry i was wrong. Darktable now dies when trying to switch from darkroom to edit mode. Created attachment 488098 [details]
darktable abrt backtrace
Hi Andre, Could you try with this rpm http://kojipkgs.fedoraproject.org/packages/darktable/0.8/8.fc14/x86_64/darktable-0.8-8.fc14.x86_64.rpm ? Hello Edouard After deleting configfiles and all *.xmp files, darktable started but crashes when trying to load thumbnails from previously imported images. darktable -d control [revive_job] load image 1 mip 4 [add_job] 30 load image 1 mip 4 [run_job+] 06 12680241.942911 load image 1 mip 4 [revive_job] load image 1 mip 4 [add_job] 29 load image 1 mip 4 [run_job+] 07 12680241.943488 load image 1 mip 4 [run_job-] 07 12680242.020541 load image 1 mip 4 [revive_job] load image 1 mip 4 [add_job] 29 load image 1 mip 4 [run_job+] 08 12680242.038093 load image 1 mip 4 [run_job-] 08 12680242.081576 load image 1 mip 4 [revive_job] load image 1 mip 4 [add_job] 29 load image 1 mip 4 [run_job+] 10 12680242.089292 load image 1 mip 4 [run_job-] 10 12680242.115446 load image 1 mip 4 [revive_job] load image 1 mip 4 [add_job] 29 load image 1 mip 4 [run_job+] 07 12680242.127439 load image 1 mip 4 [run_job-] 07 12680242.178541 load image 1 mip 4 [revive_job] load image 1 mip 4 [add_job] 29 load image 1 mip 4 [run_job+] 08 12680242.184908 load image 1 mip 4 Ungültiger Maschinenbefehl (Speicherabzug geschrieben) Its still not working for me :( My english is bad, but my german is worse. Could you try to run LANG=C darktable -d control instead? Or with gdb to get a full backtrace of the crash? Have you remove the .config/darktable before? Maybe your db file is incompatible because it was generated with a newer version of darktable (nightly build from git). Ungültiger Maschinenbefehl (Speicherabzug geschrieben) means 'bad/invalid machine code (memory dump written)' i deleted the database before gdb output comes later Created attachment 493414 [details]
gdb output
What is your CPU? Looks like bug #697687 (SIGILL) its an AMD Phenom(tm) II X4 905e Processor Moving to darktable (was 0xFFFF) -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Hi Andre, Could you try this rpm: http://koji.fedoraproject.org/koji/getfile?taskID=3087454&name=darktable-0.8-11.fc14.x86_64.rpm Is the bug still here with this rpm release? it seems to be working now. Whats the different? The difference is a patch to add a build option to make darktable binary working on any cpu, not only the cpu used to build it. This options was used since a long time but just silently ignored until now... Thank you for your feedback, I will push this package to stable asap. Best regards. darktable-0.8-11.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/darktable-0.8-11.fc15 darktable-0.8-11.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/darktable-0.8-11.fc14 Package darktable-0.8-11.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing darktable-0.8-11.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/darktable-0.8-11.fc15 then log in and leave karma (feedback). darktable-0.8-11.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report. *** Bug 711114 has been marked as a duplicate of this bug. *** *** Bug 716449 has been marked as a duplicate of this bug. *** darktable-0.8-11.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report. |