[digikam] [Bug 403073] Can't remove a removable media when digikam run

2020-07-30 Thread Loukournan29
https://bugs.kde.org/show_bug.cgi?id=403073

--- Comment #8 from Loukournan29  ---
(In reply to caulier.gilles from comment #7)
> digiKam 7.0.0 stable release is now published:
> 
> https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/
> 
> We need a fresh feedback on this file using this version.
> 
> Thanks in advance
> 
> Gilles Caulier

Hi,

According to my test, the 7.0.0 release fix the issue.

Paul-Antoine Hervin

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 402346] The digikamrc file is not recorded into the digikam directory

2020-01-15 Thread Loukournan29
https://bugs.kde.org/show_bug.cgi?id=402346

--- Comment #8 from Loukournan29  ---
(In reply to Loukournan29 from comment #7)

I want to precise that the %APPLOCALDATA%/digikam directory is created by the
installation, but the digikamrc file is not stored in.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 402346] The digikamrc file is not recorded into the digikam directory

2020-01-14 Thread Loukournan29
https://bugs.kde.org/show_bug.cgi?id=402346

--- Comment #7 from Loukournan29  ---
(In reply to caulier.gilles from comment #6)
> We have updated whole Qt to last 5.14 and KF5 to 5.65. Both are responsible
> of
> application settings management.
> 
> Can you reproduce the problem with digiKam 7.0.0-beta2 pre release ?
> 
> https://files.kde.org/digikam/
> 
> Thanks in advance
> 
> Gilles Caulier

With the 7.0.0-beta2 pre release the digikamrc file is still stored in the
%APPLOCALDATA% directory.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 402938] Rename album an within album property fails when a subalbum exists

2019-01-11 Thread Loukournan29
https://bugs.kde.org/show_bug.cgi?id=402938

--- Comment #8 from Loukournan29  ---
(In reply to Maik Qualmann from comment #7)
> I can reproduce that if the folder to be renamed has an extended network
> share on Windows, then it can not be renamed. We will not be able to detect
> or prevent this with the resources available with the Qt-API. Remove the
> network share or add it to a folder higher.
> 
> Maik

Would I use a network collection for this kind of folder ? Network folder
renaming is an avaible feature within the file manager. It is surprising that
Qt-API can't manage it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 403073] Can't remove a removable media when digikam run

2019-01-10 Thread Loukournan29
https://bugs.kde.org/show_bug.cgi?id=403073

--- Comment #2 from Loukournan29  ---
(In reply to caulier.gilles from comment #1)
> What did you expect ? To remove the media while in use and lost data ?
> 
> Seriously. This is a normal behavior...
> 
> Gilles Caulier

Seriously, why have a specific removable media collection, without specific
behaviours ?

I am a software engineer, and I would pleased to join the developpment team to
fixed some issues. 
I think that Digikam can reference photographs about a connected removable
media (thumbnails, metadata, ...), and then release every ressources to it. The
only needs to access then to the media is to display fullscreen the photographs
or when editing.

For example, I prefer to preview my shoots before importation. I would like to
browse my SD card without the limitations of the importation view. I am used to
quick edit (and cancel) some of my photographs to check their values.
Another example, I would like to browse different referenced removable media
while Digikam is running.

I noticed your are a main contributor to Digikam. I am interested in
documentation translation into french. I contacted the team, but without
response up to now.

Paul

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 403073] New: Can't remove a removable media when digikam run

2019-01-10 Thread Loukournan29
https://bugs.kde.org/show_bug.cgi?id=403073

Bug ID: 403073
   Summary: Can't remove a removable media when digikam run
   Product: digikam
   Version: 5.9.0
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: Albums-Engine
  Assignee: digikam-bugs-n...@kde.org
  Reporter: paul.her...@laposte.net
  Target Milestone: ---

SUMMARY
Can't remove a removable media when digikam run

STEPS TO REPRODUCE
1. Plug an USB media
2. Add a folder of this media to the Digikal collection of removable media
3. Browse the photographs from this USB media
4. Request the media unmount at Windows taskbar

OBSERVED RESULT
1. Windows indicate the media is in use.
2. Stop Digikam
3. The media can be unmounted


EXPECTED RESULT
The media must be removed while Digikam is running.


SOFTWARE/OS VERSIONS
Windows: Win7 home/pro french version and up to date
MacOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 402938] Rename album an within album property fails when a subalbum exists

2019-01-10 Thread Loukournan29
https://bugs.kde.org/show_bug.cgi?id=402938

--- Comment #6 from Loukournan29  ---
Created attachment 117380
  --> https://bugs.kde.org/attachment.cgi?id=117380=edit
Video showing the issue

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 402938] Rename album an within album property fails when a subalbum exists

2019-01-10 Thread Loukournan29
https://bugs.kde.org/show_bug.cgi?id=402938

--- Comment #5 from Loukournan29  ---
(In reply to Maik Qualmann from comment #4)
> I can not reproduce the problem on a real Win7 machine and also not on 2
> virtual Win7 / Win10 machines. Do they run a specific anti-virus software?
> 
> Maik

I reproduce the issue with my 2 win7 machine. I tried with album associated
with a local homegroup folder (my first try) and with a ordinary harddrive
folder.
The home group folder is set but not used over the network for the try (the
clients was off). The anti-virus is Avira (freeware version).

I reproduce the issue with another win7-pro machine and recorded the display
(attached). The anti-virus is Kaspersky.

Paul

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 402938] Rename album an within album property fails when a subalbum exists

2019-01-07 Thread Loukournan29
https://bugs.kde.org/show_bug.cgi?id=402938

--- Comment #3 from Loukournan29  ---
I reproduce this issue every try on Windows. There is no other application
using the folder or the subfolder.

I will play this test on Linux soon.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 402938] New: Rename album an within album property fails when a subalbum exists

2019-01-06 Thread Loukournan29
https://bugs.kde.org/show_bug.cgi?id=402938

Bug ID: 402938
   Summary: Rename album an within album property fails when a
subalbum exists
   Product: digikam
   Version: 5.9.0
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: Albums-TreeView
  Assignee: digikam-bugs-n...@kde.org
  Reporter: paul.her...@laposte.net
  Target Milestone: ---

SUMMARY
Rename album an within album property fails when a subalbum exists

STEPS TO REPRODUCE
1. Edit the properties of an album containing a subalbum
2. Modify the album name, then click on Ok

OBSERVED RESULT
1. A warn dialog indicates that the renaming as failed, and close the dialog
box
2. The photographs are not available any more within Digikam (switch albums to
check), and the album is not renamed.
3. The photographs files are still available in the file manager, and the
directory is not renamed
4. Rename again the album, but with the rename option. The warning is displayed
again. The album is renamed, but the corresponding directory. The photograph
are not available.
5. Rename again the album to the initial name. The renaming succeed, and the
photographs are available again.

Note : The album renaming with rename option has quite the same issue.



EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: Windows 7
MacOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 402346] The digikamrc file is not recorded into the digikam directory

2018-12-19 Thread Loukournan29
https://bugs.kde.org/show_bug.cgi?id=402346

--- Comment #1 from Loukournan29  ---
Please provide the resource moving at the upgrade to fixed version.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 402346] New: The digikamrc file is not recorded into the digikam directory

2018-12-19 Thread Loukournan29
https://bugs.kde.org/show_bug.cgi?id=402346

Bug ID: 402346
   Summary: The digikamrc file is not recorded into the digikam
directory
   Product: digikam
   Version: 5.9.0
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Setup-Misc
  Assignee: digikam-bugs-n...@kde.org
  Reporter: paul.her...@laposte.net
  Target Milestone: ---

SUMMARY
The digikamrc file is not recorded into the digikam directory

STEPS TO REPRODUCE
1. Install fresh digikam
2. Launch digikam, then quit.
3. 

OBSERVED RESULT
The digikamrc file is recorded into the %localappdata% directory.

EXPECTED RESULT
The digikamrc file should be recorded into the %localappdata%/digikam
directory.

SOFTWARE/OS VERSIONS
Windows: 7
MacOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 402288] The default Xmp.lr.hierarchicalSubject setting does not read darktable tags

2018-12-19 Thread Loukournan29
https://bugs.kde.org/show_bug.cgi?id=402288

--- Comment #2 from Loukournan29  ---
(In reply to Maik Qualmann from comment #1)
> Darktable stores Xmp.lr.hierarchicalSubject as Seq. This does not conform to
> the Adobe standard that provides a Bag. We use the capitalized alternative
> Xmp.lr.HierarchicalSubject as Seq. Since I can not determine at the moment
> which program it will use thius variant, I will not change it. Create a new
> entry that corresponds to the Darktable format and deactivate the default
> entry.
> 
> Maik

Thanks Maik for your comment,
I intend to create a new entry, but I lack precise documentation about each
field of an entry. I already try to create a second entry with the same Name,
but digikal cant manage them properly (see bug 402283). Which field DO match
with the corresponding XMP metadata ? Are they casesensitive ?

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 402288] New: The default Xmp.lr.hierarchicalSubject setting does not read darktable tags

2018-12-18 Thread Loukournan29
https://bugs.kde.org/show_bug.cgi?id=402288

Bug ID: 402288
   Summary: The default Xmp.lr.hierarchicalSubject setting does
not read darktable tags
   Product: digikam
   Version: 5.9.0
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: Setup-Metadata
  Assignee: digikam-bugs-n...@kde.org
  Reporter: paul.her...@laposte.net
  Target Milestone: ---

SUMMARY
The default Xmp.lr.hierarchicalSubject setting does not read darktable tags

STEPS TO REPRODUCE
1. Using the french version of DigiKam
2. Add a collection of photographs with sidecar xmp file, and hierarchical tag
set by darktable
3. Go to the tag view

OBSERVED RESULT
The tags are all read, but without the tags hierarchy

EXPECTED RESULT
The tags are read with the tag hierarchy

WORK AROUND
1. Edit the digikamrc file (digikam is off)
2. Go the entry Metadata/readingTags/Xmp.lr.hierarchicalSubject
3. Set the entry editable
4. Set the '*option' properties value to 6
5. Save the changes, then start digikam
6. Reread the tags -> the tag hierarchy is read.


SOFTWARE/OS VERSIONS
Windows: 7
MacOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 402286] New: Metadata settings don't display the combo value options

2018-12-18 Thread Loukournan29
https://bugs.kde.org/show_bug.cgi?id=402286

Bug ID: 402286
   Summary: Metadata settings don't display the combo value
options
   Product: digikam
   Version: 5.9.0
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: Setup-Metadata
  Assignee: digikam-bugs-n...@kde.org
  Reporter: paul.her...@laposte.net
  Target Milestone: ---

SUMMARY
Metadata settings don't show the combo value options

STEPS TO REPRODUCE
1. Using the french version of DigiKam
2. Enter into the Setup/Metadata/Advanced menu
3. Select 'Tag' ('Etiquette') in the left combo
4. Select 'Read options ('Options de lecture') in the right combo
5. Edit the default 'Xmp.lr.hierarchicalSubject' setting entry is available
(not editable)

OBSERVED RESULT
The setup options values are not displayed within the editor.
An editable setting does not display the combos value too.

EXPECTED RESULT
The combos display the setup value

SOFTWARE/OS VERSIONS
Windows: 
MacOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 402283] New: Duplicate entries drive to unpredictable performance

2018-12-18 Thread Loukournan29
https://bugs.kde.org/show_bug.cgi?id=402283

Bug ID: 402283
   Summary: Duplicate entries drive to unpredictable performance
   Product: digikam
   Version: 5.9.0
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: Setup-Metadata
  Assignee: digikam-bugs-n...@kde.org
  Reporter: paul.her...@laposte.net
  Target Milestone: ---

SUMMARY
Duplicate entries drive to unpredictable performance

STEPS TO REPRODUCE
1. Using the french version of DigiKam
2. Enter into the Setup/Metadata/Advanced menu
3. Select 'Tag' ('Etiquette') in the left combo
4. Select 'Read options ('Options de lecture') in the right combo
5. Check the default 'Xmp.lr.hierarchicalSubject' setting entry is available
(not editable)
6. Click on the 'Add' ('Ajouter') button
7. Fill a new setting entry named 'Xmp.lr.hierarchicalSubject' and save it

OBSERVED RESULT
1. The entry is recorded without any warning about the duplicate name
2. The entry is recorded with a duplicate key into the digikamrc file
3. Digikam read the duplicate entry without warning
4. Digikam have an unpredictable performance about the duplicated setting entry

EXPECTED RESULT
An duplicated entry cant be recorded with the same key into the digikamrc file.
Only one of the duplicated entries can be activated.

Note : I duplicated an entry because the default one doesn't work and I cant
edit it.


SOFTWARE/OS VERSIONS
Windows: 7
MacOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.