Darktable crashing

jbratch

Just checked:

Checking integrity of darktable ESC[32mOK ESC[0m

WetGeek

jbratch

Sorry, that's all I can think of. This might be one for the team. If so, submitting a bug at the Dev Tracker (top of this page) might be the quickest way of getting it resolved. It will at least get the attention of someone who might be able to get to the bottom of it.

jbratch

As a side note, rocm packages also all checked out ok...

Solarmass

have you tried flatpak version?
https://flathub.org/apps/org.darktable.Darktable

jbratch

Solarmass I'll keep that in mind as a last resort... I'm pretty sure that darktable was working when I first installed, so I am thinking maybe an update broke it. I'll keep that in mind though, as a backup - but I do think this problem is fixable 🙂

brent

Checking integrity of darktable ESC[32mOK
ESC[0m

I've seen output like this gobbledygook before. It usually green SUCCEED or a red FAIL.
If you run check with sudo you might see different terminal output.

edit: or a red Broken? and a green Passed? been so long I forgot

jbratch

brent You are correct - when I pipe it through less or grep though, the escape characters are shown rather than the color codes. ESC[32m turns it green, ESC[0m sets it back to normal. Grep just happily passes them on without processing 🙂

Edit:

the less command is the culprit. grep does the right thing (you just have to imagine it is green in the forums, lol)
:
root@machina ~ # eopkg check | grep darktable
Checking integrity of darktable OK

brent

jbratch thanks did not know re: grep. so is your darktable package broken or well? can't tell.

jbratch

brent It reports OK. I can't find any broken packages.

On a whim, I removed the darktable directories and cache, but still got the illegal instruction error. I may try removing ROCM to see if that helps - I know Solus uses a downlevel version to keep Blender happy, and I have no idea what the requirements are for darktable. I'm sure it was all vetted, but still... Something is amiss...

WetGeek

jbratch Something is amiss...

Indeed. As a pro photographer in an earlier life, I found your dilemma intriguing, so I thought I'd install Darktable and take a look. Installation (on my Plasma laptop) was uneventful, although it involved 22 packages. When I tried to run it from the menu, though ...

... absolutely nothing happened. No error messages, but no Darktable, either. So I tried launching it from the terminal, to see if anything more interesting happened, and this is what I got:

jerry@malachite-plasma ~ $ darktable
Illegal instruction (core dumped)

I can only repeat my earlier advice. If I were you, I'd write up a bug and let the team debug it and fix it.

jbratch

WetGeek Thank you for checking - I wanted to make sure it wasn't just me, or something stupid I did to my PC first. I'll see if I can get a bug report opened!

WetGeek

jbratch I'll see if I can get a bug report opened!

First-timer, eh? That's where we all started. You'll find that it's very easy and straightforward.

jbratch

WetGeek True - I have submitted bug reports to Red Hat and IBM before, but never via git. I was duly impressed with the attention to the issue, as well as the fact that it was fixed in probably 2 hours. I'm really liking Solus so far - great desktop OS, for sure...

palto42

Just faced the same issue, linking the bug report here:
https://github.com/getsolus/packages/issues/1497

jbratch

palto42 Ha! that is the one I opened 🙂

I have to say, their response was very quick, likely because there was a set of updates about ready for release. I tried to install the new darktable package by itself, but it wanted a newer version of colord, so they went ahead and released the update, since it was ready. After updating, colord was having issues, but darktable was mostly working. Looking into the colord issue, /var/lib/colord was empty. I did a bit of research, and saw a couple of solutions that recommended downgrading colord, then reinstalling the newer version. I downloaded the previous version from https://packages.getsol.us/shannon/c/colord/, then sudo eopkg it colord-1.4.6-22-1-x86_64.eopkg. The old version happily installed (which made me question dependency checking, but no worries), and restarted colord. The database and my monitor profile were in place. I tarred them off, then updated colord to the latest, and the database was retained. Another restart of colord showed everything good, and Darktable is working as it should. My issue is already closed on github, but I wanted to follow up here in case anyone is having similar issues.

Thanks all!

Amnios

I have the exact same issue and the same error.

alfisya

Amnios It is already fixed on unstable, will come to stable next sync.

Geum

Hello all, I found this thread last week when I was experiencing the exact same issue as OP with darktable in XFCE on solus. I played around with the steps jbratch mentioned but I didn't have any luck. I was hoping that the issue would be resolved with the latest sync (Feb 9), however I am still having the same issue. It looks like Darktable was not updated. Has that update been pushed to the next sync? Thank you!