[digikam] [Bug 474265] Crash when I start digikam:FATAL:credentials.cc (Trace point triggered).

2023-12-23 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=474265

--- Comment #15 from Kristian Karl  ---
I downloaded and tested: digiKam-8.3.0-20231223T122431-x86-64.appimage (which
is a later date than 20231222T162413)
I'm afraid that it still crashes the same way:

=START==
❯ ./digiKam-8.3.0-20231223T122431-x86-64.appimage 
-- digiKam Linux AppImage Bundle
-- Use 'help' as CLI argument to know all available options for digiKam
application.
-- Notes: to integrate this bundle to your desktop, use AppImageLauncher.
--to enable all debug messages on the console, use 'export
QT_LOGGING_RULES="digikam*=true"'.
--to extract the bundle contents locally, use option
'--appimage-extract' on the command line.
-- Detected host Linux ubuntu-64-24.4
-- AppImage mounted directory: /tmp/.mount_digiKajEFRFF
Check library libudev.so.0
Check library libxcb-dri3.so.0
Check library libcrypto.so.1.1
Check library libssl.so.1.1
Check library libnss3.so
Check library libnssutil3.so
Check library libsmime3.so
Check library libgmodule-2.0.so.0
Check library libgnutls.so.30
-- Preloading shared libs:
:/usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0:/usr/lib/x86_64-linux-gnu/libnss3.so:/usr/lib/x86_64-linux-gnu/libnssutil3.so:/usr/lib/x86_64-linux-gnu/libsmime3.so:/usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0:/usr/lib/x86_64-linux-gnu/libgnutls.so.30
unknown: EGL not available
Digikam::DPluginLoader::Private::loadPlugins: Ignoring the following plugin
since it couldn't be loaded:
"/tmp/.mount_digiKajEFRFF/usr/plugins/digikam/marble/CompassFloatItem.so"
Digikam::DPluginLoader::Private::loadPlugins: Ignoring the following plugin
since it couldn't be loaded:
"/tmp/.mount_digiKajEFRFF/usr/plugins/digikam/marble/MapScaleFloatItem.so"
Digikam::DPluginLoader::Private::loadPlugins: Ignoring the following plugin
since it couldn't be loaded:
"/tmp/.mount_digiKajEFRFF/usr/plugins/digikam/marble/MeasureTool.so"
Digikam::DPluginLoader::Private::loadPlugins: Ignoring the following plugin
since it couldn't be loaded:
"/tmp/.mount_digiKajEFRFF/usr/plugins/digikam/marble/NavigationFloatItem.so"
Digikam::DPluginLoader::Private::loadPlugins: Ignoring the following plugin
since it couldn't be loaded:
"/tmp/.mount_digiKajEFRFF/usr/plugins/digikam/marble/NominatimReverseGeocodingPlugin.so"
Digikam::DPluginLoader::Private::loadPlugins: Ignoring the following plugin
since it couldn't be loaded:
"/tmp/.mount_digiKajEFRFF/usr/plugins/digikam/marble/OsmPlugin.so"
Digikam::DPluginLoader::Private::loadPlugins: Ignoring the following plugin
since it couldn't be loaded:
"/tmp/.mount_digiKajEFRFF/usr/plugins/digikam/marble/OverviewMap.so"
[52986:52986:1223/162758.801109:FATAL:credentials.cc(125)] Check failed: . :
Permission denied (13)
/tmp/.mount_digiKajEFRFF/AppRun: line 205: 52986 Trace/breakpoint trap   (core
dumped) digikam $@
=END==

Thanks everyone for all your awesome work on Digikam this year and Merry
Christmas
Best Kristian

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

[digikam] [Bug 474265] Crash when I start digikam:FATAL:credentials.cc (Trace point triggered).

2023-12-22 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=474265

--- Comment #12 from Kristian Karl  ---
Maybe related: https://bugs.launchpad.net/ubuntu/+source/digikam/+bug/2046844

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

[digikam] [Bug 474265] Crash when I start digikam:FATAL:credentials.cc (Trace point triggered).

2023-12-22 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=474265

Kristian Karl  changed:

   What|Removed |Added

 CC||kristian.hermann.karl@gmail
   ||.com

--- Comment #11 from Kristian Karl  ---
I have observed maybe the same issue.
When launching the digikam appimage: 

=START==
./digiKam-8.3.0-20231221T191139-x86-64.appimage
:
Digikam::FaceDbSchemaUpdater::startUpdates: Face database: have a structure
version  "4"
Digikam::FacialRecognitionWrapper::Private::Private: Face database ready for
use
Digikam::OpenfacePreprocessor::loadModels: Start reading shape predictor file
Digikam::OpenfacePreprocessor::loadModels: Finish reading shape predictor file
Digikam::DNNFaceExtractor::loadModels: Extractor model:
"/home/krikar/.local/share/digikam/facesengine/openface_nn4.small2.v1.t7"
Digikam::FacePipeline::construct: Face PipeLine: add database writer
Digikam::FacePipeline::construct: Face PipeLine: add faces trainer
Digikam::FacePipeline::construct: Face PipeLine: add database writer
Digikam::FacePipeline::construct: Face PipeLine: add faces trainer
[262743:262743:1222/103917.435213:FATAL:credentials.cc(125)] Check failed: . :
Permission denied (13)
/tmp/.mount_digiKaxCPmwR/AppRun: line 205: 262743 Trace/breakpoint trap   (core
dumped) digikam $@
=END==


Launching it with gdb (using local compiled latest from master):

=START==
gdb digikam
:
digikam.facedb: Extractor model:
"/home/krikar/.local/share/digikam/facesengine/openface_nn4.small2.v1.t7"
digikam.general: Face PipeLine: add database writer
digikam.general: Face PipeLine: add faces trainer
digikam.general: Face PipeLine: add database writer
digikam.general: Face PipeLine: add faces trainer
[New Thread 0x7fffb92be6c0 (LWP 263127)]
[New Thread 0x7fffb8abd6c0 (LWP 263128)]
[New Thread 0x7fffa3fff6c0 (LWP 263129)]
[Thread 0x7fffa3fff6c0 (LWP 263129) exited]
[Thread 0x7fffb92be6c0 (LWP 263127) exited]
[Thread 0x7fffb8abd6c0 (LWP 263128) exited]
[New Thread 0x7fffb8abd6c0 (LWP 263130)]
[New Thread 0x7fffb92be6c0 (LWP 263131)]
[New Thread 0x7fffa3fff6c0 (LWP 263132)]
[Thread 0x7fffa3fff6c0 (LWP 263132) exited]
[Thread 0x7fffb8abd6c0 (LWP 263130) exited]
[Thread 0x7fffb92be6c0 (LWP 263131) exited]
[New Thread 0x7fffb92be6c0 (LWP 263133)]
[263108:263108:1222/104110.026179:FATAL:credentials.cc(125)] Check failed: . :
Permission denied (13)

Thread 1 "digikam" received signal SIGTRAP, Trace/breakpoint trap.
0x7fffe79d7b13 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
(gdb) bt
#0  0x7fffe79d7b13 in ??? () at
/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#1  0x0029 in ??? ()
#2  0x55aef2c0 in ??? ()
#3  0x5913bfc0 in ??? ()
#4  0x7383e758 in _nl_make_l10nflist
(l10nfile_list=0x73e62478 ,
std::allocator >+16>, 
l10nfile_list@entry=0x66, dirlist=0x73e62630 ,
std::allocator >+24> "\360\336\324\363\377\177",
dirlist@entry=0x739c9870 <_nl_default_dirname> "/usr/share/locale",
dirlist_len=140737488340368, mask=1492259472, 
mask@entry=0, language=language@entry=0x7fffc660 "C",
territory=territory@entry=0x0, codeset=0x3a3830313336325b , normalized_codeset=0x313a383031333632
,
modifier=0x313430312f323232 , filename=0x37313632302e3031 , do_allocate=1095121465) at
../intl/l10nflist.c:237
#5  0x7383b4f3 in _nl_find_domain
(dirname=0x739c9870 <_nl_default_dirname> "/usr/share/locale",
locale=0x7fffc660 "C", domainname=0x7fffc680 "LC_MESSAGES/libc.mo",
domainbinding=0x656843205d293532) at ./intl/finddomain.c:90
#6  0x7383af48 in __dcigettext
(domainname=, msgid1=0x7fffe0cf "", msgid2=, plural=, n=, category=)
at ./intl/dcigettext.c:837
(gdb) 
=END==

After some googling, I got some hints about apparmor, and sure enough there was
a entry in my /var/log/syslog:
=START==
2023-12-22T10:41:10.026986+01:00 Desktop kernel: [ 9294.380673] audit:
type=1400 audit(1703238070.021:926): apparmor="DENIED"
operation="userns_create" class="namespace" info="User namespace creation
restricted" error=-13 profile="unconfined" pid=263108 comm="digikam"
requested="userns_create" denied="userns_create"
=END==

I tried this work around:
sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0
which solved the problem. Digikam now launches normal.


This article that help me:
https://ubuntuforums.org/showthread.php?t=2488328

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

[digikam] [Bug 468586] Deleting 2 tags only updates 1 tag to file

2023-04-18 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=468586

--- Comment #9 from Kristian Karl  ---
I tested the fix this morning, and it works as expected now.
Thank you very much, I really appreciate your work <3

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

[digikam] [Bug 468586] Deleting 2 tags only updates 1 tag to file

2023-04-17 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=468586

--- Comment #5 from Kristian Karl  ---
Ah, nice, thank you!

I did not mention it, but I'm running my digikam on a Maria/mysql instance. But
I guess it does not matter in this case?

Also, I made a video https://youtu.be/BUHJIVCn-XY  using a clean install of
kubuntu 22.10 and the latest snapshot of digikam appiage. But I think you
understand the problem.

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

[digikam] [Bug 468586] Deleting 2 tags only updates 1 tag to file

2023-04-16 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=468586

--- Comment #3 from Kristian Karl  ---
Ah, interesting! Maybe my repro steps was flawed or incorrect. I'll make a
video of the problem tomorrow. 

One way to expose the problem is to ask Digikam to re-read from the sidecar
files, but it is not necessary to do so.
After deleting the both tags, the sidecar files can be examined externally.
Like using grep. When doing so, one of the tags will still exist in half of the
images sidecar files, where as the other half of the sidecar files will be
correct; tag is removed.

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

[digikam] [Bug 468586] Deleting 2 tags only updates 1 tag to file

2023-04-16 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=468586

--- Comment #1 from Kristian Karl  ---
Also, I tested an verified the same unexpected result on
digiKam-8.0.0-x86-64.appimage 
  Build date: 2023-04-12 15:32 (target: RelWithDebInfo)
  Revision: 66b84e1ba8f8003994fa398a669e1ccc4224a901
  Branch: HEAD

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

[digikam] [Bug 468586] New: Deleting 2 tags only updates 1 tag to file

2023-04-16 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=468586

Bug ID: 468586
   Summary: Deleting 2 tags only updates 1 tag to file
Classification: Applications
   Product: digikam
   Version: unspecified
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Tags-Keywords
  Assignee: digikam-bugs-n...@kde.org
  Reporter: kristian.hermann.k...@gmail.com
  Target Milestone: ---

SUMMARY
When deleting 2 different tags, only 1 of the tags are synced to sidecar
file(s), resulting in out of sync state between database and sidecar files.

Digikam is asked to only read and write metadata to sidecar files.

STEPS TO REPRODUCE
1.  Set up digikam to only read and write metadata to sidecar files.
2. Create 2 different tags and assign them to images. Half of the images gets
the first tag, the other half gets the second tag.
3. Apply the assignment. The sidecar files now have the correct tags
4. Open the Tag (left) side bar, select the 2 tags in step 2 and chose to
delete them.

OBSERVED RESULT
In digikam the 2 tags are deleted, but half of the sidecar files still contains
1 one the tag. 
Selecting all images and then re-reading the metadata from the images (Item ->
Reread Metadata From Selected Files) will find the tags who shoukd have been
deleted and the now appear again in Digikam, which is not expected.

EXPECTED RESULT
All tags should have been removed from the sidecar files.

SOFTWARE/OS VERSIONS
Operating System: Ubuntu 22.10
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.6
Kernel Version: 5.19.0-38-generic (64-bit)
Graphics Platform: X11

ADDITIONAL INFORMATION
Digikam built from sources  master branch commit
37193a9cf14141ff119ac468dae6c74dd061d8b2

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

[digikam] [Bug 459695] Digikam does not include Gopro raw images *.GPR

2022-09-26 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=459695

--- Comment #2 from Kristian Karl  ---
I uploaded to dropbox an example of a raw Gopro image, GOPR0006.GPR, made by a
Gopro Hero 11 camera.
https://www.dropbox.com/s/1fas6ackb5g7uyt/GOPR0006.GPR?dl=0

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

[digikam] [Bug 459695] New: Digikam does not include Gopro raw images *.GPR

2022-09-26 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=459695

Bug ID: 459695
   Summary: Digikam does not include Gopro raw images *.GPR
Classification: Applications
   Product: digikam
   Version: 7.9.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Preview-RAW
  Assignee: digikam-bugs-n...@kde.org
  Reporter: kristian.hermann.k...@gmail.com
  Target Milestone: ---

SUMMARY
When I tried to let digikam 7.9.0  scan for GPR images in an album, it does not
include them.
I could not see any gopro raw images, *.GPR files

I thought that digikam was able to detect and include those since  new version
0.20 of libraw.
But, maybe not the *.GPR files? 

I tested this using digiKam-7.9.0-20220926T033221-x86-64.appimage on this
machine:

Operating System: Ubuntu 22.10
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.6
Kernel Version: 5.19.0-18-generic (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-2600K CPU @ 3.40GHz
Memory: 15,6 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 960/PCIe/SSE2

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

[digikam] [Bug 458200] Size or position change made to face rectangle is only written to database and not to image file/sidecar

2022-08-24 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=458200

--- Comment #4 from Kristian Karl  ---
I verified the fix, and it looks great. 
Thank you :-)

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

[digikam] [Bug 458200] New: Size or position change made to face rectangle is only written to database and not to image file/sidecar

2022-08-23 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=458200

Bug ID: 458200
   Summary: Size or position change made to face rectangle is only
written to database and not to image file/sidecar
   Product: digikam
   Version: 8.0.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Faces-Workflow
  Assignee: digikam-bugs-n...@kde.org
  Reporter: kristian.hermann.k...@gmail.com
  Target Milestone: ---

Created attachment 151519
  --> https://bugs.kde.org/attachment.cgi?id=151519=edit
GIF replicating the issue

SUMMARY
When making a position or size change of a face tag, then leaving the image
without pressing the OK button on the face tag widget, the change will only be
made to the database and not to the image file nor it's sidecar file.

This will cause the user to mistakenly believe that the changes are applied to
the images, when they only are committed to database.

STEPS TO REPRODUCE
1. Open an album with images that contains face tags.
2. Open that image.
2. Change the position of the face tag.
3. Click outside the face tag, this will close the image preview, and take the
user back to the album view.

OBSERVED RESULT
The metadata change (face tag position) has been written to the database, but
not to the image/sidecar file.
If lazy synchronization is enabled, nor message is displayed on the status bar
should.

EXPECTED RESULT
The metadata change (face tag position) should have been written to both the
database and the image/sidecar file.
If lazy synchronization is enabled, the status bar should display "1 file
awaits synchronization".

SOFTWARE/OS VERSIONS

Operating System: Ubuntu 22.04
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 5.15.0-46-generic (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-2600K CPU @ 3.40GHz
Memory: 15,6 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 960/PCIe/SSE2

ADDITIONAL INFORMATION

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

[digikam] [Bug 454656] When locales not set, crash occurs when opening "Settings -> Configure digikam"

2022-05-31 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=454656

--- Comment #7 from Kristian Karl  ---
I verified the fix, and it works fine now.
Thanks!

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

[digikam] [Bug 454656] When locales not set, crash occurs when opening "Settings -> Configure digikam"

2022-05-31 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=454656

--- Comment #3 from Kristian Karl  ---
exiftool version => 12.40

Regarding the question of missing locale settings:
Yes, that is a good question indeed. It's a complete fresh install of Ubuntu
22.04, using English as the main language, and Swedish as the locale for the
keyboard layout and other regional settings.
The problem of missing locales does not really affect my system, I only see it
when running some command line tools, like exiftool, now and then. The
printouts are annoying yes, but it usually don't bother the system/desktop
machine otherwise.

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

[digikam] [Bug 454656] New: When locales not set, crash occurs when opening "Settings -> Configure digikam"

2022-05-31 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=454656

Bug ID: 454656
   Summary: When locales not set, crash occurs when opening
"Settings -> Configure digikam"
   Product: digikam
   Version: 8.0.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Metadata-ExifTool
  Assignee: digikam-bugs-n...@kde.org
  Reporter: kristian.hermann.k...@gmail.com
  Target Milestone: ---

SUMMARY
When using exiftool, and  locales are not set, the output from exiftool messes
up(?) the parsing from the tool, and digikam crashes when opening the "Settings
_ Configure digikam"


STEPS TO REPRODUCE
1. Enable the exiftool
2. If the locales are not properly set. It gives the output like this:
krikar@desktop:~$ exiftool
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "",
LC_ALL = (unset),
LC_ADDRESS = "sv_SE.UTF-8",
LC_NAME = "sv_SE.UTF-8",
LC_MONETARY = "sv_SE.UTF-8",
LC_PAPER = "sv_SE.UTF-8",
LC_IDENTIFICATION = "sv_SE.UTF-8",
LC_TELEPHONE = "sv_SE.UTF-8",
LC_MEASUREMENT = "sv_SE.UTF-8",
LC_TIME = "sv_SE.UTF-8",
LC_NUMERIC = "sv_SE.UTF-8",
LANG = "en_SE.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
Syntax:  exiftool [OPTIONS] FILE

Consult the exiftool documentation for a full list of options.

3. Open  "Settings -> Configure digikam" 

OBSERVED RESULT
Digikam crashes while opening the dialog:
digikam.general: Event is dispatched to KDE desktop notifier
digikam.general: Testing  "mysql_install_db" ...
digikam.general: Found  "mysql_install_db"
digikam.general: Testing  "mysqladmin" ...
digikam.general: Found  "mysqladmin"
digikam.general: Testing  "mysqld" ...
digikam.general: Found  "mysqld"
digikam.avplayer: decoderPriority not changed
digikam.qtav: xcb_egl=0
digikam.general: Testing  "exiftool" ...
digikam.general: "exiftool"  help header line: 
 "perl: warning: Setting locale failed."
digikam.general: Found  "exiftool"  version:  ""
ASSERT: "!isEmpty()" in file /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h,
line 363
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = digikam path = /usr/bin pid = 81860
KCrash: Arguments: /usr/bin/digikam 
QSocketNotifier: Invalid socket 43 and type 'Read', disabling...
QSocketNotifier: Invalid socket 45 and type 'Read', disabling...
QSocketNotifier: Invalid socket 50 and type 'Read', disabling...
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi


EXPECTED RESULT
The digikam Configure dialog is displayed


SOFTWARE/OS VERSIONS
Operating System: Ubuntu 22.04
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 5.15.0-33-generic (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-2600K CPU @ 3.40GHz
Memory: 15,6 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 960/PCIe/SSE2

ADDITIONAL INFORMATION
If setting the locales correct, like following the instructions here for
example:
https://www.thomas-krenn.com/en/wiki/Perl_warning_Setting_locale_failed_in_Debian
the output from the exiftool is then the expected, and digikam won't crash when
opening the Configure dialog

krikar@desktop:~/Downloads$ exiftool
Syntax:  exiftool [OPTIONS] FILE

Consult the exiftool documentation for a full list of options.

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

[digikam] [Bug 453180] "not valid" dates for video in "Adjust Time & Date"

2022-05-02 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=453180

--- Comment #12 from Kristian Karl  ---
Most awesome!
Thanks for the speedy fix :-)

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

[digikam] [Bug 453180] "not valid" dates for video in "Adjust Time & Date"

2022-04-29 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=453180

--- Comment #7 from Kristian Karl  ---
Ah, thanks! Good to know for the next time :+1:

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

[digikam] [Bug 453180] "not valid" dates for video in "Adjust Time & Date"

2022-04-29 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=453180

--- Comment #5 from Kristian Karl  ---
Created attachment 148456
  --> https://bugs.kde.org/attachment.cgi?id=148456=edit
Screenshot of "Adjust Time & Date"

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

[digikam] [Bug 453180] "not valid" dates for video in "Adjust Time & Date"

2022-04-29 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=453180

--- Comment #4 from Kristian Karl  ---
Video available here:
https://www.dropbox.com/s/l8lxx65ovjkdya9/2022-04-27_181056.mp4?dl=0

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

[digikam] [Bug 453180] "not valid" dates for video in "Adjust Time & Date"

2022-04-29 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=453180

--- Comment #3 from Kristian Karl  ---
This output was not possible to add here, so I created a public gist unstead: 
https://gist.github.com/KristianKarl/cbf1e62c3fdfbd7bfa7bb97bbd57ccd4

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

[digikam] [Bug 453180] "not valid" dates for video in "Adjust Time & Date"

2022-04-29 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=453180

--- Comment #2 from Kristian Karl  ---
Select the attached video in thumbnal view, and then open the dialog "Adjust
Time & Date"
Digikam: digiKam compiled from sources
==
>digikam.general: Action Thread run  1  new jobs
>digikam.metaengine: ExifTool path: "exiftool"
>digikam.metaengine: Path to ExifTool: "exiftool"
>digikam.metaengine: Check ExifTool availability: true
>digikam.metaengine: Path to ExifTool: "exiftool"
>digikam.metaengine: ExifToolProcess::start(): create new ExifTool instance: 
>"exiftool" ("-stay_open", "true", "-@", "-", "-common_args", "-charset", 
>"filename=UTF8", "-charset", "iptc=UTF8")
>digikam.metaengine: ExifTool process started
>digikam.metaengine: ExifTool "Load Chunks" "-TagsFromFile 
>/home/krikar/Pictures/tmp/2022-04-27_181056.mp4 -all:alldigikam.metaengine: ExifToolProcess::readOutput(): ExifTool command completed
>digikam.metaengine: ExifTool complete command for action "Load Chunks" with 
>elasped time (ms): 386
>digikam.metaengine: EXV 9
>digikam.metaengine: ExifTool parsed command for action "Load Chunks"
>digikam.metaengine: 1 properties decoded
>digikam.metaengine: ExifTool complete "Load Chunks" for 
>"/home/krikar/Pictures/tmp/2022-04-27_181056.mp4"
>digikam.metaengine: Metadata chunk loaded with ExifTool
>digikam.metaengine: EXV chunk size loaded with ExifTool: 9
>digikam.metaengine: ExifToolProcess::terminate(): send ExifTool shutdown 
>command...
>digikam.metaengine: ExifTool process finished 1 QProcess::NormalExit
>digikam.metaengine: Loading metadata with "ExifTool" backend from 
>"/home/krikar/Pictures/tmp/2022-04-27_181056.mp4"
>digikam.general: One job is done

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

[digikam] [Bug 453180] "not valid" dates for video in "Adjust Time & Date"

2022-04-29 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=453180

--- Comment #1 from Kristian Karl  ---
For some reason, I get "Your comment has been automatically blocked as it is
believed to contain spam. Please contact Sysadmin if you believe this to be
incorrect." when I try to add the log output from digikam here into the comment

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

[digikam] [Bug 453180] New: "not valid" dates for video in "Adjust Time & Date"

2022-04-29 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=453180

Bug ID: 453180
   Summary: "not valid" dates for video in "Adjust Time & Date"
   Product: digikam
   Version: 8.0.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Metadata-Date
  Assignee: digikam-bugs-n...@kde.org
  Reporter: kristian.hermann.k...@gmail.com
  Target Milestone: ---

SUMMARY
When using a compiled version of digikam from latest sources, opening the
"Adjust Time & Date" dialog for attached video, I get "not valid" for
"Timestamp used".

STEPS TO REPRODUCE
1. Use the attached video 2022-04-27_181056.mp4
2. Open the "Adjust Time & Date" dialog
3. EXIF/IPTC/XMP should be selected
3. Check the "Timestamp used" for the video

OBSERVED RESULT
The  fields in column "Timestamp used" and Timestamp Updated" are "not valid"

EXPECTED RESULT
The  fields in column "Timestamp used" and Timestamp Updated" should both be
"2022-04-27 18:09:38"

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.24
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.3
Kernel Version: 5.13.0-40-generic (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-2600K CPU @ 3.40GHz
Memory: 15,6 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 960/PCIe/SSE2

ADDITIONAL INFORMATION
When using the Weekly Snapshots appimage
digiKam-7.7.0-20220427T043335-x86-64.appimage the expected result is correct.
It seems like the appimage version of digikam is using ffmpeg(?) to determine
dates, and my compiled digikam is using exiftool?


About exiftool
=
exiftool version is 12.40

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

[digikam] [Bug 251424] Include gpx overlays found in albums

2022-03-25 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=251424

Kristian Karl  changed:

   What|Removed |Added

 CC||kristian.hermann.karl@gmail
   ||.com

--- Comment #11 from Kristian Karl  ---
This feature is awesome!
Thanks for implementing it, it's great :-)

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

[digikam] [Bug 451802] GPX files fails to load

2022-03-24 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=451802

--- Comment #9 from Kristian Karl  ---
I verified the fix this morning. Looks all good now.
Thanks Maik :-)

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

[digikam] [Bug 451802] GPX files fails to load

2022-03-23 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=451802

--- Comment #5 from Kristian Karl  ---
Inserting this code after
https://invent.kde.org/graphics/digikam/-/blob/master/core/utilities/geolocation/geoiface/tracks/trackreader.cpp#L332
 seems to be one solution to the problem.


if (xml.name() == QLatin1String("extensions"))
{
  do {
xml.readNext();
  }
  while (!(xml.tokenType() == QXmlStreamReader::EndElement && xml.name() ==
QLatin1String("extensions")) && !xml.hasError()) ;
  continue;
}


Also, I don't think this code is used anymore?
https://invent.kde.org/graphics/digikam/-/blob/master/core/utilities/geolocation/geoiface/tracks/trackreader.cpp#L147-290

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

[digikam] [Bug 451802] New: GPX files fails to load

2022-03-22 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=451802

Bug ID: 451802
   Summary: GPX files fails to load
   Product: digikam
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Geolocation-Correlator
  Assignee: digikam-bugs-n...@kde.org
  Reporter: kristian.hermann.k...@gmail.com
  Target Milestone: ---

Created attachment 147670
  --> https://bugs.kde.org/attachment.cgi?id=147670=edit
test.gpx

SUMMARY
After the commit
https://invent.kde.org/graphics/digikam/-/commit/94e656db9f78d5abf9577a45f3a2a54f4a5a47b4
gpx files from strava (and elsewhere) fails to load.

STEPS TO REPRODUCE
1. Select an image, and choosed to "Edit the geolocation"
2. In "Geolocation Editor", select tab "GPS Correlator", and click button "Load
GPX files..."
3. Use the attached test file test.gps

OBSERVED RESULT
Digikam displays an error: "The following GPX file could not be loaded:"

EXPECTED RESULT
The track of the test.gpx file displayed on the map.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.24
KDE Plasma Version: 5.24.3
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 5.13.0-37-generic (64-bit)
Graphics Platform: X11

ADDITIONAL INFORMATION
When reverting commit 94e656db
(https://invent.kde.org/graphics/digikam/-/commit/94e656db9f78d5abf9577a45f3a2a54f4a5a47b4)
the file test.gpx loads without problems.

Compiled from latest source commit: 9ff9a4b8

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

[digikam] [Bug 450518] New: Crash when opening Advanced Search

2022-02-18 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=450518

Bug ID: 450518
   Summary: Crash when opening Advanced Search
   Product: digikam
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Searches-Advanced
  Assignee: digikam-bugs-n...@kde.org
  Reporter: kristian.hermann.k...@gmail.com
  Target Milestone: ---

SUMMARY
When opening the Advanced Search dialog, Digikam crashes for me

STEPS TO REPRODUCE
1. Start Digikam
2. Open the Advanced Search dialog

OBSERVED RESULT
Digikam crashes. 

Thread 1 "digikam" received signal SIGSEGV, Segmentation fault.
0x74d766d2 in QObject::setObjectName(QString const&) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
(gdb) bt
#0  0x74d766d2 in QObject::setObjectName(QString const&) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x77a9c7c4 in
Digikam::SearchFieldChoice::setupValueWidgets(QGridLayout*, int, int)
(this=0x5708d330, layout=0x56cd3370, row=3, column=3)
at
/home/krikar/dev/kde/digikam/core/utilities/searchwindow/searchfields.cpp:2184
#2  0x77a97c54 in Digikam::SearchField::setup(QGridLayout*, int)
(this=0x5708d330, layout=0x56cd3370, line=3)
at
/home/krikar/dev/kde/digikam/core/utilities/searchwindow/searchfields.cpp:1066
#3  0x77a84be4 in
Digikam::SearchFieldGroup::addField(Digikam::SearchField*)
(this=0x56298fd0, field=0x5708d330)
at
/home/krikar/dev/kde/digikam/core/utilities/searchwindow/searchfieldgroup.cpp:64
#4  0x77a7e927 in
Digikam::SearchGroup::setup(Digikam::SearchGroup::Type) (this=0x563e9700,
type=Digikam::SearchGroup::FirstGroup)
at
/home/krikar/dev/kde/digikam/core/utilities/searchwindow/searchgroup.cpp:104
#5  0x77a77335 in Digikam::SearchView::createSearchGroup()
(this=0x5783c010) at
/home/krikar/dev/kde/digikam/core/utilities/searchwindow/searchview.cpp:280
#6  0x77a7657d in
Digikam::AbstractSearchGroupContainer::addSearchGroup() (this=0x5783c010)
at
/home/krikar/dev/kde/digikam/core/utilities/searchwindow/searchview.cpp:63
#7  0x77a76dd6 in Digikam::SearchView::setup() (this=0x5783c010) at
/home/krikar/dev/kde/digikam/core/utilities/searchwindow/searchview.cpp:205
#8  0x77a75378 in Digikam::SearchWindow::SearchWindow()
(this=0x569b0200) at
/home/krikar/dev/kde/digikam/core/utilities/searchwindow/searchwindow.cpp:82
#9  0x77aae6f1 in Digikam::SearchTabHeader::searchWindow() const
(this=0x577d20a0)
at
/home/krikar/dev/kde/digikam/core/utilities/searchwindow/searchtabheader.cpp:426
#10 0x77aaee16 in Digikam::SearchTabHeader::newAdvancedSearch()
(this=0x577d20a0) at
/home/krikar/dev/kde/digikam/core/utilities/searchwindow/searchtabheader.cpp:515
#11 0x77a723fa in
Digikam::SearchTabHeader::qt_static_metacall(QObject*, QMetaObject::Call, int,
void**)
(_o=0x577d20a0, _c=QMetaObject::InvokeMetaMethod, _id=4,
_a=0x7fffcb60)
at
/home/krikar/dev/kde/digikam/build/core/utilities/searchwindow/gui_searchwindow_obj_autogen/EWIEGA46WW/moc_searchtabheader.cpp:128
#12 0x74d7d1f0 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x75919fb6 in QAbstractButton::clicked(bool) () at
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x7591a1de in  () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x7591b6b3 in  () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x7591b875 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) ()
at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#17 0x75864cf6 in QWidget::event(QEvent*) () at
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#18 0x759c0283 in QPushButton::event(QEvent*) () at
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x75821dc3 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#20 0x7582ae77 in QApplication::notify(QObject*, QEvent*) () at
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#21 0x74d4619a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x7582a0a7 in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) ()
at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#23 0x7587fed4 in  () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#24 0x758831f4 in  () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#25 0x75821dc3 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#26 0x7582abb8 in QApplication::notify(QObject*, QEvent*) () at
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#27 0x74d4619a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt5Core.so.5
#28 0x7512a4d8 in

[digikam] [Bug 381319] Keyboard modifier not caught when using Wacom Tablet [patch]

2022-01-10 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=381319

Kristian Karl  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |NOT A BUG

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

[digikam] [Bug 381319] Keyboard modifier not caught when using Wacom Tablet [patch]

2022-01-10 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=381319

--- Comment #8 from Kristian Karl  ---
Hi Gilles and happy new year!

I think we can close this report. I believe the modification for a tablet to
work with DK is maybe unnecessary. 
I stopped using the tablet this way. Keyboard and mouse is much faster

Best Kristian

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

[digikam] [Bug 421023] Face tagging quirky in digiKam 7.0.0-beta3

2020-05-13 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=421023

--- Comment #12 from Kristian Karl  ---
For me, it works as expected again.
Thanks for the fix :-)

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

[digikam] [Bug 421023] Face tagging quirky in digiKam 7.0.0-beta3

2020-05-12 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=421023

Kristian Karl  changed:

   What|Removed |Added

 CC||kristian.hermann.karl@gmail
   ||.com

--- Comment #9 from Kristian Karl  ---
I have too experienced the sluggish behavior described here.
When I tested with
https://invent.kde.org/kde/digikam/commit/1e88b3a88c20492705de121c13d06fce4b312262
in place, the performance is back to normal.

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

[digikam] [Bug 416231] exif date not written to sidecar file when modified, nor is it updated in the metadata sidebar

2020-01-14 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=416231

Kristian Karl  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |NOT A BUG

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

[digikam] [Bug 416231] exif date not written to sidecar file when modified, nor is it updated in the metadata sidebar

2020-01-14 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=416231

--- Comment #7 from Kristian Karl  ---
Okay, got it!

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

[digikam] [Bug 416231] exif date not written to sidecar file when modified, nor is it updated in the metadata sidebar

2020-01-14 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=416231

--- Comment #5 from Kristian Karl  ---
Sorry, not left sidebar. I meant the right metadata sidebar in the comment
above.

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

[digikam] [Bug 416231] exif date not written to sidecar file when modified, nor is it updated in the metadata sidebar

2020-01-14 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=416231

--- Comment #4 from Kristian Karl  ---
Should not the update to the database (by the Time Adjust Tool) be reflected in
the [left] Metadata sidebar?

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

[digikam] [Bug 416231] exif date not written to sidecar file when modified, nor is it updated in the metadata sidebar

2020-01-14 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=416231

--- Comment #2 from Kristian Karl  ---
Ah, true. I missed that. Thanks for clarifying.

But how come is actually changes when I do a "Item -> Write Metadata to File"?
Maybe

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

[digikam] [Bug 416231] New: exif date not written to sidecar file when modified, nor is it updated in the metadata sidebar

2020-01-14 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=416231

Bug ID: 416231
   Summary: exif date not written to sidecar file when modified,
nor is it updated in the metadata sidebar
   Product: digikam
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Metadata-Date
  Assignee: digikam-bugs-n...@kde.org
  Reporter: kristian.hermann.k...@gmail.com
  Target Milestone: ---

SUMMARY
When modifying the exif original date, digikam does not write the change to the
sidecar file. Nor is the change displayed in the metadata exif sidebar.

STEPS TO REPRODUCE
1. In settings, make sure metadata is read and written to sidecar file. (Write
to sidecar only)
2. For an image, with an existing sidecar file, modify the original exif date:
Item -> Adjust Time & Date
3. Modify only the exif: original date (click Apply and close the dialog)


OBSERVED RESULT
1. The Metadata [exif] sidebar still displays the old value for Date and Time
(original) 
2. The sidecar file still holds the old value for exif:DateTimeOriginal

EXPECTED RESULT
1. The Metadata [exif] sidebar displays changed value for Date and Time
(original) 
2. The value for exif:DateTimeOriginal in the sidecar file is changed to the
modified value

OTHER INFORMATION
Only when performing a Item -> Write Metadata to File, the expected results are
achieved. 

SOFTWARE/OS VERSIONS
Tested on Digikam built from sources: rev
56b92b644e3196373ecc656e3e9bb614ed193139
and on App image digikam-7.0.0-beta2-20200112T071518-x86-64.appimage

Operating System: KDE neon 5.17
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.66.0
Qt Version: 5.13.2
Kernel Version: 4.15.0-74-generic
OS Type: 64-bit
Processors: 4 × Intel® Core™ i7-7500U CPU @ 2.70GHz
Memory: 15.4 GiB of RAM

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

[digikam] [Bug 415679] Faces are not recognized

2019-12-29 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=415679

Kristian Karl  changed:

   What|Removed |Added

 Resolution|--- |NOT A BUG
 Status|REPORTED|RESOLVED

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

[digikam] [Bug 415679] Faces are not recognized

2019-12-29 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=415679

--- Comment #3 from Kristian Karl  ---
I experimented a bit, and I think I know what's going on.

When I let Digikam detect faces, I set 'Face Accuracy' to 100%, which gives
very good results.

Then I carry on with Face Recognition, with no recognized faces. But. If I
change the 'Face Accuracy' to way less, say 50%, Digikam is starting to
recognize.

So in short, 100% 'Face Accuracy', no faces will be recognized.

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

[digikam] [Bug 415679] Faces are not recognized

2019-12-29 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=415679

--- Comment #2 from Kristian Karl  ---
My subset of images were placed in a new folder, and I started a new Digikam
database in that folder. So everything was completely new for Digikam. No old
databases.

I started digikam like this:
digikam --database-directory 

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

[digikam] [Bug 415679] New: Faces are not recognized

2019-12-29 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=415679

Bug ID: 415679
   Summary: Faces are not recognized
   Product: digikam
   Version: 7.0.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Faces-Recognition
  Assignee: digikam-bugs-n...@kde.org
  Reporter: kristian.hermann.k...@gmail.com
  Target Milestone: ---

SUMMARY
Using a subset of images with faces, Digikam fails to recognize any faces.

STEPS TO REPRODUCE
1. Digikam detect faces successfully.
2. Assign name tags to some of the Unknown face tags (at least 4 to each
person) 
3. Let Digikam try to Recognize faces

OBSERVED RESULT
No faces were recognized.

EXPECTED RESULT
Faces should have been recognized.


SOFTWARE/OS VERSIONS
KDE 5.65.0 / Plasma 5.17.4
Qt Version: 5.13.2

ADDITIONAL INFORMATION
I used the Appimage: digikam-7.0.0-beta1-20191221T113643-x86-64.appimage
I also tried the windows version: digiKam-7.0.0-beta1-20191227T151506-Win64.exe

LOG OUTPUT
igikam::RecognitionPreprocessor::Private::preprocess: Align face for OpenFace
neural network model
Digikam::OpenfacePreprocessor::process: type:  16
Digikam::OpenfacePreprocessor::process: Full object detection and landmard
computation finished
Digikam::OpenfacePreprocessor::process: Align face finished
Digikam::DNNFaceExtractor::getFaceEmbedding: Finish aligning face in  14  ms
Digikam::DNNFaceExtractor::getFaceEmbedding: Start neural network
Digikam::DNNFaceExtractor::getFaceEmbedding: Finish computing face embedding in
 224  ms
Digikam::DNNFaceExtractor::getFaceEmbedding: Face descriptors size: ( 1 ,  128
)
Digikam::DNNFaceRecognizer::predict: m_threshold  1
Digikam::DNNFaceRecognizer::predict: vecdata:  0.0493621   0.0429577
Digikam::OpenCVDNNFaceRecognizer::recognize: 2 0.59324
Digikam::DNNFaceRecognizer::predict: Predicting face image
Digikam::DNNFaceExtractor::getFaceEmbedding: faceImage channels:  3
Digikam::DNNFaceExtractor::getFaceEmbedding: faceImage size: ( 254 ,  180 )

Digikam::FacePipeline::Private::checkFinished: Check for finish:  4 packages, 0
infos to filter, hasFinished() false
Digikam::RecognitionPreprocessor::Private::preprocess: Align face for OpenFace
neural network model
Digikam::OpenfacePreprocessor::process: type:  16
Digikam::OpenfacePreprocessor::process: Full object detection and landmard
computation finished
Digikam::OpenfacePreprocessor::process: Align face finished
Digikam::DNNFaceExtractor::getFaceEmbedding: Finish aligning face in  10  ms
Digikam::DNNFaceExtractor::getFaceEmbedding: Start neural network
Digikam::DNNFaceExtractor::getFaceEmbedding: Finish computing face embedding in
 269  ms
Digikam::DNNFaceExtractor::getFaceEmbedding: Face descriptors size: ( 1 ,  128
)
Digikam::DNNFaceRecognizer::predict: m_threshold  1
Digikam::DNNFaceRecognizer::predict: vecdata:  0.0508566   0.0368828
Digikam::OpenCVDNNFaceRecognizer::recognize: 2 0.46771
Digikam::FacePipeline::Private::checkFinished: Check for finish:  3 packages, 0
infos to filter, hasFinished() false
Digikam::DNNFaceRecognizer::predict: Predicting face image
Digikam::DNNFaceExtractor::getFaceEmbedding: faceImage channels:  3
Digikam::DNNFaceExtractor::getFaceEmbedding: faceImage size: ( 254 ,  246 )

Digikam::RecognitionPreprocessor::Private::preprocess: Align face for OpenFace
neural network model
Digikam::OpenfacePreprocessor::process: type:  16
Digikam::OpenfacePreprocessor::process: Full object detection and landmard
computation finished
Digikam::OpenfacePreprocessor::process: Align face finished
Digikam::DNNFaceExtractor::getFaceEmbedding: Finish aligning face in  13  ms
Digikam::DNNFaceExtractor::getFaceEmbedding: Start neural network
Digikam::DNNFaceExtractor::getFaceEmbedding: Finish computing face embedding in
 181  ms
Digikam::DNNFaceExtractor::getFaceEmbedding: Face descriptors size: ( 1 ,  128
)
Digikam::DNNFaceRecognizer::predict: m_threshold  1
Digikam::DNNFaceRecognizer::predict: vecdata:  0.0627084   -0.0602348
Digikam::OpenCVDNNFaceRecognizer::recognize: 2 0.514198
Digikam::FacePipeline::Private::checkFinished: Check for finish:  2 packages, 0
infos to filter, hasFinished() false
Digikam::DNNFaceRecognizer::predict: Predicting face image
Digikam::DNNFaceExtractor::getFaceEmbedding: faceImage channels:  3
Digikam::DNNFaceExtractor::getFaceEmbedding: faceImage size: ( 254 ,  164 )

Digikam::RecognitionPreprocessor::Private::preprocess: Align face for OpenFace
neural network model
Digikam::OpenfacePreprocessor::process: type:  16
Digikam::OpenfacePreprocessor::process: Full object detection and landmard
computation finished
Digikam::OpenfacePreprocessor::process: Align face finished
Digikam::DNNFaceExtractor::getFaceEmbedding: Finish aligning face in  14  ms
Digikam::DNNFaceExtractor::getFaceEmbedding: Start neural network
Digikam::DNNFaceExtractor::getFaceEmbedding: Finish computing face embedding in
 202  ms

[digikam] [Bug 280618] Digikam crashes when tagging multiple faces

2019-12-29 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=280618

--- Comment #7 from Kristian Karl  ---
Not a problem anymore :-)

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

[digikam] [Bug 387870] undefined reference to typeinfo for cv::face::FaceRecognizer

2019-12-29 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=387870

--- Comment #4 from Kristian Karl  ---
Not a problem anymore :-)

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

[digikam] [Bug 332126] LibRaw_r_LIBRARIES CMake Error: The following variables are used in this project, but they are set to NOTFOUND

2019-12-29 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=332126

--- Comment #3 from Kristian Karl  ---
Not a problem anymore :-)

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

[digikam] [Bug 392518] Face recognition using the deep learning algo, dont move faces to Unconfirmed

2019-12-29 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=392518

--- Comment #10 from Kristian Karl  ---
Problem fixed!
Thanks for the great work.
Merry Christmas and Happy new year :-)

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

[digikam] [Bug 373839] Continuously face thumbnails flicker/update

2019-03-21 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=373839

--- Comment #30 from Kristian Karl  ---
I can confirm, that the issue still exists.

I tried using digikam-6.1.0-git-20190321T102236-x86-64.appimage

If there's anything I can do, to try to pin-point the problem, I'm happy to
help out.

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

[digikam] [Bug 401423] Video sidecar files nor read or written

2018-11-27 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=401423

--- Comment #5 from Kristian Karl  ---
Tested it, and it looks great.
Thanks!

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

[digikam] [Bug 401423] Video sidecar files nor read or written

2018-11-26 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=401423

--- Comment #3 from Kristian Karl  ---
Oh, sorry for not providing the version information.

I built it from latest master 244785fc86dd446afcb4c2ecc05516ce00f839a7,
using: 
cmake -DCMAKE_BUILD_TYPE=RelWithDebInfo -DBUILD_TESTING=OFF
-DENABLE_MYSQLSUPPORT=ON -DENABLE_INTERNALMYSQL=ON -DENABLE_MEDIAPLAYER=ON
-DENABLE_DBUS=ON -DENABLE_APPSTYLES=ON .. && make -j$(nproc --all) && sudo make
-j$(nproc --all) install

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

[digikam] [Bug 401423] New: Video sidecar files nor read or written

2018-11-26 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=401423

Bug ID: 401423
   Summary: Video sidecar files nor read or written
   Product: digikam
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Metadata-Sidecar
  Assignee: digikam-bugs-n...@kde.org
  Reporter: kristian.hermann.k...@gmail.com
  Target Milestone: ---

Created attachment 116506
  --> https://bugs.kde.org/attachment.cgi?id=116506=edit
A proposed patch that fixes the issue.

SUMMARY
When a settings are set to: 
 "Read from sidecar files" => true
 "Write to sidecar only" => true
Digikam does not read, or write sidecar files for video items.

STEPS TO REPRODUCE
1. Set settings according to above
2. Try to read from or write 
 "Item -> Write Metadata to File"
 "Item -> Reread Metadata From File


OBSERVED RESULT
Metadata in sidecar files are not read, nor is sidecar files written for video
files.

EXPECTED RESULT
Metadata should be read and written to sidecar files for video.


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 398714] MicrosoftPhoto:LastKeywordXMP does not show up in digkam tags list

2018-09-16 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=398714

Kristian Karl  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from Kristian Karl  ---
Okay, that explains it for me.
Thanks for taking the time to answer it. :-)

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

[digikam] [Bug 398714] MicrosoftPhoto:LastKeywordXMP does not show up in digkam tags list

2018-09-16 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=398714

Kristian Karl  changed:

   What|Removed |Added

 Attachment #115007|0   |1
is obsolete||

--- Comment #1 from Kristian Karl  ---
Created attachment 115010
  --> https://bugs.kde.org/attachment.cgi?id=115010=edit
example.jpg.xmp

Attached incorrect sidecar file.
Correct file now attached

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

[digikam] [Bug 398714] New: MicrosoftPhoto:LastKeywordXMP does not show up in digkam tags list

2018-09-16 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=398714

Bug ID: 398714
   Summary: MicrosoftPhoto:LastKeywordXMP does not show up in
digkam tags list
   Product: digikam
   Version: 6.0.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Tags-Keywords
  Assignee: digikam-bugs-n...@kde.org
  Reporter: kristian.hermann.k...@gmail.com
  Target Milestone: ---

Created attachment 115007
  --> https://bugs.kde.org/attachment.cgi?id=115007=edit
example.jpg.xmp

When digikam reads attached sidecar file, the MicrosoftPhoto:LastKeywordXMP
tag:
THIS STRING DOES NOT SHOW UP IN DIGIKAM BUT AS AN ITPC KEYWORD

does not show up in Digikam when read. As a side effect, the meta data is not
searchable by Digikam.

I expected that the tag above actually should show up in Digikam tag list. 

The sidecar file was created by an earlier version of Digikam.

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

[digikam] [Bug 397340] Update image file timestamps if metadata is written to sidecar file [patch]

2018-09-13 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=397340

--- Comment #17 from Kristian Karl  ---
But then all is fine!

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

[digikam] [Bug 397340] Update image file timestamps if metadata is written to sidecar file [patch]

2018-09-13 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=397340

--- Comment #15 from Kristian Karl  ---
Created attachment 114931
  --> https://bugs.kde.org/attachment.cgi?id=114931=edit
Old metadata remains after file is re-scanned

Hi Maik,

I think your solution looks really good.
I tested it, and the re-scanning part works well. 

However, it seems that the old metadata is not discarded from the digikam
database. This means that changes made in a sidecar file, will show up, which
is good.
But the old data, that was replaced, or removed from the sidecar file, is still
displayed by digikam.

This is how I tested it.

1) Start digikam in an empty folder: digikam --database-directory 

2) When digikam asks for a collection, point to a fresh folder of images. No
sidecar files exists.

3) Make sure settings are:
 - "Update file timestamp when files are modified"
 - "Rescan file when files are modified"
 - "Read from sidecar files"
 - "Write to sidecar files 
   - "Write to XMP sidecar only"

4) Assign a face tag XXX to some image

5) Close digikam

6) Open the sidecar file in a text editor, replace the all XXX to YYY, save and
close.

7) Restart digikam

Expected results

Image will now display only YYY

Actual results

Image displays both XXX and YYY

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

[digikam] [Bug 373839] Continuously face thumbnails flicker/update

2018-09-11 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=373839

--- Comment #28 from Kristian Karl  ---
Complete printout of information regarding the VM machine

$ VBoxManage showvminfo "Kubuntu 18.04"
Name:Kubuntu 18.04
Groups:  /
Guest OS:Ubuntu (64-bit)
UUID:73aa30f4-e0f1-4359-96ba-b1e860f8038f
Config file: /home/krikar/VirtualBox VMs/Kubuntu 18.04/Kubuntu 18.04.vbox
Snapshot folder: /home/krikar/VirtualBox VMs/Kubuntu 18.04/Snapshots
Log folder:  /home/krikar/VirtualBox VMs/Kubuntu 18.04/Logs
Hardware UUID:   73aa30f4-e0f1-4359-96ba-b1e860f8038f
Memory size: 4610MB
Page Fusion: off
VRAM size:   33MB
CPU exec cap:100%
HPET:off
Chipset: piix3
Firmware:BIOS
Number of CPUs:  1
PAE: off
Long Mode:   on
Triple Fault Reset: off
APIC:on
X2APIC:  on
CPUID Portability Level: 0
CPUID overrides: None
Boot menu mode:  message and menu
Boot Device (1): Floppy
Boot Device (2): DVD
Boot Device (3): HardDisk
Boot Device (4): Not Assigned
ACPI:on
IOAPIC:  on
BIOS APIC mode:  APIC
Time offset: 0ms
RTC: UTC
Hardw. virt.ext: on
Nested Paging:   on
Large Pages: off
VT-x VPID:   on
VT-x unr. exec.: on
Paravirt. Provider: Default
Effective Paravirt. Provider: KVM
State:   powered off (since 2018-09-11T16:41:47.67600)
Monitor count:   1
3D Acceleration: on
2D Video Acceleration: off
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address: 
Teleporter Password: 
Tracing Enabled: off
Allow Tracing to Access VM: off
Tracing Configuration: 
Autostart Enabled: off
Autostart Delay: 0
Default Frontend: 
Storage Controller Name (0):IDE
Storage Controller Type (0):PIIX4
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0):  2
Storage Controller Port Count (0):  2
Storage Controller Bootable (0):on
Storage Controller Name (1):SATA
Storage Controller Type (1):IntelAhci
Storage Controller Instance Number (1): 0
Storage Controller Max Port Count (1):  30
Storage Controller Port Count (1):  1
Storage Controller Bootable (1):on
IDE (1, 0): Empty
SATA (0, 0): /home/krikar/VirtualBox VMs/Kubuntu
18.04/Snapshots/{d346dd72-695a-4b30-a07f-9e743849bb7a}.vdi (UUID:
d346dd72-695a-4b30-a07f-9e743849bb7a)
NIC 1:   MAC: 0800272205A2, Attachment: NAT, Cable connected: on,
Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority:
0, Promisc Policy: deny, Bandwidth group: none
NIC 1 Settings:  MTU: 0, Socket (send: 64, receive: 64), TCP Window (send:64,
receive: 64)
NIC 2:   disabled
NIC 3:   disabled
NIC 4:   disabled
NIC 5:   disabled
NIC 6:   disabled
NIC 7:   disabled
NIC 8:   disabled
Pointing Device: USB Tablet
Keyboard Device: PS/2 Keyboard
UART 1:  disabled
UART 2:  disabled
UART 3:  disabled
UART 4:  disabled
LPT 1:   disabled
LPT 2:   disabled
Audio:   enabled (Driver: PulseAudio, Controller: AC97, Codec: AD1980)
Audio playback:  disabled
Audio capture: enabled
Clipboard Mode:  disabled
Drag and drop Mode: disabled
VRDE:disabled
USB: enabled
EHCI:enabled
XHCI:disabled

USB Device Filters:



Bandwidth groups:  

Shared folders:  

Capturing:  not active
Capture audio:  not active
Capture screens:0
Capture file:   /home/krikar/VirtualBox VMs/Kubuntu 18.04/Kubuntu
18.04.webm
Capture dimensions: 1024x768
Capture rate:   512 kbps
Capture FPS:25
Capture options:ac_enabled=false

Guest:

Configured memory balloon size:  0 MB

Snapshots:

   Name: Prestine (UUID: 43f8bf90-35c4-440e-b854-23041d709ac4) *

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

[digikam] [Bug 373839] Continuously face thumbnails flicker/update

2018-09-11 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=373839

--- Comment #27 from Kristian Karl  ---
System
===
Processors: 1 CPU
Base memory: 4610 MB
Acceleration: VT-x/AMD-V, Nested Paging, KVM Paravirtualization

Display
===
Video memory: 33 MB
Acceleration: 3D

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

[digikam] [Bug 373839] Continuously face thumbnails flicker/update

2018-09-11 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=373839

--- Comment #25 from Kristian Karl  ---
With 3D Acceleration enabled, I still get flickering on my VirtualBox
installation, I'm afraid.

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

[digikam] [Bug 373839] Continuously face thumbnails flicker/update

2018-09-11 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=373839

--- Comment #23 from Kristian Karl  ---
No. 3D Acceleration was disabled.

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

[digikam] [Bug 373839] Continuously face thumbnails flicker/update

2018-09-11 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=373839

--- Comment #21 from Kristian Karl  ---
I tested the latest appimage of Digikam (digikam-5.9.0-01-x86-64.appimage) on
the latest KUbuntu (18-04.1) version on Virtualbox. 

1) I used images from http://cswww.essex.ac.uk/mv/allfaces/faces94.html
   http://cswww.essex.ac.uk/mv/allfaces/faces94.zip

2) I then let Digikam scan for faces on all the images

3) I open People view, and select the tag unknown

4) Select a Flat List in the View | Separate Items

4) I maximize my VirtualBox window in my 3840x2160 screen, and then maximize
Digikam in VirtualBox.

5) I click on the People view tab (hide it), so I can maximize the number of
thumbnails in the window.

6) Adjust thumbnail sizes to smallest possible.

I get flicker.

Using the steps above should be enough to reproduce the flicker on any 4k
screen.

If an 4K screen is not available, the VirtualBox window could be made very
large by just increasing the size of that window, and moving it outside, until
a very large window is made, the maximize the Digikam window.

I think the problem perhaps is related to the actual size of the Digikam
window, and the number of people thumbnails being displayed?

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

[digikam] [Bug 373839] Continuously face thumbnails flicker/update

2018-09-11 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=373839

--- Comment #19 from Kristian Karl  ---
Maybe a long shot, but could maybe this method be involved somehow?

https://github.com/KDE/digikam/blob/c013f88088bf08e321e4da8be71a61b02b67af2c/core/libs/widgets/itemview/dcategorizedview.cpp#L70-L132

I'll add some debug logging and see what I can find

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

[digikam] [Bug 373839] Continuously face thumbnails flicker/update

2018-09-11 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=373839

--- Comment #18 from Kristian Karl  ---
I think that maybe the resolution might be involved somehow.
If I use may 2560x1440, I don't get any flickering.
When I use 3840x2160, I do get flickering.

Please note, that the digikam window is maximized in both cases.

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

[digikam] [Bug 373839] Continuously face thumbnails flicker/update

2018-09-11 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=373839

--- Comment #17 from Kristian Karl  ---
I use x11

echo $XDG_SESSION_TYPE
x11

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

[digikam] [Bug 373839] Continuously face thumbnails flicker/update

2018-09-11 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=373839

--- Comment #15 from Kristian Karl  ---
Oh sorry!

Desktop: KDE Neon (Plasma 5.13.4,KDE frameworks 5.49.0, Qt 5.11.1 ) on Ubuntu
18.04

Display manager and extension: 
cat /etc/X11/default-display-manager 
/usr/bin/sddm

Graphics card and driver?
glxinfo | grep OpenGL
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2) 
OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.0.5
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 18.0.5
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 18.0.5
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:

Resolution on the screen: 3840x2160

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

[digikam] [Bug 373839] Continuously face thumbnails flicker/update

2018-09-07 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=373839

--- Comment #13 from Kristian Karl  ---
Some more details observed while debugging.
It seems like ThumbnailLoadingTask is getting called repeatably during flicker:

libdigikamcore.so.6.0.0!Digikam::ThumbnailCreator::loadDetail(const
Digikam::ThumbnailCreator * const this, const Digikam::ThumbnailIdentifier &
identifier, const QRect & rect)
(/home/krikar/dev/kde/digikam/core/libs/threadimageio/thumbnailcreator.cpp:187)
libdigikamcore.so.6.0.0!Digikam::ThumbnailLoadingTask::execute(Digikam::ThumbnailLoadingTask
* const this)
(/home/krikar/dev/kde/digikam/core/libs/threadimageio/thumbnailtask.cpp:169)
libdigikamcore.so.6.0.0!Digikam::LoadSaveThread::run(Digikam::LoadSaveThread *
const this)
(/home/krikar/dev/kde/digikam/core/libs/threadimageio/loadsavethread.cpp:133)
libdigikamcore.so.6.0.0!Digikam::DynamicThread::Private::run(Digikam::DynamicThread::Private
* const this)
(/home/krikar/dev/kde/digikam/core/libs/threads/dynamicthread.cpp:183)
libQt5Core.so.5![Unknown/Just-In-Time compiled code] (Unknown Source:0)
libpthread.so.0!start_thread(void * arg)
(/build/glibc-OTsEL5/glibc-2.27/nptl/pthread_create.c:463)
libc.so.6!clone()
(/build/glibc-OTsEL5/glibc-2.27/sysdeps/unix/sysv/linux/x86_64/clone.S:95)

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

[digikam] [Bug 373839] Continuously face thumbnails flicker/update

2018-09-07 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=373839

--- Comment #12 from Kristian Karl  ---
When debugging this morning, I paused during flicker, and paused execution.
Every time I paused , the stack trace for Digikam code started at:
https://github.com/KDE/digikam/blob/c013f88088bf08e321e4da8be71a61b02b67af2c/core/libs/widgets/itemview/itemviewcategorized.cpp#L997

I added before the return statement:
qCDebug(DIGIKAM_GENERAL_LOG) << "Event: " << event;
return DCategorizedView::viewportEvent(event);

Which now gave the following output during flicker:

digikam.general: Event:  QPaintEvent(QRegion(929,888 144x212))
digikam.general: Event:  QPaintEvent(QRegion(1083,888 144x212))
digikam.general: Event:  QPaintEvent(QRegion(1237,888 144x212))
digikam.general: Event:  QPaintEvent(QRegion(1545,888 144x212))
digikam.general: Event:  QPaintEvent(QRegion(1699,888 144x212))
digikam.general: Event:  QPaintEvent(QRegion(1853,888 144x212))
digikam.general: Event:  QPaintEvent(QRegion(2007,888 144x212))
digikam.general: Event:  QPaintEvent(QRegion(2161,888 144x212))
digikam.general: Event:  QPaintEvent(QRegion(1391,888 144x212))
digikam.general: Event:  QPaintEvent(QRegion(2315,888 144x212))
digikam.general: Event:  QPaintEvent(QRegion(2469,888 144x212))
digikam.general: Event:  QPaintEvent(QRegion(size=2, bounds=(2623,888 298x212)
- [(2623,888 144x212), (2777,888 144x212)]))
digikam.general: Event:  QPaintEvent(QRegion(2931,888 144x212))
digikam.general: Event:  QPaintEvent(QRegion(3085,888 144x212))
digikam.general: Event:  QPaintEvent(QRegion(3239,888 144x212))
digikam.general: Event:  QPaintEvent(QRegion(3393,888 144x212))
digikam.general: Event:  QPaintEvent(QRegion(3547,888 144x212))
digikam.general: Event:  QPaintEvent(QRegion(5,1110 144x212))
digikam.general: Event:  QPaintEvent(QRegion(159,1110 144x212))
digikam.general: Event:  QPaintEvent(QRegion(313,1110 144x212))
digikam.general: Event:  QPaintEvent(QRegion(467,1110 144x212))
digikam.general: Event:  QPaintEvent(QRegion(621,1110 144x212))
digikam.general: Event:  QPaintEvent(QRegion(775,1110 144x212))
digikam.general: Event:  QPaintEvent(QRegion(929,1110 144x212))
digikam.general: Event:  QPaintEvent(QRegion(1083,1110 144x212))
digikam.general: Event:  QPaintEvent(QRegion(1237,1110 144x212))
digikam.general: Event:  QPaintEvent(QRegion(1391,1110 144x212))
digikam.general: Event:  QPaintEvent(QRegion(1545,1110 144x212))
digikam.general: Event:  QPaintEvent(QRegion(1699,1110 144x212))
digikam.general: Event:  QPaintEvent(QRegion(1853,1110 144x212))
digikam.general: Event:  QPaintEvent(QRegion(2007,1110 144x212))
digikam.general: Event:  QPaintEvent(QRegion(size=2, bounds=(2161,1110 298x212)
- [(2161,1110 144x212), (2315,1110 144x212)]))
digikam.general: Event:  QPaintEvent(QRegion(size=2, bounds=(2469,1110 298x212)
- [(2469,1110 144x212), (2623,1110 144x212)]))
digikam.general: Event:  QPaintEvent(QRegion(2777,1110 144x212))
digikam.general: Event:  QPaintEvent(QRegion(2931,1110 144x212))
digikam.general: Event:  QPaintEvent(QRegion(3085,1110 144x212))
digikam.general: Event:  QPaintEvent(QRegion(3239,1110 144x212))
digikam.general: Event:  QPaintEvent(QRegion(3393,1110 144x212))
digikam.general: Event:  QPaintEvent(QRegion(3547,1110 144x212))
digikam.general: Event:  QPaintEvent(QRegion(5,1332 144x212))
digikam.general: Event:  QPaintEvent(QRegion(159,1332 144x212))
digikam.general: Event:  QPaintEvent(QRegion(313,1332 144x212))
digikam.general: Event:  QPaintEvent(QRegion(467,1332 144x212))
digikam.general: Event:  QPaintEvent(QRegion(621,1332 144x212))
digikam.general: Event:  QPaintEvent(QRegion(775,1332 144x212))
digikam.general: Event:  QPaintEvent(QRegion(929,1332 144x212))
digikam.general: Event:  QPaintEvent(QRegion(1083,1332 144x212))
digikam.general: Event:  QPaintEvent(QRegion(1237,1332 144x212))

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

[digikam] [Bug 373839] Continuously face thumbnails flicker/update

2018-09-07 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=373839

--- Comment #11 from Kristian Karl  ---
Absolutely!
I'll try some debugging of my own in the meantime. I got a dual screen setup to
hel me debug now.

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

[digikam] [Bug 373839] Continuously face thumbnails flicker/update

2018-09-06 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=373839

--- Comment #9 from Kristian Karl  ---
I tested this on a different 4k screen, and I get the same problem.
Using the latest from git: 0890e2005cae874dd1fcf71c2d3642152c00eff0, digikam
produces the following on the terminal during this flickering
:
:
digikam.general: Request to get thumbnail for ""
digikam.general: Could not open input file:  ""
digikam.general: Failed to extract video thumbnail for ""
QFSFileEngine::open: No file name specified
digikam.general: Request to get thumbnail for ""
digikam.general: Could not open input file:  ""
digikam.general: Failed to extract video thumbnail for ""
QFSFileEngine::open: No file name specified
digikam.general: Request to get thumbnail for ""
digikam.general: Could not open input file:  ""
digikam.general: Failed to extract video thumbnail for ""
QFSFileEngine::open: No file name specified
digikam.general: Request to get thumbnail for ""
digikam.general: Could not open input file:  ""
digikam.general: Failed to extract video thumbnail for ""
digikam.general: Request to get thumbnail for ""
QFSFileEngine::open: No file name specified
digikam.general: Could not open input file:  ""
digikam.general: Failed to extract video thumbnail for ""
QFSFileEngine::open: No file name specified
digikam.general: Request to get thumbnail for ""
digikam.general: Could not open input file:  ""
digikam.general: Failed to extract video thumbnail for ""
QFSFileEngine::open: No file name specified
digikam.general: Request to get thumbnail for ""
digikam.general: Could not open input file:  ""
digikam.general: Failed to extract video thumbnail for ""
QFSFileEngine::open: No file name specified
digikam.general: Request to get thumbnail for ""
digikam.general: Could not open input file:  ""
digikam.general: Failed to extract video thumbnail for ""
QFSFileEngine::open: No file name specified
:
:

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

[digikam] [Bug 397340] Update image file timestamps if metadata is written to sidecar file [patch]

2018-08-12 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=397340

--- Comment #5 from Kristian Karl  ---
If you don't mind. I can try to have a go at suggesting a new patch, where the
modification timestamp of the sidecar file is stored in the database (as Maik
suggested) and used.

I guess it will take me a week to do that.

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

[digikam] [Bug 397340] Update image file timestamps if metadata is written to sidecar file [patch]

2018-08-12 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=397340

--- Comment #4 from Kristian Karl  ---
I'm using my patch as a work-around for now.

Sync'd metadata is a bit more important to me, than the significant drawback of
increased backup times.

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

[digikam] [Bug 397340] Update image file timestamps if metadata is written to sidecar file [patch]

2018-08-10 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=397340

--- Comment #2 from Kristian Karl  ---
I went for a solution that was easy enough to implement.

I'm not sure if any data for sidecar files like, hash, size or modification
times are saved to the database?

I agree that the changing timestamps on files that are not actually changed is
not ideal.

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

[digikam] [Bug 397340] New: Update image file timestamps if metadata is written to sidecar file

2018-08-10 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=397340

Bug ID: 397340
   Summary: Update image file timestamps if metadata is written to
sidecar file
   Product: digikam
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Metadata-Sidecar
  Assignee: digikam-bugs-n...@kde.org
  Reporter: kristian.hermann.k...@gmail.com
  Target Milestone: ---

Created attachment 114391
  --> https://bugs.kde.org/attachment.cgi?id=114391=edit
Suggested patch

As a user I would expect that Digikam during startup would rescan images when
following settings are enabled:
 - "Update file timestamp when files are modified"
 - "Rescan file when files are modified"
 - "Write to sidecar files (Write to XMP sidecar only)

But since the only the sidecar file is modified, no changes will be detected
for those affected images during startup.

A suggested solution might be that when Digikam saves metadata only to the
sidecar file, also, the timestamp of the image file is updated.

I added a suggested patch that would implement the above.

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

[digikam] [Bug 397207] Too many open files, when reverse geocoding many images

2018-08-07 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=397207

--- Comment #3 from Kristian Karl  ---
I verified the fix.
Working well. Thanks!

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

[digikam] [Bug 397207] New: Too many open files, when reverse geocoding many images

2018-08-06 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=397207

Bug ID: 397207
   Summary: Too many open files, when reverse geocoding many
images
   Product: digikam
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Geolocation-ReverseGeoCoding
  Assignee: digikam-bugs-n...@kde.org
  Reporter: kristian.hermann.k...@gmail.com
  Target Milestone: ---

Created attachment 114319
  --> https://bugs.kde.org/attachment.cgi?id=114319=edit
Proposed patch

Running reverse geocoding on a large set of images, generates error:
GLib-ERROR **: Creating pipes for GWakeup: Too many open files


Actions
===
1) In the Geolocation Editor, select the Reverse Geocoding tab.
2) Select a large set of images. I used 5,000 images.
3) Select Open Street Map as the service
4) Click on Apply reverse geocding button

Expected result
===
All images with coordinates are reversed geocoded.

Actual result
=
After around 1, requests, digikam crashes.
First I got a SSL Handshake failed, error message dialog.
Then when I exit the Editor, digikam crashes with:
GLib-ERROR **: Creating pipes for GWakeup: Too many open files

Additional info
===
Running the same scenario again, and tracking number of open files using:
 watch -n1 "ls -la /proc/$(pidof digikam)/fd | wc -l"
I could see that the number was increasing, until I ran into the same problem.

A similar issue (https://github.com/albertlauncher/albert/issues/634) was fixed
by
https://github.com/albertlauncher/albert/commit/70e3662a8e3a08137073b5932dbd7ddee136ff65

When I tested their approach on digikam, digigam did not crash running the same
scenario.

Given the above I propose the attached fix.

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

[digikam] [Bug 392518] Face recognition using the deep learning algo, dont move faces to Unconfirmed

2018-03-31 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=392518

Kristian Karl <kristian.hermann.k...@gmail.com> changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Kristian Karl <kristian.hermann.k...@gmail.com> ---
Thanks!

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

[digikam] [Bug 392518] New: Face recognition using the deep learning algo, dont move faces to Unconfirmed

2018-03-30 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=392518

Bug ID: 392518
   Summary: Face recognition using the deep learning algo, dont
move faces to Unconfirmed
   Product: digikam
   Version: 6.0.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Faces-Recognition
  Assignee: digikam-bugs-n...@kde.org
  Reporter: kristian.hermann.k...@gmail.com
  Target Milestone: ---

Building latest from master on KDE Neon don't add recognized faces to the
Unconfirmed tag.

1) Start a fresh database of digikam
2) Add a collection with some test images
3) Tag at least 4 faces of each individual
4) Let digikam detect faces
5) Clear and rebuild all train data
6) Let digikam recognize faces using the deep learning algo
   (using 5.9 appimage does not let you choose any algos)

Expected result
++
Faces being recognized, and moved from the tag Unknown to Unconfirmed.
This works fine with latest appimage 5.9.0-01

Actual result
++
No faces are being recognized, nor moved to Unconfirmed.

Additional info:
+
I tested using the latest appimage build:
  digikam-5.9.0-01-x86-64.appimage
  Build date: Mar 18 2018 (target: RelWithDebInfo)
  Rev.: d7a4fdaf60753ef121aea95724bd618799390311
where it works fine. But I believe the deep learning algo is not available on
that build(?), at least it's not selectable from the "Scanning faces" dialog.

$ ldd build/core/app/digikam
linux-vdso.so.1 =>  (0x7ffd04921000)
libdigikamgui.so.6.0.0 =>
/home/krikar/dev/kde/digikam/build/core/app/libdigikamgui.so.6.0.0
(0x7f5fe4527000)
libdigikamcore.so.6.0.0 =>
/home/krikar/dev/kde/digikam/build/core/app/libdigikamcore.so.6.0.0
(0x7f5fe31a6000)
libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1
(0x7f5fe2f7d000)
libKF5FileMetaData.so.3 =>
/usr/lib/x86_64-linux-gnu/libKF5FileMetaData.so.3 (0x7f5fe2d5b000)
libQt5Sql.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Sql.so.5
(0x7f5fe2b12000)
libKF5I18n.so.5 => /usr/lib/x86_64-linux-gnu/libKF5I18n.so.5
(0x7f5fe28c1000)
libKF5CoreAddons.so.5 =>
/usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 (0x7f5fe262e000)
libKF5ConfigCore.so.5 =>
/usr/lib/x86_64-linux-gnu/libKF5ConfigCore.so.5 (0x7f5fe23d1000)
libQt5Widgets.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
(0x7f5fe1b74000)
libQt5Gui.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
(0x7f5fe13f1000)
libQt5Core.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
(0x7f5fe0d02000)
libdigikamdatabase.so.6.0.0 =>
/home/krikar/dev/kde/digikam/build/core/libs/database/libdigikamdatabase.so.6.0.0
(0x7f5fe08b)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
(0x7f5fe052e000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
(0x7f5fe0318000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f5fdff4e000)
libKF5Solid.so.5 => /usr/lib/x86_64-linux-gnu/libKF5Solid.so.5
(0x7f5fdfc6f000)
libQt5WebKitWidgets.so.5 =>
/usr/lib/x86_64-linux-gnu/libQt5WebKitWidgets.so.5 (0x7f5fdfa29000)
libgphoto2.so.6 => /usr/lib/x86_64-linux-gnu/libgphoto2.so.6
(0x7f5fdf7a5000)
libgphoto2_port.so.12 =>
/usr/lib/x86_64-linux-gnu/libgphoto2_port.so.12 (0x7f5fdf59a000)
libopencv_imgproc.so.3.4 => /usr/local/lib/libopencv_imgproc.so.3.4
(0x7f5fdcc8c000)
libopencv_core.so.3.4 => /usr/local/lib/libopencv_core.so.3.4
(0x7f5fdbd49000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f5fdba4)
libKF5XmlGui.so.5 => /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5
(0x7f5fdb737000)
libKF5KIOWidgets.so.5 =>
/usr/lib/x86_64-linux-gnu/libKF5KIOWidgets.so.5 (0x7f5fdb3fd000)
libKF5WindowSystem.so.5 =>
/usr/lib/x86_64-linux-gnu/libKF5WindowSystem.so.5 (0x7f5fdb1b3000)
libKF5IconThemes.so.5 =>
/usr/lib/x86_64-linux-gnu/libKF5IconThemes.so.5 (0x7f5fdaf75000)
libKF5Service.so.5 => /usr/lib/x86_64-linux-gnu/libKF5Service.so.5
(0x7f5fdacce000)
libQt5DBus.so.5 => /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
(0x7f5fdaa42000)
libQt5Xml.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Xml.so.5
(0x7f5fda807000)
libKF5WidgetsAddons.so.5 =>
/usr/lib/x86_64-linux-gnu/libKF5WidgetsAddons.so.5 (0x7f5fda4b6000)
libQt5XmlPatterns.so.5 =>
/usr/lib/x86_64-linux-gnu/libQt5XmlPatterns.so.5 (0x7f5fd9ecd000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x7f5fd9cb)
liblcms2.so.2 => /usr/lib/x86_64-linux-gnu/liblcms2.so.2
(0x7f5fd9a59000)
libtiff.so.5 => /usr/lib/x86_64-linux-gnu/libtiff.so.5
(0x7f5fd97e5000)
libpng12.so.0 => /lib/x86_64-linux-gnu/libpng12.so.0

[digikam] [Bug 387892] Crash in QtAV::VideoFrameExtractor

2017-12-28 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=387892

--- Comment #6 from Kristian Karl <kristian.hermann.k...@gmail.com> ---
I solved my problem which indeed was a problem with my ffmpeg libs. I happen to
have a mixture of install devlibs from the distro, as well as my own compiled
ffmpeg libs. When I removed the distro ffmpeg libs, Digikam now plays video
nicely.

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

[digikam] [Bug 387892] Crash in QtAV::VideoFrameExtractor

2017-12-15 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=387892

--- Comment #5 from Kristian Karl <kristian.hermann.k...@gmail.com> ---
Big thanks!

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

[digikam] [Bug 387892] Crash in QtAV::VideoFrameExtractor

2017-12-14 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=387892

Kristian Karl <kristian.hermann.k...@gmail.com> changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from Kristian Karl <kristian.hermann.k...@gmail.com> ---
Using ./digikam-5.8.0-20171212T132305-x86-64.appimage had no issues with the
same video files.
As you stated, must be some problem with my ffmpeg codecs that I compiled.

Could I ask which version of ffmpeg current appimage is using?

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

[digikam] [Bug 387892] Crash in QtAV::VideoFrameExtractor

2017-12-14 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=387892

--- Comment #1 from Kristian Karl <kristian.hermann.k...@gmail.com> ---
As a workaroun, turning ENABLE_MEDIAPLAYER to off works:
cmake  -DENABLE_MEDIAPLAYER=off ..

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

[digikam] [Bug 387892] New: Crash in QtAV::VideoFrameExtractor

2017-12-14 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=387892

Bug ID: 387892
   Summary: Crash in QtAV::VideoFrameExtractor
   Product: digikam
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Albums-MainView
  Assignee: digikam-bugs-n...@kde.org
  Reporter: kristian.hermann.k...@gmail.com
  Target Milestone: ---

Crash occurred when:
1) in the main Album view
2) scrolling down to a mp4 video.

Expected behavior
=
A thumbnail or an icon of a video

Actual behavior
===
Digikam crashed

Additional info

Compiled from sources, using:
 - ffmpeg, compiled from sources released version tags/n3.4.1
 - OpenCV, compiled from sources released version tags/3.3.1
 - QtAV, compiled from sources, latest master
 - Digikam, , compiled from sources, latest master

Ubuntu 16.04, KDE neon Developer Edition, Unstable Branches

Stacktrace
==
digikam.general: Request to get thumbnail for 
"/home/krikar/Pictures/2017/2017-01-03/2017-01-03_110620.mp4"
digikam.general: Trying to load Embedded preview with libraw
digikam.rawengine: Failed to load embedded RAW preview
digikam.general: Trying to load half preview with libraw
digikam.general: Trying to load Embedded preview with Exiv2
digikam.dimg: "/home/krikar/Pictures/2017/2017-01-03/2017-01-03_110740.mp4"  :
QIMAGE file identified
digikam.dimg.qimage: Can not load "
"/home/krikar/Pictures/2017/2017-01-03/2017-01-03_110740.mp4" " using
DImg::QImageLoader!
digikam.general: mimetype =  ""  ext =  "MP4"
digikam.general: Cannot create thumbnail for 
"/home/krikar/Pictures/2017/2017-01-03/2017-01-03_110740.mp4"
digikam.general: Thumbnail is null for 
"/home/krikar/Pictures/2017/2017-01-03/2017-01-03_110740.mp4"
digikam.general: Video duration for  "2017-01-03_110620.mp4" is  13739  seconds
digikam.general: Trying to get thumbnail from  "2017-01-03_110620.mp4"  at
position  2747
digikam.general: Trying to load Embedded preview with libraw
digikam.rawengine: Failed to load embedded RAW preview
digikam.general: Trying to load half preview with libraw
digikam.general: Trying to load Embedded preview with Exiv2
[New Thread 0x7ffe49826700 (LWP 15545)]
[New Thread 0x7ffe49025700 (LWP 15546)]
[New Thread 0x7ffe48824700 (LWP 15547)]
[New Thread 0x7ffe48023700 (LWP 15548)]
[New Thread 0x7ffe47822700 (LWP 15549)]
digikam.dimg: "/home/krikar/Pictures/2017/2017-01-03/2017-01-03_110829.mp4"  :
QIMAGE file identified
[New Thread 0x7ffe47021700 (LWP 15550)]
digikam.dimg.qimage: Can not load "
"/home/krikar/Pictures/2017/2017-01-03/2017-01-03_110829.mp4" " using
DImg::QImageLoader!
digikam.general: mimetype =  ""  ext =  "MP4"
digikam.general: Cannot create thumbnail for 
"/home/krikar/Pictures/2017/2017-01-03/2017-01-03_110829.mp4"
digikam.general: Thumbnail is null for 
"/home/krikar/Pictures/2017/2017-01-03/2017-01-03_110829.mp4"
[New Thread 0x7ffe46820700 (LWP 15551)]
[New Thread 0x7ffe4601f700 (LWP 15552)]
[New Thread 0x7ffe4581e700 (LWP 15553)]
*** stack smashing detected ***: /home/krikar/dev/kde/digikam/build/app/digikam
terminated

Thread 13 "QThread" received signal SIGABRT, Aborted.
[Switching to Thread 0x7fffa1ffb700 (LWP 15464)]
0x72c75428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
54  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  0x72c75428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#1  0x72c7702a in __GI_abort () at abort.c:89
#2  0x72cb77ea in __libc_message (do_abort=do_abort@entry=1,
fmt=fmt@entry=0x72dcf45f "*** %s ***: %s terminated\n")
at ../sysdeps/posix/libc_fatal.c:175
#3  0x72d5911c in __GI___fortify_fail (msg=,
msg@entry=0x72dcf441 "stack smashing detected") at fortify_fail.c:37
#4  0x72d590c0 in __stack_chk_fail () at stack_chk_fail.c:28
#5  0x7fffe83f9a28 in QtAV::AVDemuxer::readFrame() () from
/usr/lib/x86_64-linux-gnu/libQtAV.so.1
#6  0x7fffe8468466 in
QtAV::VideoFrameExtractorPrivate::extractInPrecision(long long, int, QString&,
bool&) ()
   from /usr/lib/x86_64-linux-gnu/libQtAV.so.1
#7  0x7fffe8466c7d in QtAV::VideoFrameExtractor::extractInternal(long long)
() from /usr/lib/x86_64-linux-gnu/libQtAV.so.1
#8  0x7fffe8466ae5 in
QtAV::VideoFrameExtractor::extract()::ExtractTask::run() () from
/usr/lib/x86_64-linux-gnu/libQtAV.so.1
#9  0x7fffe846737e in QtAV::ExtractThread::run() () from
/usr/lib/x86_64-linux-gnu/libQtAV.so.1
#10 0x73b68709 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7fffec94c6ba in start_thread (arg=0x7fffa1ffb700) at
pthread_create.c:333
#12 0x72d473dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109
(gdb)

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

[digikam] [Bug 387870] undefined reference to typeinfo for cv::face::FaceRecognizer

2017-12-13 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=387870

Kristian Karl <kristian.hermann.k...@gmail.com> changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Kristian Karl <kristian.hermann.k...@gmail.com> ---
No, and when I tried version 3.3.1 of OpenCV, digikam compiled and linked
nicely.
Thanks!

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

[digikam] [Bug 387870] New: undefined reference to typeinfo for cv::face::FaceRecognizer

2017-12-13 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=387870

Bug ID: 387870
   Summary: undefined reference to typeinfo for
cv::face::FaceRecognizer
   Product: digikam
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Faces-Detection
  Assignee: digikam-bugs-n...@kde.org
  Reporter: kristian.hermann.k...@gmail.com
  Target Milestone: ---

When building latest digikam
 * from master
 * on Ubuntu 16.04
 * using latest OpenCV (from master)
the linker fails linking libdigikamgui.so:

==
../libs/facesengine/CMakeFiles/digikamfacesenginedatabase_src.dir/recognition-opencv-lbph/opencvlbphfacerecognizer.cpp.o:
In function `Digikam::OpenCVLBPHFaceRecognizer::recognize(cv::Mat const&)':
opencvlbphfacerecognizer.cpp:(.text+0x74d): undefined reference to
`cv::face::FaceRecognizer::predict(cv::_InputArray const&, int&, double&)
const'
../libs/facesengine/CMakeFiles/digikamfacesenginedatabase_src.dir/recognition-opencv-lbph/facerec_borrowed.cpp.o:
In function `cv::face::FaceRecognizer::FaceRecognizer()':
facerec_borrowed.cpp:(.text._ZN2cv4face14FaceRecognizerC2Ev[_ZN2cv4face14FaceRecognizerC5Ev]+0x1b):
undefined reference to `vtable for cv::face::FaceRecognizer'
../libs/facesengine/CMakeFiles/digikamfacesenginedatabase_src.dir/recognition-opencv-lbph/facerec_borrowed.cpp.o:
In function `cv::face::FaceRecognizer::~FaceRecognizer()':
facerec_borrowed.cpp:(.text._ZN2cv4face14FaceRecognizerD2Ev[_ZN2cv4face14FaceRecognizerD5Ev]+0xf):
undefined reference to `vtable for cv::face::FaceRecognizer'
../libs/facesengine/CMakeFiles/digikamfacesenginedatabase_src.dir/recognition-opencv-lbph/facerec_borrowed.cpp.o:(.data.rel.ro._ZTVN7Digikam18LBPHFaceRecognizerE[_ZTVN7Digikam18LBPHFaceRecognizerE]+0x40):
undefined reference to `cv::face::FaceRecognizer::save(cv::String const&)
const'
../libs/facesengine/CMakeFiles/digikamfacesenginedatabase_src.dir/recognition-opencv-lbph/facerec_borrowed.cpp.o:(.data.rel.ro._ZTVN7Digikam18LBPHFaceRecognizerE[_ZTVN7Digikam18LBPHFaceRecognizerE]+0x68):
undefined reference to `cv::face::FaceRecognizer::load(cv::String const&)'
../libs/facesengine/CMakeFiles/digikamfacesenginedatabase_src.dir/recognition-opencv-lbph/facerec_borrowed.cpp.o:(.data.rel.ro._ZTVN7Digikam18LBPHFaceRecognizerE[_ZTVN7Digikam18LBPHFaceRecognizerE]+0x80):
undefined reference to `cv::face::FaceRecognizer::setLabelInfo(int, cv::String
const&)'
../libs/facesengine/CMakeFiles/digikamfacesenginedatabase_src.dir/recognition-opencv-lbph/facerec_borrowed.cpp.o:(.data.rel.ro._ZTVN7Digikam18LBPHFaceRecognizerE[_ZTVN7Digikam18LBPHFaceRecognizerE]+0x88):
undefined reference to `cv::face::FaceRecognizer::getLabelInfo(int) const'
../libs/facesengine/CMakeFiles/digikamfacesenginedatabase_src.dir/recognition-opencv-lbph/facerec_borrowed.cpp.o:(.data.rel.ro._ZTVN7Digikam18LBPHFaceRecognizerE[_ZTVN7Digikam18LBPHFaceRecognizerE]+0x90):
undefined reference to `cv::face::FaceRecognizer::getLabelsByString(cv::String
const&) const'
../libs/facesengine/CMakeFiles/digikamfacesenginedatabase_src.dir/recognition-opencv-lbph/facerec_borrowed.cpp.o:(.data.rel.ro._ZTIN7Digikam18LBPHFaceRecognizerE[_ZTIN7Digikam18LBPHFaceRecognizerE]+0x10):
undefined reference to `typeinfo for cv::face::FaceRecognizer'
collect2: error: ld returned 1 exit status
app/CMakeFiles/digikamgui.dir/build.make:1033: recipe for target
'app/libdigikamgui.so.5.8.0' failed
make[2]: *** [app/libdigikamgui.so.5.8.0] Error 1
CMakeFiles/Makefile2:7827: recipe for target
'app/CMakeFiles/digikamgui.dir/all' failed
make[1]: *** [app/CMakeFiles/digikamgui.dir/all] Error 2
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2
==

See also build log: https://pastebin.com/FL9qnpe6

Build configuration from building OpenCV from master:
https://pastebin.com/uc7CnRhN

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

[digikam] [Bug 387351] Meta data for RAW files checkbox disabled

2017-11-28 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=387351

--- Comment #7 from Kristian Karl <kristian.hermann.k...@gmail.com> ---
That was very sad news. 
My workflow is extensively built on placing all metadata in the image files.
Maybe sidecar files will be some sort of a workaround. But it would never beat
versatility and flexibility of having the metadata embedded in the image files.

Is there anything I could help with? Is there no possibility for us delivering
a patch in the Exiv2 library?

Digikam is very important to me, so I'll gladly help out :-)

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

[digikam] [Bug 384092] Writing gps metadata to sony alpha6300 raw files deletes data (white balance data probably)

2017-11-27 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=384092

Kristian Karl <kristian.hermann.k...@gmail.com> changed:

   What|Removed |Added

 CC||kristian.hermann.karl@gmail
   ||.com

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

[digikam] [Bug 381432] Olympus ORF files to DNG conversion fails in Windows 10

2017-11-27 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=381432

Kristian Karl <kristian.hermann.k...@gmail.com> changed:

   What|Removed |Added

 CC||kristian.hermann.karl@gmail
   ||.com

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

[digikam] [Bug 387351] Meta data for RAW files checkbox disabled

2017-11-27 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=387351

--- Comment #5 from Kristian Karl <kristian.hermann.k...@gmail.com> ---
Thanks!

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

[digikam] [Bug 387351] Meta data for RAW files checkbox disabled

2017-11-27 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=387351

--- Comment #3 from Kristian Karl <kristian.hermann.k...@gmail.com> ---
Ouch! A very good emergency break indeed!
@maik Do you happen to have a reference (bug report) of the root cause?

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

[digikam] [Bug 387351] New: Meta data for RAW files checkbox disabled

2017-11-27 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=387351

Bug ID: 387351
   Summary: Meta data for RAW files checkbox disabled
   Product: digikam
   Version: 5.8.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Metadata-Raw
  Assignee: digikam-bugs-n...@kde.org
  Reporter: kristian.hermann.k...@gmail.com
  Target Milestone: ---

Created attachment 109079
  --> https://bugs.kde.org/attachment.cgi?id=109079=edit
Screenshot of Settings dialog

In the Configure dialog, Metadata settings page, the check box: "If possible
write Metadata for RAW files (experimental)" is disabled (greyed out)

Steps to reproduce
==
1) Download digikam-5.8.0-20171126T055526-x86-64.appimage from
https://files.kde.org/digikam/
2) Start Digikam
3) Open "Settings -> Configure Digikam"
4) Select "Metadata" page

Expected results

The "If possible write Metadata for RAW files (experimental)" to be enabled,
and the user being able to select or deselect the checkbox.
Also, see attached sreenshot.

Actual results
==
The "If possible write Metadata for RAW files (experimental)" is disabled.


Additional info
===
I get the same behavior when using the install packages from Neon CI
.
Version of exiv2 libs installed are: 0.26-1+16.04+xenial+build12, also from
Neon CI.

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

[krunner] [Bug 383986] New: Crash when starting app

2017-08-25 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=383986

Bug ID: 383986
   Summary: Crash when starting app
   Product: krunner
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@privat.broulik.de
  Reporter: kristian.hermann.k...@gmail.com
  Target Milestone: ---

Application: krunner (5.10.5)

Qt Version: 5.9.1
Frameworks Version: 5.37.0
Operating System: Linux 4.10.0-32-generic x86_64
Distribution: KDE neon Developer Edition

-- Information about the crash:
- What I was doing when the application crashed:

Wheh using the shortcut Alt+space, the app crashed. This could be repeated a
couple of times.

The crash can be reproduced sometimes.

-- Backtrace:
Application: krunner (krunner), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fee13ed68c0 (LWP 30984))]

Thread 14 (Thread 0x7fedd5ffb700 (LWP 10764)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fee10ae28eb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x1758710) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=, mutex=0x12960d0,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215
#3  0x7fedeb3816df in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#4  0x7fedeb385768 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7fedeb3808cd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7fedeb3832e0 in ThreadWeaver::Thread::run() () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7fee10ae1989 in QThreadPrivate::start (arg=0x310a910) at
thread/qthread_unix.cpp:368
#8  0x7fee0e8756ba in start_thread (arg=0x7fedd5ffb700) at
pthread_create.c:333
#9  0x7fee103ee3dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 13 (Thread 0x7fedd67fc700 (LWP 10763)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fee10ae28eb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x1758710) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=, mutex=0x12960d0,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215
#3  0x7fedeb3816df in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#4  0x7fedeb385768 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7fedeb3808cd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7fedeb3832e0 in ThreadWeaver::Thread::run() () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7fee10ae1989 in QThreadPrivate::start (arg=0x7fedc8002fd0) at
thread/qthread_unix.cpp:368
#8  0x7fee0e8756ba in start_thread (arg=0x7fedd67fc700) at
pthread_create.c:333
#9  0x7fee103ee3dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 12 (Thread 0x7fedd6ffd700 (LWP 10762)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fee10ae28eb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x7fedbc0031e0) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=this@entry=0x7fedbc0031c8,
mutex=mutex@entry=0x7fedbc0031c0, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:215
#3  0x7fee10adb76b in QSemaphore::acquire (this=this@entry=0x7fedd6ffcba0,
n=n@entry=1) at thread/qsemaphore.cpp:143
#4  0x7fee10ce1e56 in QMetaObject::activate (sender=0x3417320,
signalOffset=, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7fedd6ffcc30) at kernel/qobject.cpp:3734
#5  0x7fee10ce2527 in QMetaObject::activate (sender=,
m=m@entry=0x7fede1a79cc0 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fedd6ffcc30)
at kernel/qobject.cpp:3628
#6  0x7fede187862f in PlacesRunner::doMatch (this=,
_t1=0x3105080) at
/workspace/build/obj-x86_64-linux-gnu/runners/places/moc_placesrunner.cpp:252
#7  0x7fedeb5a5678 in
Plasma::AbstractRunner::performMatch(Plasma::RunnerContext&) () from
/usr/lib/x86_64-linux-gnu/libKF5Runner.so.5
#8  0x7fedeb384f17 in
ThreadWeaver::Executor::run(QSharedPointer const&,
ThreadWeaver::Thread*) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#9  0x7fedeb383a40 in
ThreadWeaver::Job::execute(QSharedPointer const&,
ThreadWeaver::Thread*) () from

[digikam] [Bug 373839] Continuously face thumbnails flicker/update

2017-06-26 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=373839

--- Comment #6 from Kristian Karl <kristian.hermann.k...@gmail.com> ---
I have seen this problem on 2 different 4K screens. One connected to my
midtower machine. 
And last, my laptop Lenovo Thinkpad X240 connected using Display Port to a BenQ
BL3201PT 32-inch Ultra HD, running 3840x2160 30 FPS

It does not matter what size I have on the thumbnails, 128 or 256 px.

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

[digikam] [Bug 373839] Continuously face thumbnails flicker/update

2017-06-26 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=373839

--- Comment #4 from Kristian Karl <kristian.hermann.k...@gmail.com> ---
The flickering still exists digikam 5.7.0, installed from neon CI repository:
aptitude show digikam  
Package: digikam
State: installed
Automatically installed: no 
Version: 4:5.5.0+p16.04+git20170621.0646-0  
Priority: optional  
Section: graphics   
Maintainer: Neon CI <n...@kde.org>  
Architecture: amd64 
Uncompressed Size: 26,6 M   
Depends: digikam-data (= 4:5.5.0+p16.04+git20170621.0646-0), libqt5sql5-sqlite,
perl, libc6 (>= 2.14),
 libexiv2-14 (>= 0.25), libexpat1 (>= 2.0.1), libgcc1 (>= 1:3.0),
libgl1-mesa-glx | libgl1, libgomp1  
 (>= 4.9), libgphoto2-6 (>= 2.5.9), libgphoto2-port12 (>= 2.5.9),
libjasper1, libjpeg8 (>= 8c),   
 libkf5akonadicontact5, libkf5calendarcore5, libkf5configcore5,
libkf5configgui5, 
 libkf5configwidgets5, libkf5contacts5, libkf5coreaddons5,
libkf5filemetadata3, libkf5i18n5,  
 libkf5iconthemes5, libkf5kdelibs4support5, libkf5kiowidgets5,
libkf5kipi32.0.0, libkf5notifications5,
 libkf5notifyconfig5, libkf5sane5, libkf5service5, libkf5solid5,
libkf5threadweaver5, 
 libkf5widgetsaddons5, libkf5windowsystem5, libkf5xmlgui5, liblcms2-2
(>= 2.2+git20110628),   
 liblensfun0 (>= 0.2.8), liblqr-1-0 (>= 0.4.0), libmarblewidget-qt5-28,
libopencv-contrib2.4v5,   
 libopencv-core2.4v5, libopencv-imgproc2.4v5, libopencv-objdetect2.4v5,
libpng12-0 (>= 1.2.13-4), 
 libqt5concurrent5 (>= 5.9.0), libqt5core5a (>= 5.9.0), libqt5dbus5 (>=
5.9.0), libqt5gui5 (>= 5.9.0),
 libqt5network5 (>= 5.9.0), libqt5opengl5 (>= 5.9.0),
libqt5printsupport5 (>= 5.9.0), libqt5sql5 (>=  
 5.9.0), libqt5webkit5, libqt5widgets5 (>= 5.9.0), libqt5x11extras5,
libqt5xml5 (>= 5.9.0), libstdc++6
 (>= 5.2), libtiff5 (>= 4.0.3), libx11-6

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

[digikam] [Bug 381319] Keyboard modifier not caught when using Wacom Tablet [patch]

2017-06-17 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=381319

--- Comment #4 from Kristian Karl <kristian.hermann.k...@gmail.com> ---
Ok, I will do that.

I'm  using qt version 5.7.1

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

[digikam] [Bug 381319] Keyboard modifier not caught when using Wacom Tablet [patch]

2017-06-17 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=381319

--- Comment #2 from Kristian Karl <kristian.hermann.k...@gmail.com> ---
Running "git grep QApplication::keyboardModifiers" there is one more place:
libs/widgets/itemview/imagedelegateoverlay.cpp in
AbstractWidgetDelegateOverlay::checkIndexOnEnter

Maybe that should be changed as well? 

There are occurrences of perhaps similar usage of QDropEvent::keyboardModifiers
in:
app/dragdrop/albumdragdrop.cpp
app/dragdrop/imagedragdrop.cpp
app/dragdrop/importdragdrop.cpp
app/dragdrop/tagdragdrop.cpp
Not sure if the behavior of QDropEvent::keyboardModifiers is the same as
QApplication::keyboardModifiers(). If it is, then that should perhaps be
changed as well?

If you'd like, I can implement the changes above and test is?


I've have been using this patch locally on my machine for 7 months. I have not
seen any keyboard side effects due to this patch (with and without the Wacom
device connected).

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

[digikam] [Bug 381319] Keyboard modifier not caught when using Wacom Tablet

2017-06-17 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=381319

Kristian Karl <kristian.hermann.k...@gmail.com> changed:

   What|Removed |Added

Summary|Keyboard modifier not catch |Keyboard modifier not
   |when using Wacom Tablet |caught when using Wacom
   ||Tablet

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

[digikam] [Bug 381319] New: Keyboard modifier not catch when using Wacom Tablet

2017-06-17 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=381319

Bug ID: 381319
   Summary: Keyboard modifier not catch when using Wacom Tablet
   Product: digikam
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Usability
  Assignee: digikam-de...@kde.org
  Reporter: kristian.hermann.k...@gmail.com
  Target Milestone: ---

Created attachment 106137
  --> https://bugs.kde.org/attachment.cgi?id=106137=edit
Enable keyboard modifier for tablets Wacom

When using the Wacom Tablet, the keyboard modifier is not correctly identified.

1) When face tagging a user can Press Ctrl key and press mouse left button, and
thus creating a face tag rectangle.
2) Doing the same thing using a  Wacom Tablet does not work, unless the patch
is applied.

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

[digikam] [Bug 360155] Tag list is not filtered during face tag naming

2016-12-30 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=360155

--- Comment #11 from Kristian Karl <kristian.hermann.k...@gmail.com> ---
I tested it (compiled sources) and I can confirm that the bug is fixed.

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

[digikam] [Bug 373839] Continuously face thumbnails flicker/update

2016-12-25 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=373839

--- Comment #3 from Kristian Karl <kristian.hermann.k...@gmail.com> ---
Yes, I could reproduce the problem on the pre-release 5.4.0 AppImage.

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

[digikam] [Bug 373839] Continuously face thumbnails flicker/update

2016-12-18 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=373839

--- Comment #1 from Kristian Karl <kristian.hermann.k...@gmail.com> ---
I noticed this first, when using a maximized Digikam window on a 4K monitor,
where enough faces/thumbnails were rendered to cause the flickering.

Reducing the size of the Digikam window will make the flickering go away.

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

[digikam] [Bug 373839] New: Continuously face thumbnails flicker/update

2016-12-18 Thread Kristian Karl 
https://bugs.kde.org/show_bug.cgi?id=373839

Bug ID: 373839
   Summary: Continuously face thumbnails flicker/update
   Product: digikam
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Thumbnails
  Assignee: digikam-de...@kde.org
  Reporter: kristian.hermann.k...@gmail.com
  Target Milestone: ---

When opening the people view in a large window allowing for many faces, the
thumbnails will flicker continuously.

Steps to reproduce
==
1) Use the faces images from http://cswww.essex.ac.uk/mv/allfaces/faces94.html
   http://cswww.essex.ac.uk/mv/allfaces/faces94.zip
2) Create test folder and put the images there.
3) Create a new test database, and use the images above
5) Open the People view, and scan all images for faces using the default
options.
5) Look for Unknown, and set the size of the face thumbnails to smallest
(124px)
6) Make the window size for Digikam large enough until the flicker starts. I
usually get it with > ~210 faces (thumbnails).

Expected result

People view displays the thumbnails without flicker.

Actual result
===
People view displays the thumbnails constant flickering

Additional info
===
See video of flickering at https://youtu.be/AwmapnWNDBw
I get this on my laptop and desktop.

I was using digikam built from sources
(d72b486b7109fd80f6071fd78af2b9509de56044)

Observation
===
It seems that applying following patch makes the flicker go away. But I'm not
sure  what the downside of the patch is...

krikar@krikar-desktop:~/dev/kde/digikam/core$ git diff
diff --git a/app/items/imagecategorizedview.cpp
b/app/items/imagecategorizedview.cpp
index d5847c7..ba6dd47 100644
--- a/app/items/imagecategorizedview.cpp
+++ b/app/items/imagecategorizedview.cpp
@@ -737,14 +737,14 @@ ImageInfoList ImageCategorizedView::resolveGrouping(const
QModelIndexList indexe
 void ImageCategorizedView::paintEvent(QPaintEvent* e)
 {
 // We want the thumbnails to be loaded in order.
-ImageThumbnailModel* const thumbModel = imageThumbnailModel();
+/*ImageThumbnailModel* const thumbModel = imageThumbnailModel();

 if (thumbModel)
 {
 QModelIndexList indexesToThumbnail =
imageFilterModel()->mapListToSource(categorizedIndexesIn(viewport()->rect()));
 d->delegate->prepareThumbnails(thumbModel, indexesToThumbnail);
 }
-
+*/
 ItemViewCategorized::paintEvent(e);
 }

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

  1   2   >