Bug #9664

Darktable crashes on Macos X 10.9.0 in a multiple monitor setup

Added by Herbet Powell over 6 years ago. Updated over 6 years ago.

Start date:
Due date:
% Done:


Estimated time:
Affected Version:
Mac OS X
hardware architecture:


While using latest version of darktable 1.2.3 on MacOS X 10.9.0, if I start darktable on a multiple monitor setup with one of the external monitors being set as primary, I get the following error message followed by a crash:
Application Specific Information:
Client is attempting to access a display by index (2) instead of display ID.
abort() called

darktable_crash_log_on_10.9.0.txt (56.5 KB) darktable_crash_log_on_10.9.0.txt Crash log on Mac OS X with multiple monitors attached Herbet Powell, 11/04/2013 02:26 AM


#1 Updated by Herbet Powell over 6 years ago

The workaround is to start darktable without screen being attached


#2 Updated by fred s over 6 years ago

Another workaround - first "Turn Display Mirroring On", start darktable, then turn mirroring back off. (Note: this may change size/position of any open windows.)

#3 Updated by André Reinald over 6 years ago

It seems the darktable window just doesn't like to stay on the external screen:

Scenario A:
1. Disconnect the external screen
2. Start darktable
3. Reconnect the external screen -> the window automatically moves to the external screen and dt crashes

Scenario B:
1. Disconnect the external screen
2. Start darktable
3. Move the window to some other place
4. Reconnect the external screen -> the window is not automatically repositioned by the system
5. Move the window to the external screen -> dt crashes

In both scenarios, when starting dt from the terminal I get:

lepiote:~ andre$ /Applications/
2013-11-13 16:35:32.978 darktable-bin[90354:d07] *** WARNING: Method userSpaceScaleFactor in class NSView is deprecated on 10.7 and later. It should not be used in new applications. Use convertRectToBacking: instead. 

And when the crash occurs I get:

Abort trap: 6

#4 Updated by Igor Kuzmin over 6 years ago

  • % Done changed from 0 to 50
  • Assignee changed from Developers to Igor Kuzmin
  • Status changed from New to In Progress

should be fixed in master with 8e4743b so upcoming rc1 will work fine with multiple monitor setup on Mavericks. I'm not closing bug report yet, because I would like that more people test my solution. I only tried Mavericks with 1 and 2 monitors, dt seems to get the right profiles. Please test on older OS X versions and different multi monitor setups (like mirroring and such). Pay extra attention if chosen profile are the correct ones (assign some noticeably different profiles to monitors before testing and try changing display profile in output color profile module).

#5 Updated by Herbet Powell over 6 years ago

  • % Done changed from 50 to 100
  • Status changed from In Progress to Fixed

Thanks Igor. I just loaded the RC1.4 on Maverick with my multi screen setup and it works fine.
To me it looks fixed - will reopen if I experience any problem of this nature.

Thanks for fixing this, much appreciated !

Also available in: Atom PDF

Go to top