Bug 317669

Summary: Two dialogs when overwrite alert.
Product: [Applications] digikam Reporter: Marek Potocki <qrczakoff>
Component: AdvancedRename-dialogAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: caulier.gilles
Priority: NOR    
Version: 3.1.0   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In: 4.0.0
Attachments: Twice displayed digikam overwrite alert

Description Marek Potocki 2013-04-01 07:08:49 UTC 
On change file name to existing, window with alert opening twice.
Bug happens always in my file naming system, but when I test another configurations, it's not happens always.
My file naming system: 
1. RAW file (.CR2 or .ARW)   
2. JPEG file (.JPG)
1+2 with xmp metadata files and groupped

Reproducible: Sometimes

Steps to Reproduce:
1. Create files with my schema ex. FOO.CR2 and FOO.JPG (I thing group is not obligatory).
2. Generate with external program file with same base name, but with lowercase extension (FOO.jpg).
3. Rename FOO.jpg to FOO.JPG
Comment 1 Marek Potocki 2013-04-01 07:09:45 UTC 
Created attachment 78533 [details]
Twice displayed digikam overwrite alert
Comment 2 caulier.gilles 2013-04-01 07:19:27 UTC 
Which digiKam version do you use ?

Gilles Caulier
Comment 3 Marek Potocki 2013-04-01 08:33:38 UTC 
3.1.0, but 3.0.x versions have same problem


2013/4/1 Gilles Caulier <caulier.gilles@gmail.com>

> https://bugs.kde.org/show_bug.cgi?id=317669
>
> Gilles Caulier <caulier.gilles@gmail.com> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                  CC|                            |caulier.gilles@gmail.com
>
> --- Comment #2 from Gilles Caulier <caulier.gilles@gmail.com> ---
> Which digiKam version do you use ?
>
> Gilles Caulier
>
> --
> You are receiving this mail because:
> You reported the bug.
>
Comment 4 caulier.gilles 2013-12-04 17:58:07 UTC 
MArek, 

This file still valid using digiKam 3.5.0 ?

Gilles Caulier
Comment 5 Marek Potocki 2013-12-04 18:12:30 UTC 
In 3.5.0 it's fixed. Thanks.