Darktable won't open

Only two questions, you’re running a 32.Bit system,the Darktable Flatpack is also 32 Bit?
And why don’t use the Version form the repository of your distribution?

1 Like

Linux Mint ships flatpak by default in their software center, so it is likely this was installed “from the distribution.”

1 Like

The remnants of my education forbid me to comment

I don’t understand your comment, sorry.

My opinion on Flatpack is here off topic. But I rather suspect a flaw in the flatpack creation than in darktable.

Sorry to zombie this thread, but I’m in the same situation and was hoping to find an answer. Was this ever resolved?

In my case I had been using Darktable and after a couple of updates it won’t start any more. I get a wait cursor then nothing, no error message.

I’ve deleted and reinstalled Darktable but I get the same result. I assume it because the database/config files are not removed on deinstallation. What files/folders should I delete? I’m not concerned about any photos/edits etc. I don’t have anything I need to keep/preserve in Darktable. I’m a Linux Mint NOOB so explicit commands would be appreciated.

Thanks,

What version of darktable and what kind of package? Deb package, snap package, or flatpak package?

It is whatever is in Synaptics Library, I think it is version 2.6.2. Not sure about snap or flatpack.

Thanks,

Provided your config and database is in ~/.config/darktable do the following in an xTerm

cd ~/.config
mv darktable darktable.bak
darktable

I confirmed the version number in Software Manager is 2.0.3-1

cd ~/.config
mv darktable darktable.bak
darktable

Got me this:
[defaults] found a 64-bit system with 2023956 kb ram and 2 cores (0 atom based)
[defaults] setting very conservative defaults
… then nothing

I deinstalled darktable and re-did the ‘rm darktable darktable.bak’ and the darktable folder is gone Did the same for entangle (tethering program) just in case it was in conflict

$ darktable
Gives me this:
[defaults] found a 64-bit system with 2023956 kb ram and 2 cores (0 atom based)
[defaults] setting very conservative defaults
[init] the database lockfile contains a pid that seems to be alive in your system: 2862
[init] the database is locked, probably another process is already using it trying to open the images in the running instance

Any suggestion on what try next?

Restart, then do this:

cd ~/.config
rm -rf darktable
darktable

I tried that (confirmed directory is gone with ls ) and got:

[defaults] found a 64-bit system with 2023956 kb ram and 2 cores (0 atom based)
[defaults] setting very conservative defaults

… then nothing

I opened another term window and ran

pgrep -l darktable

which returns
2481 darktable

So it looks like it is running but no gui

I have since upgraded to 2.4.4 via a ppa, but I’m getting the same results I had with the earlier version.

If I run darktable again I get the error:
the database lockfile contains a pid that seems to be alive in your system: 2481

Which is the pid of the first instance instantiated but running without a giu.

The lock file message means that darktable didn’t exit cleanly. There are files in ~/.config/darktable that are library.db.lock and data.db.lock.

Not sure why darktable isn’t starting.

cd ~/.config
rm -rf darktable 
darktable -d all

That gets me:

an error has occurred while trying to open the database from
/home/jason/.config/darktable/data.db
the database lock file seems to be empty

Thanks for your help on this. Rather frustrating to have it working one day and dead the next…

You need to rm ~/.config/darktable/data.db.lock

At the moment I’m typing on my phone, sorry for not that nice formatting…

I get the feeling, dt is somehow still running, by the time we delete or move the ~/.config/darktable
OR
it gets started either
-automatically or
-with parameters we don’t see here

To check this try the following:
ps aux | grep darktable
alias | grep darktable

actually above with your pgrep you found that. So killing dt prior moving away it’s config is essential

sudo kill “process number”

… after that and being sure there is no alias and no other autostart and also being sure there is only one installation of dt on your machine, try again to move or delete ~/.config/darktable

Ok so I have single stepped this to confirm dt is starting but not displaying a gui

Removed app icon pinned to start panel
Restart
Uninstalled dt
Restart
rm -rf ~/.config/darktable
Restart
pgrep -l darktable (to confirm not running)
Installed dt
Restart
pgrep -l darktable (to confirm not running)
Run dt - wait cursor for about 10 seconds, nothing on screen or panel Alt-Tab just to make sure it isn’t off screen somewhere
pgrep -l darktable (which returns a pid of 2551)

So , despite best efforts I’m where I started. Thanks all for your help. Is there another forum where I could take this?

@Area51Resident your last question could be misunderstood or misinterpreted. Especially some(if not all) darktable developers are here :slight_smile:

However, you might bring it to a MINT- or an UBUNTU-Forum, AFAIK your MINT is UBUNTU-based.
Maybe that is actually a good idea, as dt acc. to my experience is rock solid and the issue might be somewhere else…

We may still try some things together…

→ It looks to me know dt is starting but the GUI crashes or is broken in any other way. ←

I never saw something like this on my machine but I would expect, if you start dt -d all on a terminal, you would get helpfull feedback
e.g. in my case, because I have git-master installed in parallel I geth this:

~ $ darktable -d all
[memory] at startup
[memory] max address space (vmpeak): 271212 kB
[memory] cur address space (vmsize): 271212 kB
[memory] max used memory (vmhwm ): 16708 kB
[memory] cur used memory (vmrss ): 16708 kB

** (darktable:30395): WARNING **: 04:57:06.441: Couldn’t register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[init] database version of `library.db’ is too new for this build of darktable. aborting
ERROR : cannot open database

If by what ever reason, we see here, you have a very old dt-version, then pls. spend what ever it takes, to get at least darktable-2.4.4 on hand

Than still some other analysis (btw. now might be the time to start a crisp list, what have been done so far, not to all details but basic steps)

  • pgrep -l darktable (make sure is not running)
  • if so, pls.
  • kill -9 xxxx (where xxxx is th PID you got above)
  • in a terminal type darktable --version
    → geths me here:

~ $ darktable --version
this is darktable 2.6.2
copyright (c) 2009-2019 johannes hanika
darktable-dev@lists.darktable.org

compile options:
bit depth is 64 bit
normal build
SSE2 optimized codepath enabled
OpenMP support enabled
OpenCL support enabled
Lua support disabled
Colord support disabled
gPhoto2 support enabled
GraphicsMagick support disabled
OpenEXR support enabled

After you are sure, dt is not running (pgrep), pls try from a terminal

  • darktable -d all (and report back the full output)

Besides I am still waiting, you type alias in a terminal and tell us, whether in the list you may get, you find darktable.

I am not familiar with MINT since I use gentoo. Google tells me, there is synaptics, as a GUI for apt-get. Anyway:

  • could you try to installed dt like so: https://www.youtube.com/watch?v=VAWEm7m5uo8 ??
    (gives you the chance to see messages in between).
  • also I am not sure at all, how your distro guarantees that all dependencies are updated prior installation.
  • so can you make sure, your system is up-to-date or at least all dt-relevant packages are up-to-date (especially gtk+ shall be >=3.14

Here is acc. to my system (maybe not everything relevant for you!) the list af all deps:

BDEPEND="
dev-util/intltool
virtual/pkgconfig
nls? ( sys-devel/gettext )
"
COMMON_DEPEND="
dev-db/sqlite:3
dev-libs/json-glib
dev-libs/libxml2:2
dev-libs/pugixml:0=
gnome-base/librsvg:2
>=media-gfx/exiv2-0.25-r2:0=[xmp]
media-libs/lcms:2
>=media-libs/lensfun-0.2.3:0=
media-libs/libpng:0=
media-libs/tiff:0
net-libs/libsoup:2.4
net-misc/curl
sys-libs/zlib:=
virtual/jpeg:0
x11-libs/cairo
>=x11-libs/gtk±3.14:3
x11-libs/pango
colord? ( x11-libs/colord-gtk:0= )
cups? ( net-print/cups )
flickr? ( media-libs/flickcurl )
geolocation? ( >=sci-geosciences/osm-gps-map-1.1.0 )
gnome-keyring? ( >=app-crypt/libsecret-0.18 )
gphoto2? ( media-libs/libgphoto2:= )
graphicsmagick? ( media-gfx/graphicsmagick )
jpeg2k? ( media-libs/openjpeg:2= )
opencl? ( virtual/opencl )
openexr? ( media-libs/openexr:0= )
webp? ( media-libs/libwebp:0= )
"

I am sure, we make it run, -one day :wink: :smile:

1 Like

Absolutely no offence meant. Didn’t realize I was already in the best place to get help on this.

I did have a cursory look through Linux Mint forums but there weren’t any concluded threads that fit this scenario. There was one very similar where the person was running wrong video drivers, I’m using the correct ones as far as I can tell.

Here is what I’m getting:

jason@Lexington ~ $ darktable -d all
[memory] at startup
[memory] max address space (vmpeak): 331784 kB
[memory] cur address space (vmsize): 331784 kB
[memory] max used memory (vmhwm ): 20096 kB
[memory] cur used memory (vmrss ): 20096 kB
[defaults] found a 64-bit system with 2023956 kb ram and 2 cores (0 atom based)
[defaults] setting very conservative defaults
0.242388 [sql] /build/darktable-6fjxN4/darktable-2.4.4/src/common/collection.c:443, function _dt_collection_compute_count(): prepare “SELECT COUNT(DISTINCT id) FROM main.images WHERE (flags & 256) != 256 and (flags & 7) >= 0 AND (flags & 7) != 6 AND ((film_id IN (SELECT id FROM main.film_rolls WHERE folder LIKE ‘'))) ORDER BY filename, version LIMIT ?1, ?2" 0.243029 [sql] /build/darktable-6fjxN4/darktable-2.4.4/src/common/collection.c:566, function dt_collection_get_selected(): prepare "SELECT DISTINCT id FROM main.images WHERE id IN (SELECT imgid FROM main.selected_images) ORDER BY filename, version LIMIT ?1" 0.244091 [sql] /build/darktable-6fjxN4/darktable-2.4.4/src/common/collection.c:467, function dt_collection_get_selected_count(): prepare "SELECT COUNT(*) FROM main.selected_images" 0.244235 [sql] /build/darktable-6fjxN4/darktable-2.4.4/src/common/collection.c:1207, function dt_collection_update_query(): prepare "DELETE FROM main.selected_images WHERE imgid NOT IN (SELECT DISTINCT id FROM main.images WHERE (flags & 256) != 256 and (flags & 7) >= 0 AND (flags & 7) != 6 AND ((film_id IN (SELECT id FROM main.film_rolls WHERE folder LIKE '’))) ORDER BY filename, version LIMIT ?1, ?2)”
0.244430 [sql] /build/darktable-6fjxN4/darktable-2.4.4/src/common/collection.c:443, function _dt_collection_compute_count(): prepare “SELECT COUNT(DISTINCT id) FROM main.images WHERE (flags & 256) != 256 and (flags & 7) >= 0 AND (flags & 7) != 6 AND ((film_id IN (SELECT id FROM main.film_rolls WHERE folder LIKE ‘%’))) ORDER BY filename, version”
0.244662 [sql] /build/darktable-6fjxN4/darktable-2.4.4/src/common/collection.c:566, function dt_collection_get_selected(): prepare “SELECT DISTINCT id FROM main.images WHERE id IN (SELECT imgid FROM main.selected_images) ORDER BY filename, version LIMIT ?1”
0.244751 [sql] /build/darktable-6fjxN4/darktable-2.4.4/src/common/collection.c:467, function dt_collection_get_selected_count(): prepare "SELECT COUNT() FROM main.selected_images"
0.244816 [pwstorage_new] Creating new context 0x14d2ac0
0.244829 [pwstorage_new] autodetected storage backend.
0.244848 [pwstorage_new] no storage backend. not storing username/password. please change in preferences, core tab.
0.269817 [opencl_init] opencl related configuration options:
0.269842 [opencl_init]
0.269854 [opencl_init] opencl: 1
0.269865 [opencl_init] opencl_library: ‘’
0.269878 [opencl_init] opencl_memory_requirement: 768
0.269892 [opencl_init] opencl_memory_headroom: 300
0.269904 [opencl_init] opencl_device_priority: '
/!0,//*’
0.269917 [opencl_init] opencl_mandatory_timeout: 200
0.269929 [opencl_init] opencl_size_roundup: 16
0.269940 [opencl_init] opencl_async_pixelpipe: 0
0.269950 [opencl_init] opencl_synch_cache: 0
0.269962 [opencl_init] opencl_number_event_handles: 25
0.269975 [opencl_init] opencl_micro_nap: 1000
0.269986 [opencl_init] opencl_use_pinned_memory: 0
0.269997 [opencl_init] opencl_use_cpu_devices: 0
0.270007 [opencl_init] opencl_avoid_atomics: 0
0.270016 [opencl_init]
0.270324 [opencl_init] could not find opencl runtime library ‘libOpenCL’
0.270445 [opencl_init] could not find opencl runtime library ‘libOpenCL.so’
0.271508 [opencl_init] found opencl runtime library ‘libOpenCL.so.1’
0.271568 [opencl_init] opencl library ‘libOpenCL.so.1’ found on your system and loaded

jason@Lexington ~ $ darktable --version
this is darktable 2.4.4
copyright (c) 2009-2018 johannes hanika
darktable-dev@lists.darktable.org

compile options:
bit depth is 64 bit
normal build
SSE2 optimized codepath enabled
OpenMP support enabled
OpenCL support enabled
Lua support enabled, API version 5.0.0
Colord support enabled
gPhoto2 support enabled
GraphicsMagick support enabled
OpenEXR support enabled

jason@Lexington ~ $ pgrep -l darktable

jason@Lexington ~ $ darktable -d all
[memory] at startup
[memory] max address space (vmpeak): 331784 kB
[memory] cur address space (vmsize): 331784 kB
[memory] max used memory (vmhwm ): 19744 kB
[memory] cur used memory (vmrss ): 19744 kB
[defaults] found a 64-bit system with 2023956 kb ram and 2 cores (0 atom based)
[defaults] setting very conservative defaults
0.330245 [sql] /build/darktable-6fjxN4/darktable-2.4.4/src/common/collection.c:443, function _dt_collection_compute_count(): prepare “SELECT COUNT(DISTINCT id) FROM main.images WHERE (flags & 256) != 256 and (flags & 7) >= 0 AND (flags & 7) != 6 AND ((film_id IN (SELECT id FROM main.film_rolls WHERE folder LIKE ‘'))) ORDER BY filename, version LIMIT ?1, ?2" 0.331141 [sql] /build/darktable-6fjxN4/darktable-2.4.4/src/common/collection.c:566, function dt_collection_get_selected(): prepare "SELECT DISTINCT id FROM main.images WHERE id IN (SELECT imgid FROM main.selected_images) ORDER BY filename, version LIMIT ?1" 0.332135 [sql] /build/darktable-6fjxN4/darktable-2.4.4/src/common/collection.c:467, function dt_collection_get_selected_count(): prepare "SELECT COUNT(*) FROM main.selected_images" 0.332261 [sql] /build/darktable-6fjxN4/darktable-2.4.4/src/common/collection.c:1207, function dt_collection_update_query(): prepare "DELETE FROM main.selected_images WHERE imgid NOT IN (SELECT DISTINCT id FROM main.images WHERE (flags & 256) != 256 and (flags & 7) >= 0 AND (flags & 7) != 6 AND ((film_id IN (SELECT id FROM main.film_rolls WHERE folder LIKE '’))) ORDER BY filename, version LIMIT ?1, ?2)”
0.332570 [sql] /build/darktable-6fjxN4/darktable-2.4.4/src/common/collection.c:443, function _dt_collection_compute_count(): prepare “SELECT COUNT(DISTINCT id) FROM main.images WHERE (flags & 256) != 256 and (flags & 7) >= 0 AND (flags & 7) != 6 AND ((film_id IN (SELECT id FROM main.film_rolls WHERE folder LIKE ‘%’))) ORDER BY filename, version”
0.332929 [sql] /build/darktable-6fjxN4/darktable-2.4.4/src/common/collection.c:566, function dt_collection_get_selected(): prepare “SELECT DISTINCT id FROM main.images WHERE id IN (SELECT imgid FROM main.selected_images) ORDER BY filename, version LIMIT ?1”
0.333121 [sql] /build/darktable-6fjxN4/darktable-2.4.4/src/common/collection.c:467, function dt_collection_get_selected_count(): prepare "SELECT COUNT() FROM main.selected_images"
0.333283 [pwstorage_new] Creating new context 0x191f6f0
0.333300 [pwstorage_new] autodetected storage backend.
0.333307 [pwstorage_new] no storage backend. not storing username/password. please change in preferences, core tab.
0.362190 [opencl_init] opencl related configuration options:
0.362216 [opencl_init]
0.362225 [opencl_init] opencl: 1
0.362234 [opencl_init] opencl_library: ‘’
0.362244 [opencl_init] opencl_memory_requirement: 768
0.362255 [opencl_init] opencl_memory_headroom: 300
0.362264 [opencl_init] opencl_device_priority: '
/!0,//*’
0.362274 [opencl_init] opencl_mandatory_timeout: 200
0.362284 [opencl_init] opencl_size_roundup: 16
0.362295 [opencl_init] opencl_async_pixelpipe: 0
0.362303 [opencl_init] opencl_synch_cache: 0
0.362314 [opencl_init] opencl_number_event_handles: 25
0.362323 [opencl_init] opencl_micro_nap: 1000
0.362332 [opencl_init] opencl_use_pinned_memory: 0
0.362341 [opencl_init] opencl_use_cpu_devices: 0
0.362350 [opencl_init] opencl_avoid_atomics: 0
0.362357 [opencl_init]
0.362594 [opencl_init] could not find opencl runtime library ‘libOpenCL’
0.362687 [opencl_init] could not find opencl runtime library ‘libOpenCL.so’
0.366412 [opencl_init] found opencl runtime library ‘libOpenCL.so.1’
0.366481 [opencl_init] opencl library ‘libOpenCL.so.1’ found on your system and loaded

I have to enter CRTL-C to get terminal prompt back

In follow-up to your earlier post:

jason@Lexington ~ ps aux | grep darktable jason 4242 0.0 0.0 14224 1080 pts/0 S+ 10:57 0:00 grep --color=auto darktable jason@Lexington ~ alias | grep darktable
jason@Lexington - $

Removed dt via Mint Software Manager
Then:

jason@Lexington ~ sudo apt-get update [sudo] password for jason: Ign:1 http://mirror.csclub.uwaterloo.ca/linuxmint-packages sylvia InRelease Hit:2 http://mirror.csclub.uwaterloo.ca/ubuntu xenial InRelease Hit:3 http://mirror.csclub.uwaterloo.ca/ubuntu xenial-updates InRelease Ign:4 http://dl.google.com/linux/chrome/deb stable InRelease Hit:5 http://mirror.csclub.uwaterloo.ca/ubuntu xenial-backports InRelease Hit:6 http://mirror.csclub.uwaterloo.ca/linuxmint-packages sylvia Release Hit:7 http://archive.canonical.com/ubuntu xenial InRelease Hit:8 http://security.ubuntu.com/ubuntu xenial-security InRelease Hit:9 http://ppa.launchpad.net/nm-l2tp/network-manager-l2tp/ubuntu xenial InRelease Hit:10 http://dl.google.com/linux/chrome/deb stable Release Hit:11 http://ppa.launchpad.net/pmjdebruijn/darktable-release/ubuntu xenial InRelease Reading package lists... Done jason@Lexington ~

jason@Lexington ~ $ sudo apt-get install darktable -y

Reading package lists… Done
Building dependency tree
Reading state information… Done
The following packages were automatically installed and are no longer required:
gir1.2-gexiv2-0.10 libgexiv2-2 libjs-prototype libjs-scriptaculous libllvm5.0 vpnc-scripts
Use ‘sudo apt autoremove’ to remove them.
Recommended packages:
darktable-dbg
The following NEW packages will be installed:
darktable
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/3,468 kB of archives.
After this operation, 16.4 MB of additional disk space will be used.
Selecting previously unselected package darktable.
(Reading database … 844623 files and directories currently installed.)
Preparing to unpack …/darktable_1%3a2.4.4-0pmjdebruijn1~xenial_amd64.deb …
Unpacking darktable (1:2.4.4-0pmjdebruijn1~xenial) …
Processing triggers for gnome-menus (3.13.3-6ubuntu3.1) …
Processing triggers for desktop-file-utils (0.22+linuxmint1) …
Processing triggers for mime-support (3.59ubuntu1) …
Processing triggers for man-db (2.7.5-1) …
Processing triggers for hicolor-icon-theme (0.15-0ubuntu1.1) …
Setting up darktable (1:2.4.4-0pmjdebruijn1~xenial) …
jason@Lexington ~ $

These I’m not sure of:

  • also I am not sure at all, how your distro guarantees that all dependencies are updated prior installation.
  • so can you make sure, your system is up-to-date or at least all dt-relevant packages are up-to-date (especially gtk+ shall be >=3.14

Linux Mint updates and Software Manager etc manage dependencies as far as I know
I don’t know how to find my gtk+ version

According to everything I can find Linux Mint 18 uses gkt 3.18

Thanks for your continuing help on this.

No worries no offending taken :slight_smile:

darned, I hoped for an error message

Which grafic board you are using and which driver?

can you pls. take a simple editor and edit ~/.config/darktable/darktablerc and change the following:

opencl=TRUE
to
opencl=false
(that is not case sensitive, don’t worry. Indeed later you need opencl, but one by one…)

if you still have the same issue, can you check with the command dmesg in a terminal, whether you see something suspicous?

if that all does not help, I slowly get the feeling your package is broken. In that case try to get an up to date version, maybe thru this channel: