There have been multiple serious issues reported for 5.0.0 of bugs that crash DT (see GitHub Issues) when “simple” basic operations are conducted (e.g. just browsing LT). Not being familiar about how the work is planned, I would like to know if work priorities for Dev have been establish to first fix these serious bugs before working on new features, thus creating a 5.0.1 ? Any roughly estimated date for such a bug fix release ? Thx for all the good work and the time + energy invested .
The first thing is to follow these and see if they are confirmed…Lot’s of people do report bugs and esp in the Facebook forum all kinds of people update and then complain about a whole array of things only to find that something was amiss on their end… I use 5.1.0+26~ge4b105e80f which is simply the current code changes since 5.0 release in the master branch of the code…and using my system and windows I have not had any such crashes…so I think many times unless you get multiple reports to confirm if the issue is tied to some certain hardware or images then you can’t really say 5.0 is buggy…not to say that there are not bugs… but so far no issues at all for me…
I would say to most people run DT with fresh set of config files by just running an instance with --configdir and point that to a blank directory…if everything works okay then its not the software or the install but something in the update has not gone smoothly…
1 Like
Work is largely not planned. If a Dev thinks they can fix the issue, they may. Or they may not.
The issue we see often is that people report bugs, but the bug reports are of low quality. If a developer can’t replicate the issue, then the chances of it getting fixed are relatively small.
I can also relate - I run latest source code with relatively fresh config and did not experience any problems (so far).
1 Like
Thx for answering. In GitHub the crashes have been confirmed by multiple people, with logs provided . In my case, it was doing OK with 4.8.1, so 5.0.0 introduced the bugs. Granted, it may be difficult to find, so I am not complaining. For simple users like us, what can we do, else than reporting the problems ? I am available to try to test and pinpoint more precisely the nature of the bug (the one that crash DT when just browsing the LightTable). Thx
I understand. So, I have to interest a dev to fix my problem, since everything is made on a pure voluntary basis. But since we all care abut DT, I presume its stability becomes important. Anyway, thx.
If the bug report is good and reproducible, it’ll likely get fixed. The crap part of fixing things is chasing down the problem.
2 Likes
Try running DT with fresh config files…if its fine then your database likely didn’t upgrade properly or maybe its a hardware issue… I saw one issue on github but it got conflated by another poster talking about crashes when selecting missing files…I think this one has been split now to focus on that …in any case its never easy when things don’t go smoothly and so I feel your frustration. I have not had such an experience and perhaps I have missed something but I don’t see widespread issues with LT scrolling so hopefully your’s can be narrowed down…do you have the ability to install it on a second machine…this could also reveal if the issue is linked to your one specific device/install…
For anyone that don’t know how to report a bug so that the devs can act on it, I recommend reading this first:
https://www.chiark.greenend.org.uk/~sgtatham/bugs.html
Sometimes even having logs is not enough to figure out what the issue is and further investigation is needed.
Sure I will do. I am not frustrated at all, I develop my self full open source software, I know how devs feel and I surely very strongly appreciate their time and effort. Just want to have DT the best experience ever, as I use it extensively and find it is the best RAW processor available. I will help to find this bug and report back to the GtHub issue # opened. Thx again !
3 Likes
I think quite a few of these bugs are very system-specific – darktable 5.0 (as with previous versions for the last few years) has been rock-solid for me. Certainly some of the more serious-looking crashes (like the lighttable browsing crash) seem to be wayland-specific (or maybe Windows), and are probably getting less attention because most of the developers use Linux/x11 (due to issues with screen calibration on wayland).
So I’d guess the reason there’s no rush for 5.0.1 release is that these issues are not affecting everyone. Generally there’s a bug fix release a month or two after the feature release, unless there’s a major issue affecting lots of people.
Can you provide a link to the issue you raised in GitHub?
@lfsimsym I wonder what OS you are on. I use DT 5.1 weekly builds supplied for Windows here each week. It has been rock solid for me except when sometimes I was demonstrating to students while connected to a data projector and sometimes it crashed. I presumed that was a resource issue because back at home it was stable again.
I think it must be this one…
I think he could answer.
The OP’s problem is different that the rest that chimed in. The later “reporters” deleted images that darktable knew about outside of darktable, and now they are trying to use darktable to delete the images that they’ve already deleted, and darktable crashes because the image doesn’t exist anymore.
I tried explaining but…
EDIT: 5.0.1 is tentatively scheduled for February…
2 Likes
Exactly, that is what I mean in my earlier comment when I said the issue got conflated.
1 Like
but even that isn’t a general issue 
This bug (18137) is for Mint 22 on X11