is the crash log the same thing as the backtrace txt file or different? if different,where do I find it?
Please attach it here first, and only open a GitHub issue if PEBCAC is eliminated.
In addition to the backtrace, you can also start as darktable -d all > log.txt and attach that as well.
darktable_bt_4VGJL2.txt (43.5 KB)
Seems like something is indeed not coping with such a huge library…
It was coping perfectly fine until I decided to install Sigma Pro Photo (windows) under Wine. Hit all sort of unmet dependencies and in trying to fix that I ended up having to upgrade from 22.04 LTS to 23.04 and eventually to 23.10.
Somewhere in all that mess I broke darktable. And I deleted SPP, so now I have nothing! Having to revert to win/LR on my other machine to do anything 
I should have left it as it was and just used SPP on my win machine.
Thanks to everyone for pitching in on this, most appreciated (even if it isn’t fixed!).
Wine and a 32 bit Windows program should have nothing to do with how Gimp and Darktable work. I use several old 32 bit programs with Wine.
Upgrading your ubuntu is probably not a great way to fix a broken installation and often old-and-tried is best.
Usually in a terminal sudo dpkg --configure -a then sudo apt update is a fix.
Someone asked about Gimp / Darktable a week or so ago on another forum. While I do not use Darktable personally, to confirm it works, installed in a Mint 21.3 (VM) equivalent to 'buntu 22.04.
Using Gimp 2.10.36 and Darktable 4.6.1 Only 2 minutes.
I’m sure they don’t. But when I attempted to install SPP 5.5, I got errors saying it needed wine32 to run it. And when I attempted to install wine32 I got errors saying there were unmet dependencies. So then I trawled the web looking for answers for this and trying all the various suggestions. When nothing worked I decided to update Ubuntu in the hope that whatever this strange dependency problem was it would go away. And it did and I was able to install and run SPP 5.5. Unfortunately, something broke darktable in the process. And having failed to fix it despite hours of effort, I uninstalled darktable. But upon trying to re-install it I discovered that my system only had 4.6.0 a version that has a serious bug and I don’t want to use. The bug fixed 4.6.1 didn’t seem to be available (since then I have been on a journey learning about application installation in Linux). I decided to update to 23.10 in the hope that hope that 4.6.1 would be available. And it is in Snap form but that is not what I wanted, so I have been learning how to install in other ways (not that I feel that I will remember the lessons after half an hour!). Having now installed 4.6.1 with apt, it crashes on start up, which is why I’m where I am.
As it happens I have another computer that is running 22.04 LTS and darktable 4.2. I just upgraded that one to 4.6.1 and it did that in seconds and everything is running fine.
So who knows what is going on with my new computer…
I tried something. I renamed my .config/darktable folder and started darktable. It opened instantly and I was able to import a folder of images and it also imported the xml files and applied all the historical edits.
So, the problem is clearly something in that config folder. I could (if I have to to) rebuild my entire library by re-importing all my files but I would prefer to keep my old configuration if possible by fixing whatever is wrong in that folder. Any suggestions for narrowing it down? I take it there isn’t any kind of catalogue integrity/fix tool like lightroom has?
You might have ended up in some inconsistent database state between launching all those different versions, so re-importing might be your best bet actually (unless you have even more backups). As you noticed, the edits are kept in XMPs and reconstructed upon import.
I used one of the snp backups to replace the library.db. It seems to be working. However, I have lost my lua scripts, presets, and darkroom module customisation. Any idea where that is stored?
In the data.db, there are two databases.
I copied a snp backup, renamed it and replaced library.db in my new .config folder and darktable runs.
But if I use that library folder in the default .config folder and run darktable from that it still segmentation error crashes.
This makes me think the problem is not the library.db but something else. I see the data.db doesn’t seem to get backed up either. UPDATE actually it does. Let try resoring one of the backups.
I restored one of the backup library.db and data.db files and darktable runs but it is still missing my customisations to the darkroom tabs/modules and my preferences. Are they stored somewhere else?
Possibly the darktablerc file.
It’s beginning to look to me like the darktablerc file is the cause of the crashes. If I swap in the old one it crashes. I’ll try pasting the new one into the old config folder next
darktablerc is a plain text file. You can try deleting the first half and see if darktable crashes. If yes, restore the file, delete the second half.
Once you know which half is broken, delete one of the quarters (half of the ‘broken half’). Then an eighth and so on, until you narrow it down to a line or couple of lines. Take the original file, delete only the problematic line(s), enjoy your restored darktable config.
Its a text file, so you can diff two versions of it.
Ok, I put the new one in the old config folder, restored the two catalogue files from snps. I redid my preferences, reset the 3D LUTs folder location, found my darkroom customisations still existed, I just had to select them as a preset.
I expect I’ll find other glitches in due course, but for now it looks like I’m back in business.
Until next time…
Cheers!
Dave 
ps Still missing my lua scripts. I had some kind of widget in the left panel that let me switch scripts on and off (things like fancy export options, image blending and so on). Can’t remember how that works. UPDATE: forget it, I found the widget, different place than I thought 
1 Like