[digikam] [Bug 357944] wrong encoded collection paths after upgrade from digikam v4.x

https://bugs.kde.org/show_bug.cgi?id=357944 --- Comment #2 from Thomas Eschenbacher --- I'm sorry, but I don't have enough time to prepare an environment to reproduce and test it. Additionally my collection already is converted and I don't have an old digikam-4 at

[digikam] [Bug 360017] build error: opencv_contrib is required but was not found

https://bugs.kde.org/show_bug.cgi?id=360017 --- Comment #8 from Thomas Eschenbacher --- No response within one day? You guy seem to be really busy and impatient... Yes, I have seen your comment, but I have neither time nor motivation anymore to use a git version of

[digikam] [Bug 360017] build error: opencv_contrib is required but was not found

https://bugs.kde.org/show_bug.cgi?id=360017 Thomas Eschenbacher changed: What|Removed |Added Ever confirmed|0 |1

[digikam] [Bug 360017] build error: opencv_contrib is required but was not found

https://bugs.kde.org/show_bug.cgi?id=360017 --- Comment #2 from Thomas Eschenbacher --- ok, thanks for the information! You mean that opencv_contrib stuff is really still included in the "opencv" package? (I thougt that stuff has been removed) In that case I will

[digikam] [Bug 360017] New: build error: opencv_contrib is required but was not found

https://bugs.kde.org/show_bug.cgi?id=360017 Bug ID: 360017 Summary: build error: opencv_contrib is required but was not found Product: digikam Version: 5.0.0 Platform: Other OS: Linux Status:

[digikam] [Bug 358144] moving images with special characters in the file name does not work

https://bugs.kde.org/show_bug.cgi?id=358144 --- Comment #3 from Thomas Eschenbacher --- Interesting... after this patch I can see what was really wrong: there already are files with the same name! This was not obvious because file names were not shown in the Album

[digikam] [Bug 358053] drag and drop across local collections does not do anything

https://bugs.kde.org/show_bug.cgi?id=358053 --- Comment #6 from Thomas Eschenbacher --- Sorry, my mistake! You are right, that test was indeed across different partitions, even different disks (both using btrfs). But with your latest patch it is no longer reproducible

[digikam] [Bug 358053] drag and drop across local collections does not do anything

https://bugs.kde.org/show_bug.cgi?id=358053 --- Comment #4 from Thomas Eschenbacher --- No, the collections were on the same partition. I tried the latest git commit and now it works! Thanks for fixing it :-) (unfortunately I found out that moving files with special

[digikam] [Bug 358144] New: moving images with special characters in the file name does not work

https://bugs.kde.org/show_bug.cgi?id=358144 Bug ID: 358144 Summary: moving images with special characters in the file name does not work Product: digikam Version: 5.0.0 Platform: Other OS: Linux

[digikam] [Bug 357944] New: wrong encoded collection paths after upgrade from digikam v4.x

https://bugs.kde.org/show_bug.cgi?id=357944 Bug ID: 357944 Summary: wrong encoded collection paths after upgrade from digikam v4.x Product: digikam Version: 5.0.0 Platform: Other OS: Linux

[digikam] [Bug 357577] crashes after splash screen with ASSERT failure in QVector

https://bugs.kde.org/show_bug.cgi?id=357577 --- Comment #20 from Thomas Eschenbacher --- short update: now, after waiting for a very very long time, it shows Albums and Images again! It seems that it had to do it's job about face recognition in background, without any

[digikam] [Bug 357577] crashes after splash screen with ASSERT failure in QVector

https://bugs.kde.org/show_bug.cgi?id=357577 --- Comment #19 from Thomas Eschenbacher --- Thanks for the patch! It does not show any of my albums and I cannot see any picture anywhere, so the application is pretty useless at the moment, but at least it starts and no

[valgrind] [Bug 323431] VEX: unhandled instruction bytevex amd64->IR: 0x8F 0xE8 0x78 0xA2 0xC1 0x40 0xC5 0xFB

https://bugs.kde.org/show_bug.cgi?id=323431 --- Comment #5 from Thomas Eschenbacher --- I am affected by the same here: > uname -a Linux lisa 4.3.3-gentoo #1 SMP PREEMPT Fri Jan 8 07:01:39 CET 2016 x86_64 AMD A10-7870K Radeon R7, 12 Compute Cores 4C+8G AuthenticAMD

[valgrind] [Bug 323431] VEX: unhandled instruction bytevex amd64->IR: 0x8F 0xE8 0x78 0xA2 0xC1 0x40 0xC5 0xFB

https://bugs.kde.org/show_bug.cgi?id=323431 Thomas Eschenbacher changed: What|Removed |Added CC|

[digikam] [Bug 357577] crashes after splash screen with ASSERT failure in QVector

https://bugs.kde.org/show_bug.cgi?id=357577 --- Comment #13 from Thomas Eschenbacher --- sorry, that is not possible. Valgrind is broken and unusable too, crashes quite early due to this bug: https://bugs.kde.org/show_bug.cgi?id=323431 -- You are receiving this mail

[valgrind] [Bug 323431] VEX: unhandled instruction bytevex amd64->IR: 0x8F 0xE8 0x78 0xA2 0xC1 0x40 0xC5 0xFB

https://bugs.kde.org/show_bug.cgi?id=323431 --- Comment #6 from Thomas Eschenbacher --- using valgrind-3.11.0 -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 357577] crashes after splash screen with ASSERT failure in QVector

https://bugs.kde.org/show_bug.cgi?id=357577 --- Comment #11 from Thomas Eschenbacher --- No, debug symbols (as you get per -g in the CFLAGS) are necessary for a usable backtrace but not sufficient. You need to get theQt5 libs compiled "QT_DEBUG" defined and

[digikam] [Bug 357577] New: crashes after splash screen with ASSERT failure in QVector

https://bugs.kde.org/show_bug.cgi?id=357577 Bug ID: 357577 Summary: crashes after splash screen with ASSERT failure in QVector Product: digikam Version: 5.0.0 Platform: Compiled Sources OS: Linux

[digikam] [Bug 357577] crashes after splash screen with ASSERT failure in QVector

https://bugs.kde.org/show_bug.cgi?id=357577 --- Comment #1 from Thomas Eschenbacher --- Created attachment 96473 --> https://bugs.kde.org/attachment.cgi?id=96473=edit console output up to the crash -- You are receiving this mail because: You are watching all bug

[digikam] [Bug 357577] crashes after splash screen with ASSERT failure in QVector

https://bugs.kde.org/show_bug.cgi?id=357577 Thomas Eschenbacher changed: What|Removed |Added CC|

[digikam] [Bug 357577] crashes after splash screen with ASSERT failure in QVector

https://bugs.kde.org/show_bug.cgi?id=357577 --- Comment #3 from Thomas Eschenbacher --- as I wrote above: Qt-5.5.1 It is 100% reproducible here. -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 357577] crashes after splash screen with ASSERT failure in QVector

https://bugs.kde.org/show_bug.cgi?id=357577 --- Comment #6 from Thomas Eschenbacher --- how can I get this source version you are talking about? I followed the instructions on the project homepage, which lead me to this repo: > git remote -v origin