Welcome to the communityĭo you feel like you're drowning in digital photos? Sometimes it seems your phone gets filled up with selfies and snapshots all on its own, and yet picking the best shot and keeping your photos organized is never quite as automatic.debian/mysql-server-5.0.mysql.init: supply 'reset-password' and Sql/sql_ to properly verify access privileges to external tables * debian/patches/91_CVE-2007-2691.dpatch: fix sql/sql_ to make sure * debian/patches/91_CVE-2007-2583.dpatch: fix sql/item_ to verify init: supply 'reset-password' andĬheck for blank password. * SECURITY UPDATE: warn on startup if root mysql account has a blank cc to properly verify access privileges to external tables * SECURITY UPDATE: privilege escalation via views * SECURITY UPDATE: denial of service via crafted authentication request dpatch: fix sql/sql_ to make sureĭROP privileges are required when using RENAME TABLE statements * SECURITY UPDATE: denial of service via crafted IF clause On kubuntu/edgy, digikam 0.9.1 I had this bug introduced by the following mysql patch, but the workaround as described in #12 ( give write perms to all ) solved it for me. Go to the folder you specified as the "Albums Library Folder" and delete the two files that digiKam created: "digikam3.db" and "digikam3.db-journal". Delete your digiKam config file, located at: ~/.kde/share/config/digikamrcģ. Now digiKam should save pictures to your network pictures folder and it should save to the database on your local drive.Ģ. In the "Configure - digiKam" dialog, select "Albums" and then change the "Album Library Path" to your network pictures folder. In digiKam, go to the "Settings" menu and select "Configure digiKam. Create a symlink from the digikam3.db file, which digiKam created in your local "Albums Library Folder", to your network pictures folder.ĥ. (I'll refer to this as your "network pictures folder".)Ĥ. Through Konqueror, navigate to a network folder where you want to store pictures. When prompted for the "Albums Library Folder", specify a local folder (eg ~/.digiKam).ģ. ![]() Now you can re-configure digiKam from a fresh start as follows:Ģ. Go to the folder you specified as the "Albums Library Folder" and delete the two files that digiKam created: "digikam3.db" and "digikam3. Delete your digiKam config file, located at: ~/.kde/ share/config/ digikamrcģ. Use the "ps" and "kill" commands to verify and kill off the process, or, simply bring up KDE System Guard, find the digiKam process, and, kill it.)Ģ. (The digiKam process may be running even if you don't see digiKam on your desktop. Verify that digiKam is not still running. This is a workaround that will allow you to have digiKam store pictures on a network folder.įirst, if you've already run digiKam and it has hung (or done nothing) you must do the following to clean up the corrupt digiKam configuration:ġ. If you try restarting digiKam, there will be no visual feedback. When you specify that digiKam should store pictures on a network folder (CIFS/SAMBA or NFS), digiKam will hang. ![]() Here's a workaround that makes digiKam store pictures on a network folder and it's database on a local drive. It would be nice if that get fixed in 0.9 In my opinion, sqlite on an nfs share shouldn't make any difference when only one user access the db - it's just slower. This might be related to sqlite, I don't know. What's not working are the import function of digikam. It's said that nfs and sqlite doesn't work, but that's not true. Surprisingly the files are copied into the right place. The box does not change and stays at 0% forever. This start a copy process with a normal kde copy box. importing files or folder into the album. (By the way, would be nice to have an "update album" function to search for new photos.)ĭisabling the option makes digikam work again.Ģ. Interestingly this worked once with V.0.8.?. Starting digikiam in the shell gives no output. This will bring up a box on startup with a progress bar which goes to 99% and that's it. to enable the option "Search for new photos on startup" (don't know the exact wording) Importing images from the camera works, creating album folder and adding comments or tags - no problem.ġ. 0.8.x and 0.9b1 having the album on the network mount. I can't say if file locking (and that seems to be the problem with sqlite) is working with samba or not. ![]() I tested with an nfs mount and also (the same album folder) with a samba share mounted with cifs. But also when it is so I agree a message for the user is better than quietly do nothing or just crash.Īnyway, maybe I have a little more information which might help. I'm not shure if it's only a sqlite problem.
0 Comments
Leave a Reply. |