| Summary: | darktable locks up when browsing through RAW images in the darkroom module | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Stephan Mueller <steffo76> |
| Component: | RPM Packages | Assignee: | Rémi Verschelde <rverschelde> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | critical | ||
| Priority: | Normal | CC: | mageia |
| Version: | 5 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | darktable-1.6.6-1.mga5.src.rpm | CVE: | |
| Status comment: | |||
| Attachments: |
darktable debug log
strace of the already locked up process |
||
|
Description
Stephan Mueller
2015-06-20 21:53:41 CEST
Sander Lepik
2015-06-20 21:56:51 CEST
CC:
(none) =>
mageia Thanks for the detailed procedure. I tried to reproduce the issue locally but did not manage (with a folder containing 79 RAW files). Loading the next image is a bit slow, but RAW files are huge and my laptop has little RAM :) In your case, is the issue systematically reproducible? Or did it happen only once while your system was heavily loaded? Is there any output in the terminal when darktable locks up? If not, could you try running: $ darktable -d all &> darktable-debug.log Then reproduce the bug, close darktable. If the log is heavier than 1000 KB, compress it with: $ xz darktable-debug.log And then attach the compressed file to this bug report.
Rémi Verschelde
2015-06-20 22:17:32 CEST
Summary:
darktable locks up =>
darktable locks up when browsing through RAW images in the darkroom module Created attachment 6762 [details]
darktable debug log
Hi,
there is no message on the console when it locks up. It is 100% reproducable so far.
Created attachment 6763 [details]
strace of the already locked up process
Here is a strace of the already locked up process.
Thanks for the debug info, I'll have a look at it. In the meantime, could you test darktable-1.6.7-1.mga5 that I just uploaded to Core Updates Testing? I just installed and tested darktable-1.6.7-1.mga5 but the problem persists. Funny story... if I deactivate the password backend (default kwallet), it seems to work flawlessly, at least I couldn't reproduce the error with a deactivated password backend... Can you still reproduce the issue with darktable-2.0.1-1.mga5 from Core Backports? Otherwise I don't have much clue, I'd propose to bring this issue to the upstream developers as they would probably be of more help. I just tried the distribution supplied darktable-1.6.9-1.mga5 for the first time and could not reproduce the error anymore, so this seems to be resolved. Status:
NEW =>
RESOLVED |