<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body><div>I would make sure you have write access to the NAS. On some systems, e.g. Fedora it is a bit complicated to mount an NTFS drive with full access (read and write).</div><div>You can try:</div><div>"nano /path/to/nas/temp.txt"</div><div>then add some text in temp.txt and save it.</div><div>Instead of "nano" you can use "gedit" if you are on gnome or "kate" if you are on KDE.</div><div>Please run it from your user account and do not use "sudo".</div><div>Just an idea.</div><div><br></div><div><br></div><div id="composer_signature"><div style="font-size:85%;color:#575757" dir="auto">Sent from my Samsung Galaxy smartphone.</div></div><div><br></div><div style="font-size:100%;color:#000000"><!-- originalMessage --><div>-------- Original message --------</div><div>From: Uwe Haider <uwe.haider@gmx.net> </div><div>Date: 2017-05-21 6:23 AM (GMT-07:00) </div><div>To: digikam-users@kde.org </div><div>Subject: file not found.... -> no start! </div><div><br></div></div>After moving to a new computer/NAS I have trouble to start digikam. I<br>try to fix it for several weeks now, but no success so far. This is the<br>output of digikam while starting:<br><br> [...]<br><br> 133 digikam.general: Using 8 CPU core to run threads<br> 134 digikam.general: new search text settings: "" : hasResult = <br>false , validRows = 0<br> 135 QFSFileEngine::open: No file name specified<br> 136 digikam.geoiface: ----<br> 137 digikam.general: Added root album called: "WD-USB"<br> 138 digikam.general: Added root album called: "Geschäftsbericht_2011"<br> 139 digikam.general: Added root album called: "Einweihung HHN"<br> 140 digikam.general: Added root album called: "Albas Bilder"<br> 141 digikam.general: Added root album called: "Carla 18"<br> 142 digikam.general: Added root album called: "Bilder_lokal"<br> 143 digikam.general: Added root album called: "Bilder"<br> 144 digikam.general: Added root album called: "Fotos"<br> 145 digikam.general: Added root album called: "NAS"<br> 146 digikam.general: Did not find album root album in hash<br> 147 QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch<br>failed: Datei oder Verzeichnis nicht gefunden<br> 148 QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch<br>failed: Datei oder Verzeichnis nicht gefunden<br><br>-> last line is repeated until here<br><br>3094 QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch<br>failed: Datei oder Verzeichnis nicht gefunden<br>3095 QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch<br>failed: Auf dem Gerät ist kein Speicherplatz mehr verfügbar<br><br>"Datei oder Verzeichnis nicht gefunden" means "file not found"<br><br>"Auf dem Gerät ist kein Speicherplatz mehr verfügbar" means "no space<br>left on device".<br><br>This is, what I have done while moving to the new machine:<br><br>- moved the mariadb-server to my NAS<br><br>- moved all files in the NAS-mariadb as separate dumps<br><br>- changed the album paths in the albumroot-table to the new mount points<br><br>- I have lost an harddisk (broken, unreadable) and tried to mount the<br>backup instead ( I don't need this files absolut)<br><br>- changed the configuration in digikam to the NAS-mariadb<br><br>The main problem seems to be the QInotifyFileSystemWatcherEngine writing<br>a disk full - how can I stop this? I think digikam will be able to check<br>and repare the mariadb if it gets started.<br><br>Or should I remove the Albumrootpath of the crashed hard disk manually?<br><br><br>Any advice is welcome...<br><br><br>uhai<br><br><br><br>-- <br>Uwe Haider<br>uwe.haider@gmx.net<br>http://www.familie-haider.de<br><br><br></body></html>