Hi,
sorry I have to upload this in original size, but the issue only exists when I export to original size.
So, as you can see, darktable 2.7 produced a strange light margin on the right edge. Why is this? Can somebody reproduce this?
Yes, I can (with your xmp file. With my own edits, the export was fine)
And there’s also a temporary file left over after the export (which took forever…):
I would file a bug.
EDIT: Ubuntu 18.04 here.
Oh, you could reproduce the error? Good!
What dt version are you using?
My memory tells me that I have read something about “odd file types”, i.e. a file type sometimes (?!) receives an extra suffix, like the 3037 in your case. I’ll have a look…
Same thing with a RAF file.
EDIT: I mean, I loaded your xmp file into a RAF file.
No, I’m not.
I think DT devs focus more on github issues report and they are very low profile on discuss when it comes to bugs. I wouldn’t wait for them. This is clearly a bug.
I have been thinking about your problem today.
I have read something about odd filetypes from dt, but so far I have not been able to locate any additional info…
What I have done is to fetch the same distro as you are using, to see “with my own fingers” what is happening. That was a bad idea, since MX Linux 19 refuses to load on my machine (I have too modern a gfx)
I then tried to approach your problem from another angle:
Your history stack has about 40 levels.
You have very many created shapes…
Please start darktable from a terminal, using the command darktable. Open the offending photo in darkroom.
Do you get a lot of lines (in the terminal window) saying something like gamma is not the last iop?
Using the offending photo, in darkroom, please click compress history stack. Close darktable and open it again, select the offending photo. Still a problem?
Present darktable-git has a version number of 2.7.0+2112, I believe, which makes yours a trifle old. From where did you get your dt 2.7.0?
yes, I did all the things that you suggested, no change
in addition, I installed the newest git master version on a new (debian testing) system, still no change
Any reason to choose compiling instead of adding dev packages to your os?
I’m saying this because it’s much easier to keep your dev version up-to-date, instead of compiling each time they change the code (which is almost on a daily base).
Unless you want to dig deeper into debugging and sending dumps to the devs each time you face a bug.
