Darktable on Windows (Partha's Build Thread)

Partha Bagchi recently announced on Google+ (here ) that he had a Windows build of darktable for people to test out for him. A bunch of folks stepped up to the plate to help out.

I am starting this thread on the forum b/c the only mechanism to report issues to Partha was through email, which means many of us who may have the same problem cannot easily check if we should report it again or not.

Hopefully Partha joins the community to talk with us here (he can definitely see this post w/o an account though).

So, if you downloaded Partha’s build of darktable for windows (available here) and have run into any problems, please report them in this thread!

2 Likes

To kick things off, I ran into a very simple problem: crash on startup!

Windows 7 Professional, SP1

I get a crash immediately on startup. The log shows nothing out of the ordinary:

Started Darktable on Tue Jul 21 14:29:53 2015

######################################################
The current working directory is C:\Program Files\Darktable-1.6
Darktable version is 1.6.7
######################################################
ALLUSERSPROFILE=C:\ProgramData
APPDATA=C:\Users\patrickd\AppData\Roaming
CLASSPATH=.;C:\Program Files (x86)\Java\jre7\lib\ext\QTJava.zip
CM2014DIR=C:\Program Files (x86)\Common Files\Autodesk Shared\Materials
CommonProgramFiles=C:\Program Files\Common Files
CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files
CommonProgramW6432=C:\Program Files\Common Files
COMPUTERNAME=PATRICKD
ComSpec=C:\Windows\system32\cmd.exe
DellClientSystemUpdatePath=C:\Program Files (x86)\Dell\ClientSystemUpdate
FP_NO_HOST_CHECK=NO
HOMEDRIVE=C:
HOMEPATH=\Users\patrickd
ILBDIR=C:\Program Files (x86)\Common Files\Autodesk Shared\Materials
LOCALAPPDATA=C:\Users\patrickd\AppData\Local
LOGONSERVER=\MASTER
NUMBER_OF_PROCESSORS=8
OS=Windows_NT
PATH=C:\Program Files\Darktable-1.6;C:\Program Files\Darktable-1.6\bin;C:\Program Files\Darktable-1.6\Frameworks;
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC;.RB;.RBW
PROCESSOR_ARCHITECTURE=AMD64
PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 45 Stepping 7, GenuineIntel
PROCESSOR_LEVEL=6
PROCESSOR_REVISION=2d07
ProgramData=C:\ProgramData
ProgramFiles=C:\Program Files
ProgramFiles(x86)=C:\Program Files (x86)
ProgramW6432=C:\Program Files
PSModulePath=C:\Windows\system32\WindowsPowerShell\v1.0\Modules;C:\Program Files (x86)\Microsoft SQL Server\110\Tools\PowerShell\Modules
PUBLIC=C:\Users\Public
QTJAVA=C:\Program Files (x86)\Java\jre7\lib\ext\QTJava.zip
SESSIONNAME=Console
SystemDrive=C:
SystemRoot=C:\Windows
TEMP=C:\Users\patrickd\AppData\Local\Temp
TMP=C:\Users\patrickd\AppData\Local\Temp
USERDNSDOMAIN=DOMAIN.COM
USERDOMAIN=DOMAIN
USERNAME=patrickd
USERPROFILE=C:\Users\patrickd
VBOX_MSI_INSTALL_PATH=C:\Program Files\Oracle\VirtualBox
windir=C:\Windows
windows_tracing_flags=3
windows_tracing_logfile=C:\BVTBin\Tests\installpackage\csilogfile.log
WXCFG=gcc_dll\mswu
WXWIN=C:\wxWidgets-2.9.5
######################################################
Starting Darktable …

When the crash occurs, windows also gives this information from the View problem details:

Problem signature:
Problem Event Name: APPCRASH
Application Name: darktable.exe
Application Version: 0.0.0.0
Application Timestamp: 00000000
Fault Module Name: libdarktable.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c000001d
Exception Offset: 000000000001708f
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 9060
Additional Information 2: 9060a8519f5eb69a759f82d30e7facaa
Additional Information 3: 55d3
Additional Information 4: 55d36aab3db9ae46567578be1d906129

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Please do the following:

  1. Uninstall the previous version using your control panel.
  2. Re-download from the same location.
  3. Reinstall.

Please provide feedback and crashlogs if you can.

Thanks!
Partha

Please be aware that these builds are happening against the will of the
darktable developers, so while we can’t stop anyone we will not listen to any
bug reports or complaints and consider this endeavor a hostile move.

My intention is not to be “against anyone’s wishes”. There was a huge blog article on the Darktable website about Window’s users not stepping up to build Darktable for Windows or reporting bugs. So I stepped up.

The dev-mailing list has been down for almost a week and I stated up front that I wanted to discuss with the developers.

If you are a developer and feel that Window’s Users should not have Darktable, please say so and don’t say that Window’s Users don’t step up with “simple builds” etc.

Thanks,
Partha

2 Likes

I already answered you in our blog which you never reacted to:
http://www.darktable.org/2015/07/why-dont-you-provide-a-windows-build/comment-page-1/#comment-46412

Every time I posted something on the blog, it was rejected silently.

1 Like

I think there may be some crossed communications that I’d hate to see spiral out of hand…

I understand dt’s concern about having an active maintainer for a win build, vs. a packager. From what I understand they’d like to have someone actively maintaining a win version and able to contribute to that maintenance.

I can understand that part of the problem is the worry that someone will build dt, get a bunch of windows users on board (and all the associated bad things that the devs are worried about - more on that shortly), and then possibly leave or stop maintaining the build. Leaving many angry users hanging and possibly flooding any support channels they have…

I think the general perception of the last post was that the only thing lacking for a proper win port was a developer willing to be a maintainer (more on that in a sec).

So I guess, the questions are:

  1. Will dt support a win port at all?
  2. If yes, then can the dt team clarify exactly what their expectations of what a proper maintainer would be in their expectations?
    This way, assuming dt is ok with a win port at all, it’s well understood ahead of time what is expected from someone willing to step up (avoiding any misunderstandings or unpleasantness).

About those windows users…

I know there’s some concern generally about the quality of user in terms of project feedback and bug-reporting, but I’d hazard a guess that early on the people using a win dt would most likely be more tech savvy than an average win user? Hopefully this could mean that more quality bug reporting and issues could be expected at a time when the port would be most fragile and benefit from better quality reporting (early).

5 Likes

Pat,

I responded here because I was not aware of Mr. Houz’s comments on the DT blog. So, I visited it this morning and noted his comment.

Now I do see that he was asking whether I’ll be willing to maintain it. He also says that the Window’s builds are trivial. So, I am at a loss exactly what is required since he is already building for Windows? Now I am confused.

I am happy to provide Windows builds as a service and maintain my builds as I do with GIMP. Also, for GIMP I ask people to report issues to me.

Anyway, I don’t understand the hostility. Well, it’s his code and I suppose he is entitled to it.

Thanks,
Partha

1 Like

I didn’t find a way to respond. There is a reply button under my post while none under yours.

So, here is my response:

As I mentioned, I am happy to build for Windows and also get Users to provide their feedback to me as I do for GIMP. I am not fine that you insult the first person who comes across your blog post and then steps up to build for Windows.

You know that I’m personally appreciative of the work you do with this, and I think that @houz is simply being cautious. (Perhaps a little overzealous in his caution, but it’s coming from a good place). The problem is simply that the team doesn’t have the manpower to effectively handle a possible flood of incoming support and bugs, and they are (rightfully) concerned about being able to handle the input with the scary possibility of little in terms of giving back to the project.

I think some more discussions with the dt team would help clarify their willingness to consider supporting a path forward. While I personally think it would be great to be able to offer win users good alternatives to commercial software from the open world, I am also ok with continuing to use dt in a VM when needed (it’s like my OS penance… - at least there’s an OSX build for home).

Let’s see if they might consider supporting some effort going forward.

Darktable 2.0 Windows 64 bit (Jan 23, 2016)

Also, looks like @partha won’t be making any more darktable builds after 2.0, see the post here: http://www.partha.com/

It’s also possible to run darktable in Windows 10 now with WSL (Windows subsystem for Linux), and an X-server for windows like Xming. Which is pretty awesome. :slight_smile: (Wonder if I should write an article…)

Why would I need an X-server for windows. Can’t the app use Windows Explorer?

Where can I get a copy of the 2.0 darktable build that partha created. The link above is broken

So, if you downloaded Partha’s build of darktable for windows (available here659) and have run into any problems, please report them in this thread!

http://www.partha.com/temp/Darktable-2.0-64bit.exe

Please note that this particular build of darktable is old, unsupported and not looked upon kindly by the dt team. There is a possibility of a windows port in the future, and this path is a dead end.

https://www.mail-archive.com/darktable-dev@lists.darktable.org/msg01785.html

If you must have darktable at the moment on windows, you can try it with WSL and Xming, but please don’t bug the devs about bugs or problems using this method - as it’s also unsupported. (If you do go this route, at least update your WSL install to Ubuntu 16.04 first, btw).

Thank you @patdavid I am aware that the devs get pretty mad when anyone mentioned darktable for Windows. I am going to try the WSL method.

Cool thanks I downloaded it and a cursory look seems it does run on Windows 7

The hostile build 2.0 is admirably stable and efficient both on Win7 and Win10.