<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body><div>Maybe that is possible to recompile digikam with xfc support turned off ?</div><div><br></div><div><br></div><div><br></div><div id="composer_signature"><div style="font-size:85%;color:#575757" dir="auto">Sent from my Samsung Galaxy smartphone.</div></div><div><br></div><div style="font-size:100%;color:#000000"><!-- originalMessage --><div>-------- Original message --------</div><div>From: Elle Stone <ellestone@ninedegreesbelow.com> </div><div>Date: 2017-10-28 12:17 PM (GMT-07:00) </div><div>To: digikam-users@kde.org </div><div>Subject: Re: digiKam crashing on every second or third XCF file - is there a config file I can modify? </div><div><br></div></div>On 10/28/2017 01:40 PM, Gilles Caulier wrote:<br>> The crash about XCF is a redondant problem, due to changes in XCF format.<br><br>Well, actually digiKam did crash on some older XCF files, just not on <br>all of them.<br><br>> <br>> The XCF image loader is delegate to KDE frameworks which provide the<br>> relevant plugin.<br><br>What software packages do I modify so that KDE frameworks does *not* <br>provide the relevant GIMP XCF plugin? It seems a shame that digiKam <br>crashes instead of just ignoring file formats that it can't open.<br><br>If KDE frameworks would completely ignore XCF files, I could add "xcf" <br>as a new file format, and digiKam would just show a blank thumbnail, <br>which would be great. Well, at least I'd be able to use digiKam to <br>browse to the XCF files, locate which is which using the "png sidecar" <br>files, and then open the actual XCF file from digiKam.<br><br>Best,<br>Elle<br><br><br></body></html>