Project

General

Profile

Bug #10937

Epson V550 scans crash Darktable on import

Added by Frank Walsh over 3 years ago. Updated over 3 years ago.

Status:
Incomplete
Priority:
Low
Assignee:
-
Category:
General
Target version:
-
Start date:
02/29/2016
Due date:
% Done:

20%

Estimated time:
Affected Version:
2.0.1
System:
Mac OS X
bitness:
64-bit
hardware architecture:
amd64/x86

Description

I recently acquired an Epson V550 scanner, and when attempting to import my first roll into Darktable it crashed immediately. I tried to import a single file and that also crashed.

What I have tried: Scanning JPG and TIFF, same result

Replacing ICC profile with Preview - when using SRGB profile I was able to import the file, other profiles failed. Now Darktable will not launch at all!

Files have Grey ICC profile. I have tried to scan in color, but as mentioned above, now I cannot get the program to launch at all

Petri Feb16 015.jpg (4.28 MB) Petri Feb16 015.jpg Frank Walsh, 02/29/2016 03:17 AM
crash log.txt (89 KB) crash log.txt Frank Walsh, 03/01/2016 12:49 AM

History

#1 Updated by Roman Lebedev over 3 years ago

  • % Done changed from 0 to 20
  • Status changed from New to Incomplete

Loads just fine here.
If it crashes, please provide backtrace.
Also, please do make sure that this is the image that crashes darktable - by moving library.db away temporairly and importing only one image at a time.

#2 Updated by Frank Walsh over 3 years ago

I created a new user account with a fresh Darktable library. I put the file previously attached inside a folder called test and I attempted to import the single file. DT crashed immediately. I copied the crash log from the console and have attached it as a text file. I hope this helps. If you need more diagnostics you will need to walk me through the process as I am not a developer

As a test, I rescanned a negative as 24 bit color instead of grayscale. I had to delete the library database before DT would launch, but when I did this the color file imported with no problem.

#3 Updated by Frank Walsh over 3 years ago

Now that I've figured out a good way to test without exploding my library, I have found that if I replace the color profiles from the scanner with generic RGB profiles, the files import no problems. I can work around this by scanning to color, it just increases file size. Hopefully this information will help lead to a fix.

Also available in: Atom PDF

Go to top