Re: [darktable-dev] denoise(profiled) problems
Hello Tobias, On Sat, 12 Aug 2017 08:52:18 +1000, Terry Duell wrote: [snip] -- Missing jsonschema, problems in noiseprofiles.json might go unnoticed which may relate to my problems. I have json-glib-devel installed, but can't find any reference to jsonschema in Fedora 26 repos. Any thoughts on this? Finally figured this out, jasonschema now found and new build installed, so now to see if problems go away. Thanks for your help, and sorry for any unnecessary diversions. Cheers, -- Regards, Terry Duell ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] denoise(profiled) problems
Hello Tobias, On Sat, 12 Aug 2017 08:30:02 +1000, Tobias Ellinghaus wrote: Am Samstag, 12. August 2017, 08:14:39 CEST schrieb Terry Duell: [snip] yes, I have gdb. It's possible a dt crash report is in /tmp, but nothing has a name that would suggest it was from dt. What typical naming would a dt crash report have? darktable_bt_XX.txt with the X replaced by some random characters. Maybe your /tmp/ is getting wiped at reboot so the backtrace got lost? Or it wasn't a real crash (I didn't see a SIGSEGV IIRC). What you can do is running darktable from within gdb and when it crashes copy&paste this to the console: set pagination off set logging file gdb.txt set logging on where echo \n=\n\n info threads echo \n=\n thread apply all bt full Then send the gdb.txt file. Thanks for that. I'll do all that shortly if necessary. I have just been checking the the output from rpmbuild for a new build, and I see the following message... -- Missing jsonschema, problems in noiseprofiles.json might go unnoticed which may relate to my problems. I have json-glib-devel installed, but can't find any reference to jsonschema in Fedora 26 repos. Any thoughts on this? Cheers, -- Regards, Terry Duell ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] denoise(profiled) problems
Am Samstag, 12. August 2017, 08:14:39 CEST schrieb Terry Duell: > Hello Tobias, > > On Fri, 11 Aug 2017 17:44:47 +1000, Tobias Ellinghaus wrote: > > Am Freitag, 11. August 2017, 08:46:26 CEST schrieb Terry Duell: > >> No sign of anything in /tmp that looks like a crash report related to > >> dt. > > > > Too bad. Do you have "gdb" installed? > > yes, I have gdb. > It's possible a dt crash report is in /tmp, but nothing has a name that > would suggest it was from dt. > What typical naming would a dt crash report have? darktable_bt_XX.txt with the X replaced by some random characters. Maybe your /tmp/ is getting wiped at reboot so the backtrace got lost? Or it wasn't a real crash (I didn't see a SIGSEGV IIRC). What you can do is running darktable from within gdb and when it crashes copy&paste this to the console: set pagination off set logging file gdb.txt set logging on where echo \n=\n\n info threads echo \n=\n thread apply all bt full Then send the gdb.txt file. > Cheers, Tobias signature.asc Description: This is a digitally signed message part.
Re: [darktable-dev] denoise(profiled) problems
Hello Tobias, On Fri, 11 Aug 2017 17:44:47 +1000, Tobias Ellinghaus wrote: Am Freitag, 11. August 2017, 08:46:26 CEST schrieb Terry Duell: No sign of anything in /tmp that looks like a crash report related to dt. Too bad. Do you have "gdb" installed? yes, I have gdb. It's possible a dt crash report is in /tmp, but nothing has a name that would suggest it was from dt. What typical naming would a dt crash report have? Cheers, -- Regards, Terry Duell ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] denoise(profiled) problems
Am Freitag, 11. August 2017, 08:46:26 CEST schrieb Terry Duell: > Hello Tobias, > > On Thu, 10 Aug 2017 18:35:07 +1000, Tobias Ellinghaus wrote: > > [snip] > > >> I didn't manage to reproduce the denoise issue, but did dt did > >> crash...something that has happened before but it has been random. > > > > When dt crashes it tries to write a crash report in /tmp/. If you can > > find such > > files I'd be interested in them. > > No sign of anything in /tmp that looks like a crash report related to dt. Too bad. Do you have "gdb" installed? > >> Attached text file is the contents of the terminal output. > > > > That indicates something is wrong with your noise profiles file. Please > > start dt > > like this and see what it prints: > > > > darktable -d control | grep noiseprofile > > OK, output attached. That looks fine. No idea then where the errors were coming from ... > Cheers, Tobias signature.asc Description: This is a digitally signed message part.
Re: [darktable-dev] denoise(profiled) problems
Hello Tobias, On Thu, 10 Aug 2017 18:35:07 +1000, Tobias Ellinghaus wrote: [snip] I didn't manage to reproduce the denoise issue, but did dt did crash...something that has happened before but it has been random. When dt crashes it tries to write a crash report in /tmp/. If you can find such files I'd be interested in them. No sign of anything in /tmp that looks like a crash report related to dt. Attached text file is the contents of the terminal output. That indicates something is wrong with your noise profiles file. Please start dt like this and see what it prints: darktable -d control | grep noiseprofile OK, output attached. Cheers, -- Regards, Terry Duell ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org[terry@localhost ~]$ darktable -d control | grep noiseprofile ** (darktable:2548): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-NzYb7hnXNU: Connection refused [noiseprofile] loading noiseprofiles from `/usr/share/darktable/noiseprofiles.json' [noiseprofile] verifying noiseprofile file [noiseprofile] found 12 makers [noiseprofile] found maker `Canon' [noiseprofile] found 53 models [noiseprofile] found PowerShot S100 [noiseprofile] found 20 profiles [noiseprofile] found PowerShot SX100 IS [noiseprofile] found 18 profiles [noiseprofile] found EOS M3 [noiseprofile] found 19 profiles [noiseprofile] found EOS M5 [noiseprofile] found 25 profiles [noiseprofile] found PowerShot G3 X [noiseprofile] found 21 profiles [noiseprofile] found PowerShot G7 X [noiseprofile] found 111 profiles [noiseprofile] found PowerShot G7 X Mark II [noiseprofile] found 21 profiles [noiseprofile] found PowerShot G9 X Mark II [noiseprofile] found 21 profiles [noiseprofile] found EOS 1200D [noiseprofile] found 7 profiles [noiseprofile] found EOS 1000D [noiseprofile] found 5 profiles [noiseprofile] found EOS 1100D [noiseprofile] found 7 profiles [noiseprofile] found EOS-1D Mark II [noiseprofile] found 32 profiles [noiseprofile] found EOS-1D Mark III [noiseprofile] found 25 profiles [noiseprofile] found EOS-1D Mark IV [noiseprofile] found 24 profiles [noiseprofile] found EOS-1Ds Mark II [noiseprofile] found 14 profiles [noiseprofile] found EOS-1D X [noiseprofile] found 14 profiles [noiseprofile] found EOS 20D [noiseprofile] found 6 profiles [noiseprofile] found EOS 30D [noiseprofile] found 14 profiles [noiseprofile] found EOS 350D [noiseprofile] found 5 profiles [noiseprofile] found EOS 400D [noiseprofile] found 10 profiles [noiseprofile] found EOS 40D [noiseprofile] found 14 profiles [noiseprofile] found EOS 450D [noiseprofile] found 5 profiles [noiseprofile] found EOS 500D [noiseprofile] found 6 profiles [noiseprofile] found EOS 50D [noiseprofile] found 18 profiles [noiseprofile] found EOS 550D [noiseprofile] found 15 profiles [noiseprofile] found EOS 5D [noiseprofile] found 14 profiles [noiseprofile] found EOS 5D Mark II [noiseprofile] found 31 profiles [noiseprofile] found EOS 5D Mark III [noiseprofile] found 24 profiles [noiseprofile] found EOS 5D Mark IV [noiseprofile] found 29 profiles [noiseprofile] found EOS 5DS R [noiseprofile] found 7 profiles [noiseprofile] found EOS 5DS [noiseprofile] found 7 profiles [noiseprofile] found EOS 600D [noiseprofile] found 8 profiles [noiseprofile] found EOS 60D [noiseprofile] found 20 profiles [noiseprofile] found EOS 650D [noiseprofile] found 9 profiles [noiseprofile] found EOS 6D [noiseprofile] found 28 profiles [noiseprofile] found EOS 700D [noiseprofile] found 9 profiles [noiseprofile] found EOS 70D [noiseprofile] found 22 profiles [noiseprofile] found EOS 80D [noiseprofile] found 24 profiles [noiseprofile] found EOS 7D [noiseprofile] found 20 profiles [noiseprofile] found EOS 7D Mark II [noiseprofile] found 25 profiles [noiseprofile] found EOS M [noiseprofile] found 26 profiles [noiseprofile] found EOS 100D [noiseprofile] found 9 profiles [noiseprofile] found PowerShot G9 [noiseprofile] found 6 profiles [noiseprofile] found PowerShot G10 [noiseprofile] found 26 profiles [noiseprofile] found PowerShot G11 [noiseprofile] found 7 profiles [noiseprofile] found PowerShot G12 [noiseprofile] found 17 profiles [noiseprofile] found PowerShot G15 [noiseprofile] found 70 profiles [noiseprofile] found PowerShot S90 [noiseprofile] found 17 profiles [noiseprofile] found PowerShot S95 [noiseprofile] found 17 profiles [noiseprofile] found PowerShot S120 [noiseprofile] found 23 profiles [noiseprofile] found PowerShot SX50 HS [noiseprofile] found 20 profiles [noiseprofile] found PowerShot SX60 HS [noiseprofile] found 16 profiles [noiseprofile] found PowerShot SX510 HS [noiseprofile] found 7 profiles [noiseprofile] found maker `Fujifilm' [noiseprofile] found 14 models [noiseprofile] found X-T2 [noiseprofile] found 21 profiles [noiseprofile] found X70 [noiseprofile] found 16 profiles [noiseprofile] found X
Re: [darktable-dev] denoise(profiled) problems
Am Donnerstag, 10. August 2017, 09:57:26 CEST schrieb Terry Duell: > Hello Tobias, > > On Wed, 09 Aug 2017 18:19:04 +1000, Tobias Ellinghaus wrote: > > Am Mittwoch, 9. August 2017, 09:20:58 CEST schrieb Terry Duell: > >> Hello All, > > > > Hi. > > > >> I'm running a local build of the current master on Fedora 26. Noise > >> profiles exist for my cameras. > >> I use the denoise (profiled) and dt reports "found match for ISO 800" or > >> similar, and it works well, but sometimes when going back to look again > >> at > >> images already PP'd the quality of the image is poor and denoise > >> (profiled) is saying "generic poissonian", and the camera profiles are > >> no > >> accessible. If I kill dt and restart, all is OK again until some > >> (random) > >> time later when it reverts again. > >> Not a lot of helpful detail here I know, and any suggestions as what I > >> might do to provide more useful info appreciated. > > > > Try running dt from a terminal and see if there are any errors reported. > > Thanks, I should have thought of that. > > I didn't manage to reproduce the denoise issue, but did dt did > crash...something that has happened before but it has been random. When dt crashes it tries to write a crash report in /tmp/. If you can find such files I'd be interested in them. > Attached text file is the contents of the terminal output. That indicates something is wrong with your noise profiles file. Please start dt like this and see what it prints: darktable -d control | grep noiseprofile > Cheers, Tobias signature.asc Description: This is a digitally signed message part.
Re: [darktable-dev] denoise(profiled) problems
Hello Tobias, On Wed, 09 Aug 2017 18:19:04 +1000, Tobias Ellinghaus wrote: Am Mittwoch, 9. August 2017, 09:20:58 CEST schrieb Terry Duell: Hello All, Hi. I'm running a local build of the current master on Fedora 26. Noise profiles exist for my cameras. I use the denoise (profiled) and dt reports "found match for ISO 800" or similar, and it works well, but sometimes when going back to look again at images already PP'd the quality of the image is poor and denoise (profiled) is saying "generic poissonian", and the camera profiles are no accessible. If I kill dt and restart, all is OK again until some (random) time later when it reverts again. Not a lot of helpful detail here I know, and any suggestions as what I might do to provide more useful info appreciated. Try running dt from a terminal and see if there are any errors reported. Thanks, I should have thought of that. I didn't manage to reproduce the denoise issue, but did dt did crash...something that has happened before but it has been random. Attached text file is the contents of the terminal output. Cheers, -- Regards, Terry Duell ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org[terry@localhost ~]$ darktable ** (darktable:5299): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-FyKwFHG2Xl: Connection refused [export_job] exported to `/home/terry/Pentax-K-1/2017/Ella/100_0908/darktable_exported/IMG09385.jpg' [export_job] exported to `/home/terry/Pentax-K-1/2017/Ella/100_0908/darktable_exported/IMG09409.jpg' [export_job] exported to `/home/terry/Pentax-K-1/2017/Ella/100_0908/darktable_exported/IMG09415.jpg' (darktable:5299): Json-CRITICAL **: json_object_ref: assertion 'object->ref_count > 0' failed (darktable:5299): Json-CRITICAL **: json_object_has_member: assertion 'object != NULL' failed (darktable:5299): Json-CRITICAL **: json_object_ref: assertion 'object->ref_count > 0' failed (darktable:5299): Json-CRITICAL **: json_object_has_member: assertion 'object != NULL' failed (darktable:5299): Json-CRITICAL **: json_object_ref: assertion 'object->ref_count > 0' failed (darktable:5299): Json-CRITICAL **: json_object_has_member: assertion 'object != NULL' failed (darktable:5299): Json-CRITICAL **: json_object_ref: assertion 'object->ref_count > 0' failed (darktable:5299): Json-CRITICAL **: json_object_has_member: assertion 'object != NULL' failed (darktable:5299): Json-CRITICAL **: json_object_ref: assertion 'object->ref_count > 0' failed (darktable:5299): Json-CRITICAL **: json_object_has_member: assertion 'object != NULL' failed (darktable:5299): Json-CRITICAL **: json_object_ref: assertion 'object->ref_count > 0' failed (darktable:5299): Json-CRITICAL **: json_object_has_member: assertion 'object != NULL' failed (darktable:5299): Json-CRITICAL **: json_object_ref: assertion 'object->ref_count > 0' failed (darktable:5299): Json-CRITICAL **: json_object_has_member: assertion 'object != NULL' failed (darktable:5299): Json-CRITICAL **: json_object_ref: assertion 'object->ref_count > 0' failed (darktable:5299): Json-CRITICAL **: json_object_has_member: assertion 'object != NULL' failed (darktable:5299): Json-CRITICAL **: json_object_ref: assertion 'object->ref_count > 0' failed (darktable:5299): Json-CRITICAL **: json_object_has_member: assertion 'object != NULL' failed (darktable:5299): Json-CRITICAL **: json_object_ref: assertion 'object->ref_count > 0' failed (darktable:5299): Json-CRITICAL **: json_object_has_member: assertion 'object != NULL' failed (darktable:5299): Json-CRITICAL **: json_object_ref: assertion 'object->ref_count > 0' failed (darktable:5299): Json-CRITICAL **: json_object_has_member: assertion 'object != NULL' failed (darktable:5299): Json-CRITICAL **: json_object_ref: assertion 'object->ref_count > 0' failed (darktable:5299): Json-CRITICAL **: json_object_has_member: assertion 'object != NULL' failed (darktable:5299): Json-CRITICAL **: json_object_ref: assertion 'object->ref_count > 0' failed (darktable:5299): Json-CRITICAL **: json_object_has_member: assertion 'object != NULL' failed (darktable:5299): Json-CRITICAL **: json_object_ref: assertion 'object->ref_count > 0' failed (darktable:5299): Json-CRITICAL **: json_object_has_member: assertion 'object != NULL' failed (darktable:5299): Json-CRITICAL **: json_object_ref: assertion 'object->ref_count > 0' failed (darktable:5299): Json-CRITICAL **: json_object_has_member: assertion 'object != NULL' failed (darktable:5299): Json-CRITICAL **: json_object_ref: assertion 'object->ref_count > 0' failed (darktable:5299): Json-CRITICAL **: json_object_has_member: assertion 'object != NULL' failed (darktable:5299): Json-CRITICAL **: json_object_ref: assertion 'object->ref_count > 0' failed (darktable:5299): Json-CRITICAL **:
Re: [darktable-dev] denoise(profiled) problems
Am Mittwoch, 9. August 2017, 09:20:58 CEST schrieb Terry Duell: > Hello All, Hi. > I'm running a local build of the current master on Fedora 26. Noise > profiles exist for my cameras. > I use the denoise (profiled) and dt reports "found match for ISO 800" or > similar, and it works well, but sometimes when going back to look again at > images already PP'd the quality of the image is poor and denoise > (profiled) is saying "generic poissonian", and the camera profiles are no > accessible. If I kill dt and restart, all is OK again until some (random) > time later when it reverts again. > Not a lot of helpful detail here I know, and any suggestions as what I > might do to provide more useful info appreciated. Try running dt from a terminal and see if there are any errors reported. > Cheers, Tobias signature.asc Description: This is a digitally signed message part.
