| Summary: | problems with albums who's name start as the album library path | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | George B <george> |
| Component: | Albums-MainView | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version: | 0.9.1 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 1.0.0 | |
| Sentry Crash Report: | |||
|
Description
George B
2007-07-22 14:58:34 UTC
George, Problem still exist with last digiKam 0.9.2 release ? Gilles Caulier Hi, from your description, I am not sure whether the problem is already caused from the process of copying. When using directories (or filenames) with spaces, it is very important to protect them from being split into parts. (Personally I would strongly recommend to use either underscores from the very beginning, or write "PozeNuntaErol" instead of "poze nunta Erol", but this is surely a matter of taste). Could you try the whole procedure in systematic way: a) copy the files from one computer to the other, under the directory name /poze (where all your images are, right). In this step digikam should not be running. Which command do you use for copying? b) Then check, whether the files ended up in the right plac and that no additional directories were created (e.g. due to spaces in the Directory names and insufficient quoting during the copying) c) Start digikam and see how the new folder is scanned. d) leave and enter digikam: no problems should arise. Also note that 0.9.2 packages are out for kubuntu, see http://www.digikam.org/?q=download/binary/ (However, I don't think that your problem is affected by upgrading. Still the feature improvements are worth an update ;-). Best, Arnd I tried with the version from repos (0.9.2-final) and it's the same; I tried compiling it from svn, but after two hours I gave up. Last name the folder had was "nunta_Erol"; after installing the new version I started digikam and everything was ok; I closed it, and "mv nunta_Erol/ poze_nunta_Erol"; when I started digikam it asked for confirmation to delete the album "nunta_Erol" because it was removed from the disk, then it scanned the library, and asked for confirmation to delete a big list of pics from the "_nunta_Erol" album because they are not on the disk; so at least at the startup scan, it can see the folder; but I think there's a problem with its database. The folder was copied using scp from the other maching and at file system level everything was ok (no multiple folders, etc). I did another test, I created a folder "/pics", change the library path to this folder, closed digikam, created a sub-folder "pics album" and copied a picture there, then opened digikam.. same problem; I attached two screenshots. root@mormy:/usr/lib# mkdir /pics root@mormy:/usr/lib# chown georgeav:georgeav /pics georgeav@mormy:/poze$ mkdir /pics/pics\ album georgeav@mormy:/poze$ cp ./poze_nunta_Erol/img_5609.jpg /pics/pics\ album/ screenshots: http://img231.imageshack.us/my.php?image=digikamxm0.png http://img119.imageshack.us/my.php?image=digikam2lg5.png Also, on another system I have the library path in /arhive/everyone/digikam ; I tried creatin an album "arhive everyone digikam new" and "arhive\everyone\digikam new" and it was ok, no problem (I couldn't create "arhive/everyone/digikam new" :-) ). So I think this problem is only if the library path is a folder in the root folder. Concerning the first problem: you should not move any folders around outside of digikam when they are below digikams image root. DigiKam does not know on restart where they were moved. I am not sure if I understand the rest ... This does not sound like "a space in filename issue", or? George, This file still valid using 0.9.4 (KDE3) or 0.10.0 release (KDE4) ? Gilles Caulier Is this report still valid? I tested now on digikam 2:1.0.0~beta5-1ubuntu1 (KDE 4.3.2) and the problem is fixed. |
