Ask Your Question

Basic troubleshooting procedures for application that won't start

asked 2016-03-26 16:10:04 -0500

thingummybob gravatar image

updated 2016-03-28 10:08:22 -0500

florian gravatar image

Still learning all about Fedora and Linux, so please excuse basic level questions. I've tried searching for my answer but can't seem to find specifically what I need to get me started.

When I first installed Fedora and before tweaking, I installed and ran Darktable via the software manager. It installed and worked perfectly fine.

Then, several Fedora kernels later, and having managed to hook up my Nvidia graphics card to run under the akmod drivers through use of a particular repo, Darktable will no longer start up. The activity icon whirls for a bit and then stops.

I've had no luck at all trying to post over on the darktable newsgroups - possibly posting in the wrong place? I've spent more than a week now trying to compile my own version of darktable from their source, following their instructions. Despite having all dependencies the build fails. Again a complete lack of any response over on their forum.

I don't need the lastest version, I'd be quite happy to have the current stable version. What I'd like is for someone to help me get started with some basic log inspection so that I can find out where the problem is, and whether I might be able to fix it. I would consider switching my graphics back if that were the only way, but as yet I'm not actually certain that is the problem - that's more like guesswork at the moment.

How/where should I be interrogating logs to find out what's preventing it running? I notice there's a LOT of logging in Linux ;0)

edit retag flag offensive close merge delete



The first thing you should do is to run the application the terminal that way you can see the output and posible the error that brake it.

aeperezt gravatar imageaeperezt ( 2016-03-26 21:40:47 -0500 )edit

4 Answers

Sort by ยป oldest newest most voted

answered 2016-03-26 23:25:15 -0500

subpop gravatar image

Definitely run it in Terminal and paste the output to and link it to this post. The other option you can check is run journalctl -b | grep darktable and see if there's any log entries in the journal. Darktable might log to the systemd journal. I'm not familiar enough with it to know for sure.

edit flag offensive delete link more


Why didn't I think of this!! Thanks. Here's my output - clearly there's a problem

thingummybob gravatar imagethingummybob ( 2016-03-27 09:39:35 -0500 )edit

just to expand a little:

I've not been able to find any output from Darktable via journalctl, but that said this seems like a fairly complex journal to a beginner. I have however installed "logs" which is some sort of graphical interface and which is kind enough to sort logs into categories. As such I can't see anything generated by Darktable, so it's definitely going to have to be via terminal

thingummybob gravatar imagethingummybob ( 2016-03-27 09:44:59 -0500 )edit

more output. Your initial suggestion gave me something to search for via google, so I ran "ldd -r /usr/bin/darktable" and got the following... clearly something's broken. Is this something to do with having old packages or configs lying around?

thingummybob gravatar imagethingummybob ( 2016-03-27 09:56:07 -0500 )edit

would the fact that I tend to simply # su - before running any commands - as opposed to $ sudo - make any difference? I wasn't aware that there's any important differences between $ sudo 'command' and # 'command' - the latter simply avoids my having to keep typing passwords

thingummybob gravatar imagethingummybob ( 2016-03-27 11:38:50 -0500 )edit

Darktable needs OpenEXR-libs version 2.2.0

davidva gravatar imagedavidva ( 2016-03-27 15:20:37 -0500 )edit

answered 2016-03-26 23:01:32 -0500

davidva gravatar image

updated 2016-03-26 23:29:28 -0500

Hi, I recommend you, share a log file; but if you need a updated version of darktable exist 2 way.

1) Updated version 2.0.0

dnf -y copr enable tsgeek/Darktable
dnf clean metadata && dnf update

2) Git version (nightly build)

dnf -y copr enable decathorpe/darktable-git 
dnf clean metadata && dnf update
edit flag offensive delete link more


nice idea, but as per my original post, for whatever reason I've been getting NO help or feedback at all over at darktable. Until I can find out why it's broken, there seems little point in trying to build a later (unstable) version

thingummybob gravatar imagethingummybob ( 2016-03-27 09:41:45 -0500 )edit

tried this but it didn't work. I think the problem is related to installation paths on my system - thus not strictly speaking an issue with Darktable.

Is there such a thing as some sort of 'correct' file-path map I can look up to see if my basic install configuration is correct?

thingummybob gravatar imagethingummybob ( 2016-03-27 18:19:15 -0500 )edit

answered 2016-03-28 06:15:46 -0500

updated 2016-03-28 11:02:12 -0500

hhlp gravatar image

Do: $ sudo dnf install OpenEXR-libs-2.2.0-4.fc23.i686 OR: # dnf install OpenEXR-libs-2.2.0-4.fc23.i686 and see if that fixes it.

I found the package by doing: $ sudo dnf whatprovides since it seems this is what are you missing/what is needed in your case.

edit flag offensive delete link more


Nice idea but sadly it doesn't help.

I've been having a lot of help from the folks over at DT (helps if I follow instructions properly!!). However, this seems to boil down at present to some bizarre system configuration issue. On suggestion I ran

"# rpm -Va" and note that it says

/usr/lib64/ is missing

however, if I run

$ locate

it returns


Note that these are NOT the same directories but appear to reference the same libraries. So either OpenEXR is not installed correctly or some other major conflict. Any suggestions?

thingummybob gravatar imagethingummybob ( 2016-03-28 09:53:21 -0500 )edit

Then I guess you have the 32 bit but it requires the 64 bit. Try $ sudo dnf install OpenEXR-libs-2.2.0-4.fc23.x86_64 OR: # dnf install OpenEXR-libs-2.2.0-4.fc23.x86_64 then

ifohancroft gravatar imageifohancroft ( 2016-03-28 10:02:33 -0500 )edit

Thanks again, but in fact after a LOT of digging around, testing etc. I followed both advice elsewhere and partly my own 'instincts' and decided to completely wipe and re-install. Since then, everything's worked perfectly! So it all came down finally to something getting irretrievably screwed up stands up, takes bow ;0)

thingummybob gravatar imagethingummybob ( 2016-03-29 07:47:24 -0500 )edit

answered 2016-03-29 07:48:15 -0500

thingummybob gravatar image

I guess I finally answered this one myself by wiping and completely reinstalling Fedora 23. Didn't actually hurt, and the third time I've done it, things went a lot more smoothly ;0)

edit flag offensive delete link more

Question Tools

1 follower


Asked: 2016-03-26 16:10:04 -0500

Seen: 1,399 times

Last updated: Mar 29 '16