file not found.... -> no start!

/exact/

Send Digikam-users mailing list submissions to
 [hidden email]

To subscribe or unsubscribe via the World Wide Web, visit
 https://mail.kde.org/mailman/listinfo/digikam-users
or, via email, send a message with subject or body 'help' to
 [hidden email]

You can reach the person managing the list at
 [hidden email]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Digikam-users digest..."

Today's Topics:

   1. Re: file not found.... -> no start! (Remco Viëtor)
   2. Re: Adjusting file last modified date (Andrey Goreev)
   3. Re: file not found.... -> no start! (Uwe Haider) (Uwe Haider)
   4. Re: file not found.... -> no start! (Gilles Caulier)
   5. Re: How do I save "DateTime imported" value in Digikam?
      (Jens Benecke)

Message: 1
Date: Sun, 21 May 2017 15:50:00 +0200
From: Remco Viëtor <[hidden email]>
To: digiKam - Home Manage your photographs as a professional with the
 power of open source <[hidden email]>
Subject: Re: file not found.... -> no start!
Message-ID: <5388231.gBvAhygMuy@manticore>
Content-Type: text/plain; charset="UTF-8"

On dimanche 21 mai 2017 14:23:29 CEST Uwe Haider wrote:
 After moving to a new computer/NAS I have trouble to start digikam. I
 try to fix it for several weeks now, but no success so far. This is the
 output of digikam while starting:

   [...]

   133  digikam.general: Using  8  CPU core to run threads
   134 digikam.general: new search text settings:  "" : hasResult =
 false , validRows =  0
   135 QFSFileEngine::open: No file name specified
   136 digikam.geoiface: ----
   137 digikam.general: Added root album called:  "WD-USB"
   138 digikam.general: Added root album called:  "Geschäftsbericht_2011"
   139 digikam.general: Added root album called:  "Einweihung HHN"
   140 digikam.general: Added root album called:  "Albas Bilder"
   141 digikam.general: Added root album called:  "Carla 18"
   142 digikam.general: Added root album called:  "Bilder_lokal"
   143 digikam.general: Added root album called:  "Bilder"
   144 digikam.general: Added root album called:  "Fotos"
   145 digikam.general: Added root album called:  "NAS"
   146 digikam.general: Did not find album root album in hash
   147 QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch
 failed: Datei oder Verzeichnis nicht gefunden
   148 QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch
 failed: Datei oder Verzeichnis nicht gefunden

 -> last line is repeated until here

 3094 QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch
 failed: Datei oder Verzeichnis nicht gefunden
 3095 QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch
 failed: Auf dem Gerät ist kein Speicherplatz mehr verfügbar

 "Datei oder Verzeichnis nicht gefunden" means "file not found"

 "Auf dem Gerät ist kein Speicherplatz mehr verfügbar" means "no space
 left on device".

 This is, what I have done while moving to the new machine:

 - moved the mariadb-server to my NAS

 - moved all files in the NAS-mariadb as separate dumps

 - changed the album paths in the albumroot-table to the new mount points

 - I have lost an harddisk (broken, unreadable) and tried to mount the
 backup instead ( I don't need this files absolut)

 - changed the configuration in digikam to the NAS-mariadb

 The main problem seems to be the QInotifyFileSystemWatcherEngine writing
 a disk full - how can I stop this? I think digikam will be able to check
 and repare the mariadb if it gets started.

 Or should I remove the Albumrootpath of the crashed hard disk manually?

 Any advice is welcome...

 uhai
If I understand correctly, you are trying to put the digikam database on a 
network drive. Looking at the Digikam settings dialog, it says explicitly:
"Note: a remote file system such as NFS, cannot be used here"...
In addition, MySQL is still marked as experimental, mariadb is a fork of 
MySQL. That's for Digikam version 5.5.0 (as appimage under OpenSuSE 42.2)

Might that be the cause of the problems?

Remco

Message: 2
Date: Sun, 21 May 2017 08:18:20 -0600
From: Andrey Goreev <[hidden email]>
To: digiKam - Home Manage your photographs as a professional with the
 power of open source <[hidden email]>
Subject: Re: Adjusting file last modified date
Message-ID: <[hidden email]>
Content-Type: text/plain; charset="utf-8"

I am pretty sure that FileModifyDate is the system's "date modified". Windows would have "date created" in addition to it but linux does not store "date created". In the example I sent I copy values from QuickTime Date Created of mp4 file to system's file date modified (I do that because digikam uses date modified (file system) as date created (content) for video files. Works for me)

Sent from my Samsung Galaxy smartphone.
-------- Original message --------From: Remco Viëtor <[hidden email]> Date: 2017-05-21  7:43 AM  (GMT-07:00) To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]> Subject: Re: Adjusting file last modified date 
On dimanche 21 mai 2017 15:15:10 CEST Andrey Goreev wrote:
 In the meantime, exiftool can do that easily.
 exiftool -api quicktimeutc=1 "-FileModifyDate<QuickTime:CreateDate"
 -overwrite_original FILE  Change QuickTime:CreateDate to whatever tag you
 want to copy the info from or to a certain value (date). 

But make sure you know which tag you need to overwrite...
In this case, the OP wanted to change the date the file was last /modified/.
Your exemple would change the date the file content was /created/, not the same 
thing. I'd even think you wouldn't want to touch that particular item at all, 
except when you know the date is wrong and you know the correct creation date.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20170521/83b60105/attachment-0001.html>

Message: 3
Date: Sun, 21 May 2017 16:50:41 +0200
From: Uwe Haider <[hidden email]>
To: [hidden email]
Subject: Re: file not found.... -> no start! (Uwe Haider)
Message-ID: <[hidden email]>
Content-Type: text/plain; charset=utf-8

Thanks Andrey,

I've tested it with vim and it works for my user. Writing is possible to
the NAS.

uhai

file not found.... -> no start!

file not found.... -> no start!

Re: file not found.... -> no start!

Re: file not found.... -> no start!

Re: file not found.... -> no start!

RE: Re: file not found.... -> no start!

Re: RE: Re: file not found.... -> no start!

Re: RE: Re: file not found.... -> no start!

Re: RE: Re: file not found.... -> no start!

Re: file not found.... -> no start!

Re: RE: Re: file not found.... -> no start!

Re: file not found.... -> no start!