[digikam] [Bug 411946] Crash when saving captions to picture

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=411946

--- Comment #8 from IWBR  ---
Ok, understood, thanks.

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

[digikam] [Bug 411946] Crash when saving captions to picture

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=411946

--- Comment #5 from IWBR  ---
Sure, no problem. I was just reporting what I experienced.

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

[digikam] [Bug 411946] Crash when saving captions to picture

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=411946

--- Comment #2 from IWBR  ---
Created attachment 122674
  --> https://bugs.kde.org/attachment.cgi?id=122674=edit
Backtrace of the exact same problem (and same picture) in another digikam
session

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

[digikam] [Bug 411946] Crash when saving captions to picture

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=411946

IWBR  changed:

   What|Removed |Added

 CC||iwannaber...@gmail.com

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

[digikam] [Bug 411946] Crash when saving captions to picture

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=411946

--- Comment #1 from IWBR  ---
More info:

After restarting digikam, and checking on that file, I can see that the
captions I had written had been saved to digikam's database but not to the
image metadata. Editing any changes to that picture (e.g. the date, using the
metadata editor) made those changes go away from the database.

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

[digikam] [Bug 411946] New: Crash when saving captions to picture

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=411946

Bug ID: 411946
   Summary: Crash when saving captions to picture
   Product: digikam
   Version: 6.4.0
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: digikam-bugs-n...@kde.org
  Reporter: iwannaber...@gmail.com
  Target Milestone: ---

Created attachment 122673
  --> https://bugs.kde.org/attachment.cgi?id=122673=edit
Backtrace of the crash

SUMMARY

I had another crash today when saving the changes after editing the captions
(title, description and date) of a jpg picture. 

I have attached the console output to this bug report, including the backtrace.
The beginning of the output is missing due to its size (the terminal emulator
only saves the last 1 lines).

STEPS TO REPRODUCE
1. Start digikam and wait until the initial scan finishes.
2. Select one file, go to the Captions panel, and edit the title, description
and date.
3. Save the changes

OBSERVED RESULT
Digikam immediately crashed and closed.

EXPECTED RESULT
Changes should be saved and the user should continue to use the software.

SOFTWARE/OS VERSIONS

digikam-6.4.0-git-20190915T141349-x86-64.appimage in Ubuntu 18.04LTS.

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

[digikam] [Bug 411927] Crash during initial scan

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=411927

--- Comment #6 from IWBR  ---
Glad you could fix it.

Gilles, sadly, the following time I started digikam, it finished the initial
scan successfully (it continued where it left it), so I could not reproduce it
anymore. I would need to wait until another batch of new pictures are added to
the library and digikam scans them.

In any case, I'll keep an eye in case it happens again and report back if
necessary.

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

[digikam] [Bug 411927] Crash during initial scan

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=411927

IWBR  changed:

   What|Removed |Added

 CC||iwannaber...@gmail.com

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

[digikam] [Bug 411927] New: Crash during initial scan

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=411927

Bug ID: 411927
   Summary: Crash during initial scan
   Product: digikam
   Version: 6.3.0
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: digikam-bugs-n...@kde.org
  Reporter: iwannaber...@gmail.com
  Target Milestone: ---

Created attachment 122661
  --> https://bugs.kde.org/attachment.cgi?id=122661=edit
Backtrace of the crash

SUMMARY

Today digikam crashed twice while scanning for new pictures in the collection.
The second time I was able to run it in debug mode and capture the backtrace. I
have attached the console output to this bug report. I hope it is useful.

I am using digikam-6.4.0-git-20190911T052139-x86-64.appimage under Ubuntu
18.04.

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

[digikam] [Bug 411773] Crash when writing captions on picture

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=411773

--- Comment #2 from IWBR  ---
Created attachment 122571
  --> https://bugs.kde.org/attachment.cgi?id=122571=edit
Backtrace of the crash (second attempt)

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

[digikam] [Bug 411773] Crash when writing captions on picture

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=411773

--- Comment #1 from IWBR  ---
Ok, I tried to edit the metadata for the exact same file. The crash happened
exactly at the same point of the original post:

I selected the image. I went to the Captions panel, and wrote the title, author
and description of the picture. Then I clicked on the date (near the bottom) to
change it, and at that moment Digikam crashed. All that before actually saving
any metadata to the file.

I attached a new console output with the backtrace.

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

[digikam] [Bug 411773] New: Crash when writing captions on picture

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=411773

Bug ID: 411773
   Summary: Crash when writing captions on picture
   Product: digikam
   Version: 6.3.0
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: digikam-bugs-n...@kde.org
  Reporter: iwannaber...@gmail.com
  Target Milestone: ---

Created attachment 122570
  --> https://bugs.kde.org/attachment.cgi?id=122570=edit
Backtrace of the crash

SUMMARY

I had a couple of crashes today when trying to tag a few pictures, so I thought
of running digikam in debug mode and capture the error and the backtrace.

The first time, digikam just closed by itself during or immediately after
scanning for new pictures. The time I was able to record the log (attached in
this report), digikam crashed when the picture scan alreaady finished and I was
editing the caption and date of a picture in the Captions panel.

I hope this bug report is useful.

PS: Using digikam-6.3.0-git-20190825T034937-x86-64.appimage in Ubuntu 18.04LTS.

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

[digikam] [Bug 411773] Crash when writing captions on picture

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=411773

IWBR  changed:

   What|Removed |Added

 CC||iwannaber...@gmail.com

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

[digikam] [Bug 411619] Crash when tagging, switching to map view...

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=411619

IWBR  changed:

   What|Removed |Added

 CC||iwannaber...@gmail.com

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

[digikam] [Bug 411619] New: Crash when tagging, switching to map view...

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=411619

Bug ID: 411619
   Summary: Crash when tagging, switching to map view...
   Product: digikam
   Version: 6.3.0
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: digikam-bugs-n...@kde.org
  Reporter: iwannaber...@gmail.com
  Target Milestone: ---

Created attachment 122500
  --> https://bugs.kde.org/attachment.cgi?id=122500=edit
Backtrace of the crash

SUMMARY

Today I had to tag a bunch of new pictures (around 800). I experienced three
crashes during that process. I don't recall doing anything specific, just
selecting pictures in the miniture view, using the Captions panel to tag, and
switching to the map panel from time to time to check the location of a picture
with GPS coordinates.

The third time I started digikam in debug mode, so I could capture the error
and run the backtrace. I have attached the textfile with the output of the
console.

In short, this is the main error message:

Thread 1 "digikam" received signal SIGSEGV, Segmentation fault.
0x7fffe1ae5bf0 in ubrk_following ()
   from /tmp/.mount_digikabK4AdX/usr/lib/libicuuc.so.58


This may be related to Bug 407914 and Bug 392607, but that's for you to judge. 
I hope it helps. Thanks!

PS: I'm using digikam-6.3.0-git-20190825T034937-x86-64.appimage under Ubuntu
18.04 LTS

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

[digikam] [Bug 392010] Face recognition assigns faces to people without confirmation, leading to false positives

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=392010

--- Comment #2 from IWBR  ---
I believe this bug is no longer relevant (or won't be relevant soon). Faces are
never assigned to people, just suggested. Therefore, metadata is never written
for new faces without the intervention of the user. When I opened this bug, I
was still not sure of that.

However, for the sake of clarity, I would not close it until Bug 392016 is
solved (which will be, once the changes from gsoc2019 will be incorporated to
the main branch).

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

[digikam] [Bug 411289] Wishlist: Color schemes, Icon themes and Widget style together in the same menu

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=411289

--- Comment #2 from IWBR  ---
Ok, it's not a big deal in any case.

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

[digikam] [Bug 411289] New: Wishlist: Color schemes, Icon themes and Widget style together in the same menu

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=411289

Bug ID: 411289
   Summary: Wishlist: Color schemes, Icon themes and Widget style
together in the same menu
   Product: digikam
   Version: 6.3.0
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Usability-Themes
  Assignee: digikam-bugs-n...@kde.org
  Reporter: iwannaber...@gmail.com
  Target Milestone: ---

SUMMARY

I have noticed that Digikam has 3 possible customization options: color
schemes, icon themes and widget styles. The first one is located in the main
"Settings" menu, while the other two are located in Settings, Configure
Digikam, Miscellaneous, Appearance.

Wouldn't it be more intuitive towards the final user if the three customization
options were in the same menu? At least, adding the color scheme in
"Appearance" as well, with the other two. Although adding the three in the
Settings/Themes menu would be fine too (it could be categorized as Icons,
Colors and Widget style). 

Another thing, since changing the icon theme requires restarting Digikam, what
about prompting the user if he wishes to restart at that moment?

That's it. I have been playing with the themes these days and I thought it
would be convenient if the three were next to each other. Thanks for your time!

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

[digikam] [Bug 411289] Wishlist: Color schemes, Icon themes and Widget style together in the same menu

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=411289

IWBR  changed:

   What|Removed |Added

 CC||iwannaber...@gmail.com

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

[digikam] [Bug 410862] Crash when starting appimage build 6.3.0-git-20190812T053738-x86-64

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=410862

--- Comment #7 from IWBR  ---
Don't worry, whenever it's available again.

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

[digikam] [Bug 410862] Crash when starting appimage build 6.3.0-git-20190812T053738-x86-64

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=410862

--- Comment #5 from IWBR  ---
Oh, ok ok. I'll wait for next build in a few days then :)

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

[digikam] [Bug 410862] Crash when starting appimage build 6.3.0-git-20190812T053738-x86-64

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=410862

--- Comment #3 from IWBR  ---
That explains why the other day digikam had to rescan the whole library when
connectivity was lost.

Anyway, I deleted all the mounthpaths except the one I am actively using now,
and the problem persist with the same error message (if that's what you fixed
in this commit then it's fine):


Digikam::ActionThreadBase::setMaximumNumberOfThreads: Using  8  CPU core to run
threads
Digikam::AlbumFilterModel::setSearchTextSettings: new search text settings: ""
: hasResult = false , validRows = 0
unknown: QFSFileEngine::open: No file name specified
Digikam::ItemMarkerTiler::slotSourceModelReset: 
Digikam::ItemMarkerTiler::slotSourceModelReset: 
unknown: ASSERT: "!isEmpty()" in file ././/include/QtCore/qlist.h, line 345
/tmp/.mount_digikat5eTpJ/AppRun línia 151:  5336 Avortat (s'ha
bolcat la memòria) digikam $@

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

[digikam] [Bug 410862] Crash when starting appimage build 6.3.0-git-20190812T053738-x86-64

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=410862

IWBR  changed:

   What|Removed |Added

 CC||iwannaber...@gmail.com

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

[digikam] [Bug 410862] New: Crash when starting appimage build 6.3.0-git-20190812T053738-x86-64

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=410862

Bug ID: 410862
   Summary: Crash when starting appimage build
6.3.0-git-20190812T053738-x86-64
   Product: digikam
   Version: 6.3.0
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: digikam-bugs-n...@kde.org
  Reporter: iwannaber...@gmail.com
  Target Milestone: ---

SUMMARY

I downloaded and tried the most recent appimage build for x64
(6.3.0-git-20190812T053738-x86-64). It seems to crash at startup in my computer
(Ubuntu 18.04 LTS).

If I start it from command line in debug mode, this is the full output I get
(including backtrace). I hope it helps:





user@user-TM1703:~/Applications$
./digikam-6.3.0-git-20190812T053738-x86-64_4338a3f6f7f40768c9c5fc4baf344970.appimage
debug

(AppImageLauncher:21162): GLib-GIO-CRITICAL **: 01:39:30.114:
g_converter_convert: assertion 'outbuf_size > 0' failed

(AppImageLauncher:21162): Gtk-CRITICAL **: 01:39:30.114: Unable to load
resource for composite template for type 'GtkDialog': No s'ha pogut
descomprimir el recurs «/org/gtk/libgtk/ui/gtkdialog.ui»

(AppImageLauncher:21162): Gtk-CRITICAL **: 01:39:30.114:
gtk_widget_class_bind_template_child_full: assertion
'widget_class->priv->template != NULL' failed

(AppImageLauncher:21162): Gtk-CRITICAL **: 01:39:30.114:
gtk_widget_class_bind_template_child_full: assertion
'widget_class->priv->template != NULL' failed

(AppImageLauncher:21162): Gtk-CRITICAL **: 01:39:30.114:
gtk_widget_class_bind_template_child_full: assertion
'widget_class->priv->template != NULL' failed

(AppImageLauncher:21162): Gtk-CRITICAL **: 01:39:30.114:
gtk_widget_class_bind_template_child_full: assertion
'widget_class->priv->template != NULL' failed

(AppImageLauncher:21162): Gtk-CRITICAL **: 01:39:30.114:
gtk_widget_class_bind_template_callback_full: assertion
'widget_class->priv->template != NULL' failed
-- digiKam Linux AppImage Bundle
-- Use 'help' as CLI argument to know all available options for digiKam
application.
-- Note: to integrate this bundle to your desktop, use AppImageLauncher.
libudev.so.0 
-- Preloading shared libs: 
Starting digiKam into GDB...
Use 'bt' command on debugger prompt to get a crash backtrace.
Use 'q' command to quit debugger session.
GNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-git
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from digikam...done.
Starting program: /tmp/.mount_digikasuEFNg/usr/bin/digikam 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffd8f00700 (LWP 21734)]
[New Thread 0x7fffd3fff700 (LWP 21740)]
Digikam::DXmlGuiWindow::setupIconTheme: Breeze icons resource file found
Digikam::DXmlGuiWindow::setupIconTheme: Breeze-dark icons resource file found
Digikam::ApplicationSettings::setApplicationFont: Switch to application font: 
QFont( "Ubuntu,12,-1,5,50,0,0,0,0,0,Regular" )
Digikam::AlbumWatch::AlbumWatch: AlbumWatch is disabled
[New Thread 0x7fffd2700700 (LWP 21751)]
Digikam::AlbumManager::setDatabase: Database Parameters:
   Type: "QSQLITE"
   DB Core Name: "/home/user/Imatges/digikam4.db"
   DB Thumbs Name:   "/home/user/Imatges/thumbnails-digikam.db"
   DB Face Name: "/home/user/Imatges/recognition.db"
   DB Similarity Name:   "/home/user/Imatges/similarity.db"
   Connect Options:  ""
   Host Name:""
   Host port:-1
   Internal Server:  false
   Internal Server Path: ""
   Internal Server Serv Cmd: ""
   Internal Server Init Cmd: ""
   Username: ""
   Password: ""

[New Thread 0x7fffd1eff700 (LWP 21752)]
[Thread 0x7fffd1eff700 (LWP 21752) exited]
Digikam::DbEngineConfigSettingsLoader::readConfig: Loading SQL code from config
file "/tmp/.mount_digikasuEFNg/usr/share/digikam/database/dbconfig.xml"
Digikam::DbEngineConfigSettingsLoader::readConfig: Checking XML version ID =>
expected:  3  found:  3
Digikam::CoreDbSchemaUpdater::update: Core database: running schema update
Digikam::CoreDbSchemaUpdater::startUpdates: Core database: have a structure
version  10

[digikam] [Bug 393408] Support for extra image formats as HEIC, FITS, JPEG-XR [patch]

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=393408

IWBR  changed:

   What|Removed |Added

 CC||iwannaber...@gmail.com

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

[digikam] [Bug 410425] Wishlist: Reverse geocoding to IPTC/XMP location fields.

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=410425

IWBR  changed:

   What|Removed |Added

 CC||iwannaber...@gmail.com

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

[digikam] [Bug 310812] Geocoding photos by using place names information from metadata (IPTC, XMP)

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=310812

IWBR  changed:

   What|Removed |Added

 CC||iwannaber...@gmail.com

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

[digikam] [Bug 410425] New: Wishlist: Reverse geocoding to IPTC/XMP location fields.

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=410425

Bug ID: 410425
   Summary: Wishlist: Reverse geocoding to IPTC/XMP location
fields.
   Product: digikam
   Version: 6.2.0
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Geolocation-ReverseGeoCoding
  Assignee: digikam-bugs-n...@kde.org
  Reporter: iwannaber...@gmail.com
  Target Milestone: ---

SUMMARY

The Edit Geolocation tool has a function to perform reverse geocoding and works
quite well. It saves the location of the picture's GPS coordinates as
hierarchical keywords. However, there are already some IPTC and XMP fields
available for that information (which can be filled using templates, or the
metadata editor).

I think it could be useful if the reverse geocoding tool could save the City,
State/Province and Country to the IPTC fields. Or even a button in the Metadata
Editor to fill these fields based on geolocation.

This is a feature I saw in the software Photo Mechanic, and I think some people
could find useful.

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

[digikam] [Bug 410275] Tag list disappear when drag and dropping tag to top of the list

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=410275

--- Comment #7 from IWBR  ---
If you look closely, all the tags that appear on the list either contain the
string "cuba" or are subtags of the tag "Cuba" (which is at the top, but
disappears before you can see it). I don't think there is any problem with the
filter. 

But maybe the tags "collapse" too soon, before you can even see the top-level
tag at the root.

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

[digikam] [Bug 410282] Crash when clearing unused tags in the Tag Manager tool.

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=410282

--- Comment #2 from IWBR  ---
I believe it's in the attachment in the bug description.

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

[digikam] [Bug 410282] New: Crash when clearing unused tags in the Tag Manager tool.

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=410282

Bug ID: 410282
   Summary: Crash when clearing unused tags in the Tag Manager
tool.
   Product: digikam
   Version: 6.2.0
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Tags-Manager
  Assignee: digikam-bugs-n...@kde.org
  Reporter: iwannaber...@gmail.com
  Target Milestone: ---

Created attachment 121777
  --> https://bugs.kde.org/attachment.cgi?id=121777=edit
Backtrace of the crash

SUMMARY

It happens quite often, but not always. Sometimes when clearing unused tags
using the Tag Manager tool, digikam freezes and needs to be force closed. In
the last case I saw, it had to clear 7 unused tags. The tags are successfully
cleared, though.

I was running digikam in debug mode, so I could capture the error and get the
backtrace. See attached text file. I hope it helps.

STEPS TO REPRODUCE
1. Make sure there are some unused tags in the tag list (with a 0 next to it).
2. Open the Tag manager tool.
3. Click on Organize, Delete unassigned tags.

OBSERVED RESULT
Digikam freezes.

EXPECTED RESULT
A popup saying how many tags have been cleared should appear.

SOFTWARE/OS VERSIONS
digikam-6.2.0-git-20190722T062931-qtwebkit-x86-64.appimage in Ubuntu 18.04 LTS
with Gnome.

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

[digikam] [Bug 410282] Crash when clearing unused tags in the Tag Manager tool.

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=410282

IWBR  changed:

   What|Removed |Added

 CC||iwannaber...@gmail.com

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

[digikam] [Bug 410275] Tag list disappear when drag and dropping tag to top of the list

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=410275

--- Comment #5 from IWBR  ---
No, the filter seems to work fine. Only words that contain that string ("Cuba"
in the example) are displayed. Also tags that are nested inside, which I think
it's the correct behavior.

Ok ok. I think you were right in the first place. It's a matter of the delay. I
didn't know the root of the Tags (the folder-looking item called Tags) could
also collapse and expand. Now I see that dragging over it also hides the rest
of the tags, without needing to scroll or filter or anything. I guess that I
inadvertently hovered over the "Tags" root and the whole tree collapsed,
without knowing why. That's why it only happened to me when I "scrolled".

I guess that, just because the "Tags" item does not show expand and collapse
arrows like the rest of the tags, I assumed it couldn't be collapsed and
expanded. 

So now I am almost totally confident that this is not a bug. At most, it would
be a usability thing.

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

[digikam] [Bug 410275] Tag list disappear when drag and dropping tag to top of the list

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=410275

--- Comment #3 from IWBR  ---
I believe we are not talking about the same thing. The node does not collapse
or expand, it just vanishes from the list. The tag list does not reappear until
I delete the search term and write it again.

And it only happens when there's a text in the search box, and when scrolling
is needed, and the dragged tag isn't near the top of the list.

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

[digikam] [Bug 406583] Cannot write special characters (è, í, ó) in Tag search box

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=406583

--- Comment #3 from IWBR  ---
Thanks for checking it out, Maik.

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

[digikam] [Bug 410275] Tag list disappear when drag and dropping tag to top of the list

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=410275

IWBR  changed:

   What|Removed |Added

 CC||iwannaber...@gmail.com

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

[digikam] [Bug 410275] New: Tag list disappear when drag and dropping tag to top of the list

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=410275

Bug ID: 410275
   Summary: Tag list disappear when drag and dropping tag to top
of the list
   Product: digikam
   Version: 6.2.0
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: Tags-Keywords
  Assignee: digikam-bugs-n...@kde.org
  Reporter: iwannaber...@gmail.com
  Target Milestone: ---

Created attachment 121773
  --> https://bugs.kde.org/attachment.cgi?id=121773=edit
Screen capture showing this bug

SUMMARY

The summary describes it. I have attached a screen capture so you can see this
exact behavior. I particularly wanted to merge a duplicated tag, so I dragged
the tag to the top of the list (where I wanted to drop it), and the tag list
disappeared.

This does not happen if the current tag list is short enough so all tags are
visible on screen without scrolling up. It doesn't happen either if no term is
used in the search box to restrict the number of results.


STEPS TO REPRODUCE
1. In the Tags panel, search for some word that contains lots of tags, in order
to fill the tag list, so scrolling is needed.
2. Drag one of the tags from the bottom to the top of the list.

OBSERVED RESULT
The tag list disappears, before dropping the tag.

EXPECTED RESULT
Nothing should happen.

SOFTWARE/OS VERSIONS
digikam-6.2.0-git-20190722T062931-qtwebkit-x86-64.appimage in Ubuntu 18.04 LTS
with Gnome.

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

[digikam] [Bug 406583] Cannot write special characters (è, í, ó) in Tag search box

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=406583

--- Comment #1 from IWBR  ---
Hey, sorry to be insistent, but can I bring some attention to this issue?

I have narrowed it down, and it appears that letters with special characters
cannot be written (they appear as plain letters é -> e) only when the
autocomplete suggestion box when typing is present on screen. 

So let's say I have a tag called "María". If I start writing that name, it
would appear as "Maria" (and nothing would come up). But if I start typing a
non-existing tag, so the autocomplete box does not pop up, I can perfectly type
something like "Waría" (and nothing would come up either, because it doesn't
exist).

That makes it harder to find tags with very common names.

PS: Another option could be to be more permissive with search results,
including accented letters even when searching non-accented ones (e.g.
searching "maria" would show "maría, mària, märìa, etc.)

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

[digikam] [Bug 409995] Scan for Faces in video files is not yet supported

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=409995

--- Comment #1 from IWBR  ---
Not a dev, but there is a project to improve the whole face recognition process
in digikam. However, I have not heard anything about recognizing people in
videos, so I wouldn't be optimistic about it, at least in short-medium term.

Probably some of the developers will be able to give you a more specific
answer.

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

[digikam] [Bug 392607] Crash sometimes when applying Tags to images

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=392607

--- Comment #17 from IWBR  ---
I personally have not had that problem in some time (a couple of months). I am
not sure if it has been solved or I just have not repeated the same behavior
that triggered this crash.

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

[digikam] [Bug 406428] Video preview - no sound

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=406428

--- Comment #50 from IWBR  ---
I can confirm the sound also works for me. Good job devs.

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

[digikam] [Bug 386591] Cannot save changes in geolocation coordinates to .RW2 RAW files from a Panasonic FZ300 camera

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=386591

IWBR  changed:

   What|Removed |Added

 CC||iwannaber...@gmail.com

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

[digikam] [Bug 409995] Scan for Faces in video files is not yet supported

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=409995

IWBR  changed:

   What|Removed |Added

 CC||iwannaber...@gmail.com

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

[digikam] [Bug 409990] Wishlist: Apply metadata changes to picture selection

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=409990

--- Comment #6 from IWBR  ---
Well, the two are not mutually exclusive :)

And I think also having the option in the metadata editor would be more
user-friendly.

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

[digikam] [Bug 409990] Wishlist: Apply metadata changes to picture selection

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=409990

--- Comment #4 from IWBR  ---
Sure, no problem. I searched for similar requests before submitting it, but I
must have missed that one.

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

[digikam] [Bug 409990] Wishlist: Apply metadata changes to picture selection

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=409990

--- Comment #2 from IWBR  ---
Yes, I know, but this would be much more flexible. For instance, you could
change camera model, the exposition time, or the IPTC location for multiple
pictures in a click.

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

[digikam] [Bug 409990] Wishlist: Apply metadata changes to picture selection

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=409990

IWBR  changed:

   What|Removed |Added

 CC||iwannaber...@gmail.com

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

[digikam] [Bug 409990] New: Wishlist: Apply metadata changes to picture selection

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=409990

Bug ID: 409990
   Summary: Wishlist: Apply metadata changes to picture selection
   Product: digikam
   Version: 6.2.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Metadata-Editor
  Assignee: digikam-bugs-n...@kde.org
  Reporter: iwannaber...@gmail.com
  Target Milestone: ---

Created attachment 121624
  --> https://bugs.kde.org/attachment.cgi?id=121624=edit
Capture of EasyTag software where a solution similar to the one described in
this report is used.

SUMMARY

After reading this message (
http://digikam.1695700.n4.nabble.com/digiKam-users-Update-metadata-for-multiple-photographs-td4708829.html
) in the mailing list, and having wished for the same thing in the past, I
think it would be convenient to have an option to save a current metadata field
to a selection of photographs using the Metadata Editor. The Batch Queue
Manager could work for some cases, but it is not as flexible.

For instance, you want to add a title and description to all pictures in a
selection, or just edit some XMP field. Instead of going one by one, clicking
on "next", a little button could be added to the left to each field to apply
that change to the picture selection.

I have attached a screenshot of another software that does a similar thing. In
this case, EasyTag, a metadata editor for music files. Notice the little square
buttons at the rightmost part of each field (Title, Artist, etc.). These apply
the current content of the field to all the selection. I think something
similar could work very well for digikam.

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

[digikam] [Bug 384485] Face Regions are deleted when unconfirmed face suggestion is rejected by user

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=384485

--- Comment #6 from IWBR  ---
Created attachment 121195
  --> https://bugs.kde.org/attachment.cgi?id=121195=edit
Redundant buttons when face tagging?

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

[digikam] [Bug 384485] Face Regions are deleted when unconfirmed face suggestion is rejected by user

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=384485

--- Comment #5 from IWBR  ---
Ok, but then it is misleading. Basically you have a text box showing you a name
and asking whether it is right or wrong with big green and red buttons. Most
people will assume that these buttons are meant to confirm if that face
corresponds to that name, not whether that is a face or not. Specially when
these two buttons and the name appear at the same time when the user clicks on
that face.

Moreover, there is a X sign at the top right corner of each face that does
exactly that, remove the face from the image, so the red "minus sign" button
would be redundant.

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

[digikam] [Bug 391840] Timeline does not show any pictures if range is too big

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=391840

--- Comment #10 from IWBR  ---
I no longer have this issue, at least using the linux version of Digikam (in my
new computer I don't have a windows installation, so I can't try it). If it
were for me, you can close it.

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

[digikam] [Bug 384485] Face Regions are deleted when unconfirmed face suggestion is rejected by user

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=384485

--- Comment #3 from IWBR  ---
I just noticed that bug too. It's still present in the last appimage
(digikam-6.2.0-git-20190618T151249-qtwebkit-x86-64.appimage). 

If a suggestion from the "Unconfirmed" list is rejected, it means that that
face does not belong to the person digikam thought it was. But it is still a
face, so it should not be deleted altogether.

When rejecting a confirmation, the face should either return to the "Unknown"
list, or try and suggest another name.

(also, currently "Unconfirmed/Suggested" faces appear in two places in the
Personal panel: within the "Unconfirmed" list, and within each suggested
person's. Maybe just the latter would be enough?)

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

[digikam] [Bug 384485] Face Regions are deleted when unconfirmed face suggestion is rejected by user

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=384485

IWBR  changed:

   What|Removed |Added

 CC||iwannaber...@gmail.com

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

[digikam] [Bug 406428] Video preview - no sound

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=406428

IWBR  changed:

   What|Removed |Added

 CC||iwannaber...@gmail.com

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

[digikam] [Bug 409153] New: Improvement suggestion: timeline for tags.

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=409153

Bug ID: 409153
   Summary: Improvement suggestion: timeline for tags.
   Product: digikam
   Version: 6.2.0
  Platform: Other
OS: All
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Searches-TimeLine
  Assignee: digikam-bugs-n...@kde.org
  Reporter: iwannaber...@gmail.com
  Target Milestone: ---

SUMMARY

Currently there's a timeline panel that shows an histogram of the number of
pictures per unit of time, and there's the possibility of saving searches for
specific timeframes. 

However, I feel there's a degree of overlap between the Timeline and Dates
panels and their function is redundant: both show pictures classified by units
of time (year and month) which are displayed chronologically. 

I think the timeline panel has lots of potential if combined with tags (or even
People). For instance, showing the histogram of a Tag. Or overlapping
histograms of different colors for a selection of tags. (e.g.: to visualize the
time frame of the weddings I've attended, or when you last had contact with
some friend).

That's it, just an idea.

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

[digikam] [Bug 409153] Improvement suggestion: timeline for tags.

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=409153

IWBR  changed:

   What|Removed |Added

 CC||iwannaber...@gmail.com

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

[digikam] [Bug 408982] Not being able to write person name when tagging faces despite text field having focus

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=408982

--- Comment #11 from IWBR  ---
Well, I see that you already fixed it, but selecting a picture using the first
letter also happens in the Windows version.

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

[digikam] [Bug 408982] Not being able to write person name when tagging faces despite text field having focus

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=408982

--- Comment #7 from IWBR  ---
That is weird. I'll try it in my windows partition, to see if it also happens,
and report back.

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

[digikam] [Bug 408982] Not being able to write person name when tagging faces despite text field having focus

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=408982

--- Comment #5 from IWBR  ---
If I press "G" on the Thumbnail or Preview view, a picture in the album whose
filename starts by G is selected. Same for other letters. For instance, I can
switch between game-of-thrones.jpeg, 2604185h688.jpg, and
b3dbddb3-game-of-thrones-season-8-episode-4.jpg by pressing the keys "G", "2"
and "B". 

In the preview view (where the bug seems to happen), it only jumps from picture
to picture if the Thumbbar (Control+T) is "selected"/"focused". If you click on
the picture preview itself, the thumbbar is no longer "selected", and selecting
files by pressing those keys is not enabled anymore (and I presume face names
can be entered just fine).

So I think that the issue is that, when you switch from one picture to the next
in the thumbbar, the thumbbar is still "selected"/"focused" instead of the
picture itself, and even if you see a vertical cursor blinking on the face name
text field, typing a name will act on the thumbbar (by changing the picture),
not on the text field.

To solve it, I think either the picture preview gets the focus automatically,
or do not show a cursor blinking on the text field as if it is waiting for text
to be written.

(do you follow what I mean?)

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

[digikam] [Bug 408982] Not being able to write person name when tagging faces despite text field having focus

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=408982

--- Comment #3 from IWBR  ---
Sorry, I forgot to mention, changing the locale (with LANG=C) does not change
that behavior. I don't think it has anything to do with it.

PS: I also tried to add captions to the screencast, but I didn't find an easy
way. Any recommendations for linux software that can do that easily?

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

[digikam] [Bug 408982] Not being able to write person name when tagging faces despite text field having focus

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=408982

--- Comment #2 from IWBR  ---
I made a quick screencast.

https://imgur.com/a/GnTDxXe

In the video, first I enter a picture with detected faces, and I type the name
of the face that already has the focus (Arya). As you can see, I can enter her
name just fine. Then I switch to another one in the same picture (Jon Snow). So
far so good.

However, when I change to another picture, and I start typing the name of the
person who has the focus (in this case, "Grey Worm", at the right of the
picture), instead of seeing the text, digikam goes to the first picture of that
album that starts with the letter I just typed. In this case, "G", so it goes
to a file called "Game-of-thrones.jpeg", you can see the filename at the bottom
left corner. 

I hope now it's a bit more clear. If I manually click on the text field I want
to input before writing, then it works just fine. But otherwise, it is
misleading because a seemingly active text field is not actually "active".


And yeah, I had thought about compiling and creating a digikam repository for
ubuntu, so users could install the latest versions using apt-get command, but
it's not a very straightforward process and I have to look into it. Ideally, it
should be as automatic as possible. I'll set up a virtual machine and start
experimenting soon.

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

[digikam] [Bug 408982] Not being able to write person name when tagging faces despite text field having focus

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=408982

IWBR  changed:

   What|Removed |Added

 CC||iwannaber...@gmail.com

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

[digikam] [Bug 408982] New: Not being able to write person name when tagging faces despite text field having focus

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=408982

Bug ID: 408982
   Summary: Not being able to write person name when tagging faces
despite text field having focus
   Product: digikam
   Version: 6.2.0
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Faces-Workflow
  Assignee: digikam-bugs-n...@kde.org
  Reporter: iwannaber...@gmail.com
  Target Milestone: ---

SUMMARY

When tagging already detected faces (that is, digikam already has the rectangle
over the face of several pictures, but without a name yet), sometimes instead
of writing the name on the text field, digikam interprets the keystroke as a
keyboard shortcut, despite the cursor being a vertical bar blinking in the text
field.

Specifically, it happens when tagging a face in a second picture after faces in
a previous picture have been tagged.

I hope it's not too difficult to understand the way I explained. It's actually
quite simple once you have seen it in action.


STEPS TO REPRODUCE
1. Scan several pictures in a folder for faces. (via right-click, scan for
faces).
2. Open the first one (double click), click on the text field under a detected
face, and write the name. Click "Confirm".
3. Hover over to another face, or go to the following picture where a face is.
4. Observe how the cursor on the face rectangle text field is blinking. Start
typing the name.

OBSERVED RESULT

Keyboard shortcuts (e.g. going to pictures named with the letter you just typed
in the album) are interpreted instead of writing the name of the person.

EXPECTED RESULT
If the textbox is selected and the cursor is a vertical bar that blinks, it
should write the name of the person, instead of using keyboard shortcuts in the
album. 


SOFTWARE/OS VERSIONS
digikam-6.2.0-git-20190613T125237-qtwebkit-x86-64.appimage in Ubuntu 18.04 LTS.

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

[digikam] [Bug 384396] Wish: display faces sorted by similarity (pre-grouped) instead of album/time/..

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=384396

--- Comment #6 from IWBR  ---
In theory, this was proposed as part of the improvements for the GSoC 2019 in
the Faces Management workflow improvements project. However, it was included as
one of the last things to do (see point 4 at
https://docs.google.com/document/d/1EPACR_JgZ5BWfbuqOP_Xlyd_cldEIKSd7n4TTgZ495Q/edit
), so I don't know if that option will be ready this summer.

I agree that it is important, and all other software dealing with picture
recognition has this feature.

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

[digikam] [Bug 404167] improve confirmation process

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=404167

IWBR  changed:

   What|Removed |Added

 CC||iwannaber...@gmail.com

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

[digikam] [Bug 406937] Cannot change icon theme in appimage

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=406937

--- Comment #18 from IWBR  ---
Thanks. I see now that some themes lack some icons. But it's nice to be able to
choose again.

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

[digikam] [Bug 408687] "Failed to update file timestamp" despite date being changed successfully in Adjust Date and Time tool

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=408687

--- Comment #2 from IWBR  ---
Ok. My library is mounted in a sshfs network share. I'll check out what can be
happening here.

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

[digikam] [Bug 408687] "Failed to update file timestamp" despite date being changed successfully in Adjust Date and Time tool

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=408687

IWBR  changed:

   What|Removed |Added

 CC||iwannaber...@gmail.com

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

[digikam] [Bug 408687] New: "Failed to update file timestamp" despite date being changed successfully in Adjust Date and Time tool

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=408687

Bug ID: 408687
   Summary: "Failed to update file timestamp" despite date being
changed successfully in Adjust Date and Time tool
   Product: digikam
   Version: 6.2.0
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Metadata-TimeAdjust
  Assignee: digikam-bugs-n...@kde.org
  Reporter: iwannaber...@gmail.com
  Target Milestone: ---

SUMMARY

I frequently use the Adjust Date and Time for adding a date to pictures without
metadata.

I have observed that, sometimes, I correct the date, save it to the metadata,
and when I click on "Apply" I get the "Failed to update file timestamp" error. 

However, when inspecting the metadata, the new date is there. When looking at
the console, I can confirm that the metadata was saved with a message like:
"Digikam::MetaEngine::save: Metadata for file "Picture 20190221_191536.jpg"
written to file."

Moreover, after closing the adjust date and time tool, the date is not
refreshed in the miniature/thumbnail view in digikam, and I need to manually
reread the metadata from the file so the changes are shown.

I have recorded a short clip showing this behavior: https://imgur.com/a/pQUgO5O


STEPS TO REPRODUCE
1. Select a picture or group of pictures
2. Open the Adjust Date and Time tool
3. Change the date using any option (e.g. filename timestamp, or directly
entering the date)
4. Click "Apply"

OBSERVED RESULT
"Failed to update file timestamp" appears next to each picture. The metadata is
not refreshed in digikam.

EXPECTED RESULT
Indicate that the metadata has been written successfully and refresh that
metadata in digikam.

SOFTWARE/OS VERSIONS
digikam-6.2.0-git-20190612T102714-qtwebkit-x86-64.appdata in Ubuntu 18.04

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

[digikam] [Bug 399034] Pictures are not centered in the map

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=399034

--- Comment #5 from IWBR  ---
A similar issue is present when using the right map panel. The picture location
is not updated until another picture is clicked while the panel is open.

I've recorded two short clips, one showing the bug with the top map view, and
another one for the lateral right map panel. They can be watched here:
https://imgur.com/a/JEblJIk

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

[digikam] [Bug 408667] In reverse geocoding, whow which address element correspond to each name

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=408667

IWBR  changed:

   What|Removed |Added

 CC||iwannaber...@gmail.com

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

[digikam] [Bug 408667] New: In reverse geocoding, whow which address element correspond to each name

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=408667

Bug ID: 408667
   Summary: In reverse geocoding, whow which address element
correspond to each name
   Product: digikam
   Version: 6.2.0
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: Geolocation-ReverseGeoCoding
  Assignee: digikam-bugs-n...@kde.org
  Reporter: iwannaber...@gmail.com
  Target Milestone: ---

Created attachment 120852
  --> https://bugs.kde.org/attachment.cgi?id=120852=edit
Reverse geocoding tool, showing the corresponding full tag tree for a picture

SUMMARY

In the reverse geocoding tool, you can select which address elements you want
to use to tag your pictures. However, often not all elements are available, and
digikam will only show you those that found.

In order to fine tune which elements are which, and fine-tune the structure, it
would be useful if it indicated which address element a specific place is,
either by hovering your mouse over it, or displaying it next to the name. (e.g.
hovering over the word "New York City" you should see "{City}".

See the attached screenshot. I basically would like to know which of the words
in Green correspond to the words in Red.

STEPS TO REPRODUCE
1. Reverse-geolocate a picture using all address elements.
2. Observe the results in the tool's tree view.

SOFTWARE/OS VERSIONS
digikam-6.2.0-git-20190612T102714-qtwebkit-x86-64.appimage in Ubuntu 18.04

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

[digikam] [Bug 397872] Slight improvement of Geolocation window layout for better efficiency

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=397872

IWBR  changed:

   What|Removed |Added

 CC||iwannaber...@gmail.com

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

[digikam] [Bug 408666] New: Reverse geocoding tool, confusing dialog question phrasing

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=408666

Bug ID: 408666
   Summary: Reverse geocoding tool, confusing dialog question
phrasing
   Product: digikam
   Version: 6.2.0
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: Geolocation-ReverseGeoCoding
  Assignee: digikam-bugs-n...@kde.org
  Reporter: iwannaber...@gmail.com
  Target Milestone: ---

Created attachment 120851
  --> https://bugs.kde.org/attachment.cgi?id=120851=edit
Screen capture of said dialog screen

SUMMARY

In the reverse geocoding tool, when cancelling the tagging process before
finishing, a dialog asks whether you want to keep tags in pictures so far, or
if you want to discard all of them, and the possible answers: Yes or No. (see
attachment)

Either change the buttons to something like (Keep and Discard) or rephrase the
text so it's a yes/no question.

STEPS TO REPRODUCE
1. Enter the reverse-geotagging panel in the Geolocation tool. 
2. Start tagging some pictures.
3. Cancel the process before finishing.


SOFTWARE/OS VERSIONS
digikam-6.2.0-git-20190612T102714-qtwebkit-x86-64.appimage in Ubuntu 18.04

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

[digikam] [Bug 406937] Cannot change icon theme in appimage

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=406937

--- Comment #15 from IWBR  ---
Ok, last request, I promise.

Could you please add the "Humanity" icon theme (the default Ubuntu look) to the
whitelist? (Ambiance seems to be the GTK/Gnome shell theme, not the icon
theme).

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

[digikam] [Bug 382825] Settings/Metadata/Advanced: why limited to Tags, rating and Comments ?

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=382825

IWBR  changed:

   What|Removed |Added

 CC||iwannaber...@gmail.com

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

[digikam] [Bug 406937] Cannot change icon theme in appimage

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=406937

--- Comment #13 from IWBR  ---
Yay! Now the icons in the tool panel are displayed correctly.

By the way, the Theme is always Breeze regardless of the selected option
(System theme, Breeze and Breeze dark), right? Is it technically possible to
select the system theme, so I could use Ubuntu's "Ambiance" icons for the
Albums panel?

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

[digikam] [Bug 408261] In Metadata editor, "Ok" and "Apply" buttons should save changes for all tabs, not just the active one.

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=408261

--- Comment #2 from IWBR  ---
Thanks Maik!

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

[digikam] [Bug 408261] In Metadata editor, "Ok" and "Apply" buttons should save changes for all tabs, not just the active one.

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=408261

IWBR  changed:

   What|Removed |Added

 CC||iwannaber...@gmail.com

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

[digikam] [Bug 408261] New: In Metadata editor, "Ok" and "Apply" buttons should save changes for all tabs, not just the active one.

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=408261

Bug ID: 408261
   Summary: In Metadata editor, "Ok" and "Apply" buttons should
save changes for all tabs, not just the active one.
   Product: digikam
   Version: 6.2.0
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: Metadata-Editor
  Assignee: digikam-bugs-n...@kde.org
  Reporter: iwannaber...@gmail.com
  Target Milestone: ---

SUMMARY

When using the metadata editor, there are three tabs: Edit EXIF, IPTC, and XMP.
If any changes are made in several tabs and the Ok or Apply buttons are used,
only those changes in the current/active tab will be saved. 

Right now, you have to click "Apply" before changing to another tab, otherwise
the edits are lost.

I personally think the "Ok" and "Apply" buttons should save changes made in the
three tabs.

STEPS TO REPRODUCE
1. Open metadata editor
2. Do some changes on one tab (e.g. change EXIF's Original date and time)
3. Move to another tab (e.g. XMP)
4. Click "Apply"
5. Go back to the previous tab.

OBSERVED RESULT
Changes in the previous tab have been lost (not applied).

EXPECTED RESULT
Changes should have been applied even if that tab did not have the focus.

SOFTWARE/OS VERSIONS
Ubuntu 18.04 with Gnome and
digikam-6.2.0-git-20190522T104638-qtwebkit-x86-64.appimage

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

[digikam] [Bug 408155] Workflow improvement : simply drag & drop pictures from Thumbnail to Map area

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=408155

IWBR  changed:

   What|Removed |Added

 CC||iwannaber...@gmail.com

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

[digikam] [Bug 407993] New: Feature request: feedback when deleting unassigned tags in Tag Manager

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=407993

Bug ID: 407993
   Summary: Feature request: feedback when deleting unassigned
tags in Tag Manager
   Product: digikam
   Version: 6.2.0
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Tags-Manager
  Assignee: digikam-bugs-n...@kde.org
  Reporter: iwannaber...@gmail.com
  Target Milestone: ---

SUMMARY

When using the "Delete unassigned tags" in the Tag tool, you click on it... and
nothing happens.

Well, yes, it works and empty tags get cleaned up. But the user does not have
any kind of feedback after clicking that button, which may lead to think that
nothing happened.

Just a "Done." message or, even better, "xx tags were deleted." would be great.
Just like when you scan for new items or clean the database.



SOFTWARE/OS VERSIONS
digikam-6.2.0-git-20190522T104638-qtwebkit-x86-64.appimage in Ubuntu 18.04 with
Gnome.

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

[digikam] [Bug 407993] Feature request: feedback when deleting unassigned tags in Tag Manager

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=407993

IWBR  changed:

   What|Removed |Added

 CC||iwannaber...@gmail.com

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

[digikam] [Bug 402894] Display of original image

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=402894

--- Comment #12 from IWBR  ---
Yes, yes, of course. I like versioning the way it is. That's not the point. 

I just found it confusing that the original and the new version were both shown
regardless of the settings, but only if "save changes" was used in the editor,
not "save as new version".

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

[digikam] [Bug 402894] Display of original image

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=402894

--- Comment #10 from IWBR  ---
Joining the conversation since I had the same thoughts about versioning, as
stated here:
http://digikam.1695700.n4.nabble.com/digiKam-users-Showing-original-and-versions-Is-it-working-alright-td4708568.html

I personally thought that "save changes" in the image editor would overwrite
the original, and "save as new version" would be the non-destructive editing
(but I am wrong).

The fact that the versioning panel actually detects both way of saving a
picture as original and version, respectively, makes it more confusing. I would
personally hide the original in any case. 

But not for RAW images, that's a separate story and I think it's OK the way it
is now.

PS: Also, it would be cool if you could toggle displaying the
original/intermediate images in the versioning panel itself, instead of having
to go to the settings.

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

[digikam] [Bug 402894] Display of original image

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=402894

IWBR  changed:

   What|Removed |Added

 CC||iwannaber...@gmail.com

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

[digikam] [Bug 406855] Feature request: date from filename

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=406855

--- Comment #15 from IWBR  ---
It's me again.

I found two pictures whose date was not detected correctly from the filename:

14-09-04_1918.jpg -> 9/4/1918 0:00:00
14-09-04_1937.jpg -> 9/4/1937 0:00:00

I guess it automatically assumes that "19xx" is the year. Again, not a big
deal.

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

[digikam] [Bug 407947] Crash while updating fingerprints.

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=407947

--- Comment #2 from IWBR  ---
"Unsupported image format". Well, yeah.

Why with that file in particular? Couldn't digikam skip non-picture files?

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

[digikam] [Bug 407947] Crash while updating fingerprints.

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=407947

IWBR  changed:

   What|Removed |Added

 CC||iwannaber...@gmail.com

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

[digikam] [Bug 407947] New: Crash while updating fingerprints.

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=407947

Bug ID: 407947
   Summary: Crash while updating fingerprints.
   Product: digikam
   Version: 6.2.0
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Searches-Similarity
  Assignee: digikam-bugs-n...@kde.org
  Reporter: iwannaber...@gmail.com
  Target Milestone: ---

SUMMARY

Digikam crashed when updating the fingerprints (reached 73%). 
Here's the console full output with the backtrace:
https://drive.google.com/open?id=1wgXbgOofUZW8Q9_yCZbRfs--wItl8NXX


STEPS TO REPRODUCE
1. Go to the Similarity panel. 
2. Click on Update fingerprints.


SOFTWARE/OS VERSIONS
Ubuntu 18.04 with Gnome
digikam-6.2.0-git-20190522T104638-qtwebkit-x86-64.appimage

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

[digikam] [Bug 407946] Duplicates search should perform the search automatically

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=407946

--- Comment #3 from IWBR  ---
Oh, and I forgot, I would perform the fingerprint update on the go, as new
files are imported into Digikam. At least if the main fingerprint update has
already been performed manually. (Maybe an option in the main settings, to
enable o disable automatic fingerprints?).

Otherwise the user needs to remember to regularly update the fingerprints by
going to that panel an clicking that button. (And the same same applies to face
detection/recognition, but that's another topic).

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

[digikam] [Bug 407946] Duplicates search should perform the search automatically

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=407946

--- Comment #2 from IWBR  ---
I mean, it allows for flexibility in the search, which is great, but it's not
user friendly at all.

I would personally put that Combobox in an "Advanced" section, and by default
search only in Albums or Tags, based on which tab is selected at that moment. 

Same with the "Similarity range" and "Restriction" options.

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

[digikam] [Bug 407946] New: Duplicates search should perform the search automatically

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=407946

Bug ID: 407946
   Summary: Duplicates search should perform the search
automatically
   Product: digikam
   Version: 6.2.0
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: Searches-Similarity
  Assignee: digikam-bugs-n...@kde.org
  Reporter: iwannaber...@gmail.com
  Target Milestone: ---

SUMMARY

Performing a duplicate search is quite cumbersome at the moment. 

First, you must right click the Album or Tag and select "Find Duplicates...".
Digikam then just opens the Similarity panel with the Album or Tag preselected
on the dropdown list, but does nothing.

The user then needs to select the appropriate "Restrict to" option ("Albums but
no tags, or "Tags but not albums"), otherwise the search won't work, and
finally click on the "Find duplicates" button.

Moreover, that panel will show the results of the last similarity search
performed by the user (even from the "Image" tab). I think old results should
be cleared up before performing the new search.

STEPS TO REPRODUCE
1. Right click on any Album or Tag.
2. Click on "Find duplicates...".

OBSERVED RESULT
The Similarity panel opens. Said Album/Tag is pre-selected on the list.
If a previous search had been performed, the results are still there.

EXPECTED RESULT
The search is performed automatically and results (duplicated pictures) are
shown.

SOFTWARE/OS VERSIONS
Ubuntu 18.04 with Gnome
digikam-6.2.0-git-20190522T104638-qtwebkit-x86-64.appimage

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

[digikam] [Bug 407946] Duplicates search should perform the search automatically

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=407946

IWBR  changed:

   What|Removed |Added

 CC||iwannaber...@gmail.com

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

[digikam] [Bug 392607] Crash sometimes when applying Tags to images

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=392607

--- Comment #15 from IWBR  ---
That's too bad. I'll keep it in mind for the next time.

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

[digikam] [Bug 392607] Crash sometimes when applying Tags to images

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=392607

--- Comment #13 from IWBR  ---
Full logfile for bug #407914:

https://drive.google.com/open?id=1nwxNUtGug_BcikkdFOr5VDyyt8Nrrmu1


The beginning is truncated due to the limitations in gnome-terminal. I have
redacted people's names in the log file due to privacy concerns.

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

[digikam] [Bug 407914] Crash when tagging, finding duplicates, moving between albums...

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=407914

IWBR  changed:

   What|Removed |Added

 CC||iwannaber...@gmail.com

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

[digikam] [Bug 407914] New: Crash when tagging, finding duplicates, moving between albums...

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=407914

Bug ID: 407914
   Summary: Crash when tagging, finding duplicates, moving between
albums...
   Product: digikam
   Version: 6.2.0
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: digikam-bugs-n...@kde.org
  Reporter: iwannaber...@gmail.com
  Target Milestone: ---

SUMMARY

My digikam crashed when I was using it in debug mode, so I thought of reporting
the output in case it is of interest.

This crash is quite nonspecific, because I don't recall doing anything special
at the moment. I was using the "Find similar" on pictures, deleting duplicates,
and switching back to the original album where the picture was stored, that's
all.

Here are the last lines before the crash:



Digikam::DImg::load: "/media/sshfs/nas/media/usb2/Fotos/FotosUser1/Canada
Others/2008-10 Visita   Toronto/imgp3589.jpg"  : JPEG file identified
Digikam::DImg::load: "/media/sshfs/nas/media/usb2/Fotos/FotosUser1/Canada
Others/2008-10 Visita   Toronto/imgp3589.jpg"  : JPEG file identified
Digikam::ActionThreadBase::setMaximumNumberOfThreads: Using  8  CPU core to run
threads
[New Thread 0x7fffad1eb700 (LWP 29333)]
Digikam::ActionThreadBase::setMaximumNumberOfThreads: Using  8  CPU core to run
threads
Digikam::ActionThreadBase::run: Action Thread run  1  new jobs
[New Thread 0x7fff93fff700 (LWP 29335)]
[New Thread 0x7fff937fe700 (LWP 29334)]
Digikam::ActionThreadBase::run: Action Thread run  1  new jobs
[New Thread 0x7fff91ffb700 (LWP 29336)]
Digikam::ActionThreadBase::slotJobFinished: One job is done
Digikam::ActionThreadBase::cancel: Cancel Main Thread
[Thread 0x7fffad1eb700 (LWP 29333) exited]
[Thread 0x7fff937fe700 (LWP 29334) exited]
Digikam::ActionThreadBase::slotJobFinished: One job is done
Digikam::ActionThreadBase::cancel: Cancel Main Thread
[Thread 0x7fff93fff700 (LWP 29335) exited]
[Thread 0x7fff91ffb700 (LWP 29336) exited]
Digikam::DeleteDialog::slotUser1Clicked: setShowTrashDeleteDialog  true
Digikam::DIO::processJob: Number of files to be deleted: 1
Digikam::ActionThreadBase::setMaximumNumberOfThreads: Using  8  CPU core to run
threads
[New Thread 0x7fff91ffb700 (LWP 29337)]
Digikam::AlbumManager::slotImagesDeleted: Got image deletion notification from
ItemViewUtilities for  1  images.
Digikam::ActionThreadBase::run: Action Thread run  1  new jobs
[New Thread 0x7fff93fff700 (LWP 29338)]
Digikam::DeleteJob::run: Deleting:   
"/media/sshfs/nas/media/usb2/Fotos/FotosUser1/Canada Others/Canadà 08-09 - the
canadian life (2)/9316_1253175769222_1224387293_792729_4825454_n.jpg"
Digikam::DeleteJob::run: File exists? true
Digikam::DeleteJob::run: Is to trash? true
Digikam::DTrash::deleteImage: DTrash: Image album root path:
"/media/sshfs/nas/media/usb2/Fotos/FotosUser1"
Digikam::DTrash::prepareCollectionTrash: Trash folder for collection: 
"/media/sshfs/nas/media/usb2/Fotos/FotosUser1/.dtrash"
Digikam::IOJobsThread::slotOneJobFinished: Thread Finished
Digikam::ActionThreadBase::slotJobFinished: One job is done
[Thread 0x7fff91ffb700 (LWP 29337) exited]
Digikam::ActionThreadBase::cancel: Cancel Main Thread
[Thread 0x7fff93fff700 (LWP 29338) exited]
Digikam::ActionThreadBase::setMaximumNumberOfThreads: Using  8  CPU core to run
threads
[New Thread 0x7fff93fff700 (LWP 29339)]
Digikam::ActionThreadBase::run: Action Thread run  1  new jobs
[New Thread 0x7fff91ffb700 (LWP 29340)]
Digikam::ScanController::slotRelaxedScanning: Starting scan!
Digikam::ActionThreadBase::cancel: Cancel Main Thread
[Thread 0x7fff93fff700 (LWP 29339) exited]
Digikam::ActionThreadBase::slotJobFinished: One job is done
Digikam::ActionThreadBase::cancel: Cancel Main Thread
[Thread 0x7fff91ffb700 (LWP 29340) exited]
Digikam::ActionThreadBase::setMaximumNumberOfThreads: Using  8  CPU core to run
threads
[New Thread 0x7fff91ffb700 (LWP 29341)]
Digikam::ActionThreadBase::run: Action Thread run  1  new jobs
[New Thread 0x7fff93fff700 (LWP 29342)]
Digikam::ActionThreadBase::slotJobFinished: One job is done
Digikam::ActionThreadBase::cancel: Cancel Main Thread
[Thread 0x7fff91ffb700 (LWP 29341) exited]
[Thread 0x7fff93fff700 (LWP 29342) exited]
Digikam::ItemMarkerTiler::slotSourceModelReset: 
Digikam::ItemMarkerTiler::slotSourceModelReset: 
Digikam::ActionThreadBase::setMaximumNumberOfThreads: Using  8  CPU core to run
threads
[New Thread 0x7fff93fff700 (LWP 29343)]
Digikam::ActionThreadBase::run: Action Thread run  1  new jobs
[New Thread 0x7fff91ffb700 (LWP 29344)]
Digikam::ActionThreadBase::cancel: Cancel Main Thread
Digikam::ActionThreadBase::slotJobFinished: One job is done
[Thread 0x7fff93fff700 (LWP 29343) exited]
Digikam::ActionThreadBase::cancel: Cancel Main Thread
[Thread 0x7fff91ffb700 (LWP 29344) exited]
Digikam::ItemMarkerTiler::slotSourceModelReset: 

Thread 1 "digikam" received signal SIGSEGV, Segmentation 

[digikam] [Bug 406937] Cannot change icon theme in appimage

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=406937

--- Comment #2 from IWBR  ---
I just realized that the icon theme loads correctly when the Tree View Icon
Size is set to 32, 48 or 64, but not 16 or 22. Maybe the icon theme does not
have icon for the smallest sizes?

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

[digikam] [Bug 407866] New: Feature request: sync People with true Keywords

[IWBR]

https://bugs.kde.org/show_bug.cgi?id=407866

Bug ID: 407866
   Summary: Feature request: sync People with true Keywords
   Product: digikam
   Version: 6.2.0
  Platform: unspecified
OS: All
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Faces-Workflow
  Assignee: digikam-bugs-n...@kde.org
  Reporter: iwannaber...@gmail.com
  Target Milestone: ---

SUMMARY

On the context of the GSoC 2019 face workflow improvement project, face
rectangles and true keywords will be separated and used independently (just
like labels, date, and location). 

However, for interoperability purposes, some users may find interesting to have
matching keywords with the names of the people that appear in a photo. That
way, software that lacks face management but can read keywords, can also be
used to search pictures with certain people in it.

I propose that option to be added to the Tag manager tool, under the "Organize"
drop-down menu.

That option would just copy the name of the face rectangles in the form of a
keyword to a selection or to all pictures that lack it (yes, that can be a
lengthy process). Moreover, similar to the current "People" pseudo-tag that
gets added automatically, I propose that the user can choose a custom keyword
under which all keywords with people names will be written.

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