DK 2.8.0 / Piicasa crashes during eport
Locked
DK 2.8.0 / Piicasa crashes during eport
 
|
Hello,
I think I found a litle Problem: I tried to export some Pics from DK to Picasa into an existing album. When I mark a picture, which is already existing in the targetalbum, DK will crash, but if I mark only new pics, it works as expected. In DK 2.7.0 there was no problem with picasa-export and dublettes. My System: (K)Ubuntu 12.04 LTS with actual patches and fixes Greets, Christoph _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Puzzling, and troubling, issue with empty folders
|
|
All,
About a year ago I suffered a catastrophic drive issue. I was able to recover images from the drive with appropriate tools. Glad to have images recovered, yes, but the recovery application named the recovered imaged with a multi-digit name. As such, they were relatively useless. Had no idea what the images were, when they were from, etc. Using exiftool I was able to rename the files and at the same time organize them using the exif data they contain. Once I was done with the renaming, I had multiple folders organized by year/month/day, with images named using this format: DSCN_YYYYMMDDTHHMMSS.ext. I was able to use Digikam to find and eliminate duplicates, of which there were hundreds, as well as thumbnails. I've been very happy with Digikam, but recently I've noticed something very puzzling. Given the way the renaming process works (I use Linux and I have a shell script that uses the commandline applications, exiftool and install, to do the renaming) I know, without doubt, that if there is a folder in my collection in the year/month hierarchy for any day in any month in any year, that the folder can only exist because the script, well exiftool in the script, **read data from an existing image** and used that data to create, with the install program, the folder the image was then put into by the install application. But now, I have discovered over the past several days while reviewing images for a contest submission that I have over 50 zero-file folders in my collection. I am very troubled by this. I have deleted practically no image unless I knew they were duplicate images (in fact, I used Digikam itself to identify the duplicates and I reviewed them visually and deleted duplicates only when I could see in Digikam the two images side-by-side). I have nearly seven good years worth of images. And suddenly I see holes in my collection and I have no way of knowing just how significant the holes may be. The year 2008 does not count in the matter as I know I lost many of them several years ago (failed CD backup). But having 50+ folders with zero files in them makes me very worried. Is Digikam somehow involved? Digikam is the only application I use to manage my collection since I stopped using Picasa a year ago. I still use my commandline tools, in the script, to move images from camera SD cards to my collection where Digikam has, thus far, had no problem finding them. I have over 22000 images. Is this a problem? Here is what I see: 2012 has 1 empty folder 2011 has 2 empby folders 2010 had 4 empty folders 2009 has 17 empty folders! 2008 has 5 emtpy folders 2007 has 1 empty folder 2006 has 7 empty folders 2005 has 8 empty folders 2004 has 3 of 4 total empty 2003 has 5 empty folders So, that's the report. What can I do? Is there any record kept by Digikam of its activities I can check? Has anyone else experienced sudden unusual mysterious vanishments? I'm worried. Thanks for any help anyone can give. -- "There is only love, and then oblivion. Love is all we have to set against hatred." (paraphrased) Ian McEwan Guy Stalnaker [hidden email] _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Puzzling, and troubling, issue with empty folders
|
|
Hi Guy,
I've been using DigiKam for 3 years now and never experienced any unintentional disappearing fotos. For backup, I use "Unison File Synchronizer" (http://www.cis.upenn.edu/~bcpierce/unison/), which lists every changed file, before copiing it to the backup storage. Unfortunately it does not tell, what exactly changed. Great would be something like: Change: myfile.jpg (added Tag: "Family") BTW: Does somebody else know a free tool, which could do this? Maybe using unison (or a similar backup tool), you could detect disappearing fotos in the future. Regards, Peter Albrecht On 17.08.2012 07:04, Guy Stalnaker wrote: > All, > > About a year ago I suffered a catastrophic drive issue. I > was able to recover images from the drive with appropriate > tools. Glad to have images recovered, yes, but the recovery > application named the recovered imaged with a multi-digit > name. As such, they were relatively useless. Had no idea > what the images were, when they were from, etc. > > Using exiftool I was able to rename the files and at the > same time organize them using the exif data they contain. > Once I was done with the renaming, I had multiple folders > organized by year/month/day, with images named using this > format: DSCN_YYYYMMDDTHHMMSS.ext. > > I was able to use Digikam to find and eliminate duplicates, > of which there were hundreds, as well as thumbnails. > > I've been very happy with Digikam, but recently I've noticed > something very puzzling. Given the way the renaming process > works (I use Linux and I have a shell script that uses the > commandline applications, exiftool and install, to do the > renaming) I know, without doubt, that if there is a folder > in my collection in the year/month hierarchy for any day in > any month in any year, that the folder can only exist > because the script, well exiftool in the script, **read data > from an existing image** and used that data to create, with > the install program, the folder the image was then put into > by the install application. > > But now, I have discovered over the past several days while > reviewing images for a contest submission that I have over > 50 zero-file folders in my collection. I am very troubled by > this. I have deleted practically no image unless I knew they > were duplicate images (in fact, I used Digikam itself to > identify the duplicates and I reviewed them visually and > deleted duplicates only when I could see in Digikam the two > images side-by-side). I have nearly seven good years worth > of images. And suddenly I see holes in my collection and I > have no way of knowing just how significant the holes may > be. The year 2008 does not count in the matter as I know I > lost many of them several years ago (failed CD backup). But > having 50+ folders with zero files in them makes me very > worried. > > Is Digikam somehow involved? Digikam is the only application > I use to manage my collection since I stopped using Picasa a > year ago. I still use my commandline tools, in the script, > to move images from camera SD cards to my collection where > Digikam has, thus far, had no problem finding them. I have > over 22000 images. Is this a problem? > > Here is what I see: > 2012 has 1 empty folder > 2011 has 2 empby folders > 2010 had 4 empty folders > 2009 has 17 empty folders! > 2008 has 5 emtpy folders > 2007 has 1 empty folder > 2006 has 7 empty folders > 2005 has 8 empty folders > 2004 has 3 of 4 total empty > 2003 has 5 empty folders > > So, that's the report. What can I do? Is there any record > kept by Digikam of its activities I can check? Has anyone > else experienced sudden unusual mysterious vanishments? I'm > worried. > > Thanks for any help anyone can give. > Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Puzzling, and troubling, issue with empty folders
|
|
On 17/08/12 19:11, Peter Albrecht wrote:
> Hi Guy, > > I've been using DigiKam for 3 years now and never > experienced any unintentional disappearing fotos. > > For backup, I use "Unison File Synchronizer" > (http://www.cis.upenn.edu/~bcpierce/unison/), which lists > every changed file, before copiing it to the backup storage. > > Unfortunately it does not tell, what exactly changed. Great > would be something like: > Change: myfile.jpg (added Tag: "Family") > > BTW: Does somebody else know a free tool, which could do this? > > Maybe using unison (or a similar backup tool), you could > detect disappearing fotos in the future. > > Regards, > Peter Albrecht > > On 17.08.2012 07:04, Guy Stalnaker wrote: >> All, >> >> About a year ago I suffered a catastrophic drive issue. I >> was able to recover images from the drive with appropriate >> tools. Glad to have images recovered, yes, but the recovery >> application named the recovered imaged with a multi-digit >> name. As such, they were relatively useless. Had no idea >> what the images were, when they were from, etc. >> >> Using exiftool I was able to rename the files and at the >> same time organize them using the exif data they contain. >> Once I was done with the renaming, I had multiple folders >> organized by year/month/day, with images named using this >> format: DSCN_YYYYMMDDTHHMMSS.ext. >> >> I was able to use Digikam to find and eliminate duplicates, >> of which there were hundreds, as well as thumbnails. >> >> I've been very happy with Digikam, but recently I've noticed >> something very puzzling. Given the way the renaming process >> works (I use Linux and I have a shell script that uses the >> commandline applications, exiftool and install, to do the >> renaming) I know, without doubt, that if there is a folder >> in my collection in the year/month hierarchy for any day in >> any month in any year, that the folder can only exist >> because the script, well exiftool in the script, **read data >> from an existing image** and used that data to create, with >> the install program, the folder the image was then put into >> by the install application. >> >> But now, I have discovered over the past several days while >> reviewing images for a contest submission that I have over >> 50 zero-file folders in my collection. I am very troubled by >> this. I have deleted practically no image unless I knew they >> were duplicate images (in fact, I used Digikam itself to >> identify the duplicates and I reviewed them visually and >> deleted duplicates only when I could see in Digikam the two >> images side-by-side). I have nearly seven good years worth >> of images. And suddenly I see holes in my collection and I >> have no way of knowing just how significant the holes may >> be. The year 2008 does not count in the matter as I know I >> lost many of them several years ago (failed CD backup). But >> having 50+ folders with zero files in them makes me very >> worried. >> >> Is Digikam somehow involved? Digikam is the only application >> I use to manage my collection since I stopped using Picasa a >> year ago. I still use my commandline tools, in the script, >> to move images from camera SD cards to my collection where >> Digikam has, thus far, had no problem finding them. I have >> over 22000 images. Is this a problem? >> >> Here is what I see: >> 2012 has 1 empty folder >> 2011 has 2 empby folders >> 2010 had 4 empty folders >> 2009 has 17 empty folders! >> 2008 has 5 emtpy folders >> 2007 has 1 empty folder >> 2006 has 7 empty folders >> 2005 has 8 empty folders >> 2004 has 3 of 4 total empty >> 2003 has 5 empty folders >> >> So, that's the report. What can I do? Is there any record >> kept by Digikam of its activities I can check? Has anyone >> else experienced sudden unusual mysterious vanishments? I'm >> worried. >> >> Thanks for any help anyone can give. >> > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users > Peter, Metadata can be extracted using exiftools, so either with python or bash you should be able to filter out changes, as long as you kept a version of the extracted metadata at the last backup. -- Cheers Simon Simon Cropper - Open Content Creator Free and Open Source Software Workflow Guides ------------------------------------------------------------ Introduction http://www.fossworkflowguides.com GIS Packages http://www.fossworkflowguides.com/gis bash / Python http://www.fossworkflowguides.com/scripting _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Puzzling, and troubling, issue with empty folders
|
|
In reply to this post by Guy Stalnaker
On 17/08/12 06:04, Guy Stalnaker wrote:
> So, that's the report. What can I do? Is there any record kept by > Digikam of its activities I can check? Has anyone else experienced > sudden unusual mysterious vanishments? I'm worried. > > Thanks for any help anyone can give. > Just a few observations. You suffered a catastrophic drive failure yet it sounds like you are not keeping backups of your data. The next time you have a drive failure, and it will happen, you may not be able to recover anything. You need to start backing up your data. You should have one copy off line in a separate location. The maxim is that if you don't have your data backed up in two different ways then you don't have your data. If you had a backup, then the simple thing to do is to compare the files you have live on line with the backup. There are too many unknowns to be able to say why those directories are empty. My guess would be as a result of the de-duplication you did. No, digikam does not randomly delete files. Other people would have noticed, especially those who keep backups. Andrew _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Puzzling, and troubling, issue with empty folders
|
|
In reply to this post by Simon Cropper-3
On 17.08.2012 17:22, Simon Cropper wrote:
> On 17/08/12 19:11, Peter Albrecht wrote: >> For backup, I use "Unison File Synchronizer" >> (http://www.cis.upenn.edu/~bcpierce/unison/), which lists >> every changed file, before copiing it to the backup storage. >> >> Unfortunately it does not tell, what exactly changed. Great >> would be something like: >> Change: myfile.jpg (added Tag: "Family") >> >> BTW: Does somebody else know a free tool, which could do >> this? > Metadata can be extracted using exiftools, so either with > python or bash you should be able to filter out changes, as > long as you kept a version of the extracted metadata at the > last backup. Thanks for the answer, Simon. But I was looking for a "ready-to-use" programm (integrated in the backup tool). ;) Regards, Peter _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: DK 2.8.0 crashes during eport or copy
|
|
In reply to this post by cool.chris65
Hey,
yesterday I just wanted to reorganise some folders and pics, and DK freezes alltime when the destination folder was not empty and there was a file-nameconflict. Normaly (DK 2.7.0) there should appear the overwrite/renaming-dialog, but in this case (DK 2.8.0) just DK freeze and I have to kill it ... A filecopy of the same foldes and files in krusader or filemanager works as expected So at least it seems to be a similar error like the picasa-export-error desciped before? Greets, Christoph Am 14.08.2012 14:44, schrieb cool.chris65: > Hello, > > I think I found a litle Problem: > > I tried to export some Pics from DK to Picasa into an existing album. When I > mark a picture, which is already existing in the targetalbum, DK will crash, > but if I mark only new pics, it works as expected. > > In DK 2.7.0 there was no problem with picasa-export and dublettes. > > My System: (K)Ubuntu 12.04 LTS with actual patches and fixes > > Greets, Christoph > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users > Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
«
Return to digikam-users
|
1 view|%1 views
| Free forum by Nabble | Edit this page |