Bug 112426 - Problems moving photos to album with whitespace in its name
Summary: Problems moving photos to album with whitespace in its name
Status: RESOLVED NOT A BUG
Alias: None
Product: digikam
Classification: Applications
Component: Database-Albums (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-11 15:41 UTC by krienke
Modified: 2023-04-08 20:55 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 8.0.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description krienke 2005-09-11 15:41:19 UTC
Version:           0.8.0beta1 (using KDE KDE 3.4.2)
Installed from:    SuSE RPMs
Compiler:          gcc 3.3.5 
OS:                Linux

When I try to move jpgs from a konqueror filemanager window to a digikam folder by simply dragging the photos and the digikam folder name has e.g. a blank in its name this will result in an error and data loss! If eg the source is media:/sda1/photos (CF-Card) and the target foldername ist "target name" then this error messages shows up right after starting to move myphoto01.jpg ist the first photo in source: 

The file or folder /media/sda1/myphoto01.jpg does not exist.

Actualy the error messages says that the source does not exist which was not true before the move. The real trouble is, that afterwards several images are simply lost, they have been deleted from the source but not copied to the destination!!!

If try to move to a target without blanks in its name it works. If I copy the files instead of moving it works also.
Comment 1 Joern Ahrens 2005-09-11 17:09:21 UTC
I cannot reproduce it here.
Can you start digikam from konsole and post the output here, if there is any when the error occurs.
Comment 2 krienke 2005-09-11 18:29:13 UTC
Am Sonntag, 11. September 2005 17:09 schrieb Joern Ahrens:
[bugs.kde.org quoted mail]

Just tried to reproduce this bug myself one more time to get the commandline 
output of digikam. Well strange enough I cannot, but I know for sure I did 
some hours ago when I wrote the bug report. So the bug  seems to depend on 
something I don't see at the moment. I'll keep on watching this.

Thanks
Rainer
Comment 3 Tom Albers 2005-09-12 16:54:11 UTC
non-reproducable by reporter