https://bugs.kde.org/show_bug.cgi?id=412795
Simon Westersund changed:
What|Removed |Added
Keywords||usability
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=412795
Simon Westersund changed:
What|Removed |Added
CC||simon.westers...@iki.fi
--- Comment #6 from
https://bugs.kde.org/show_bug.cgi?id=427333
--- Comment #48 from Simon Westersund ---
Created attachment 133371
--> https://bugs.kde.org/attachment.cgi?id=133371&action=edit
Debug logs from stuck face detection in 8f1b5e900f
I retested with the 8f1b5e900f commit, and now it seems l
https://bugs.kde.org/show_bug.cgi?id=427333
--- Comment #46 from Simon Westersund ---
Hello Maik,
I reproduced the problem and ran into the ASSERT breakpoint. Is there anything
special you would want me to provide from gdb, or are backtraces and debug logs
still enough?
The short backtrace
https://bugs.kde.org/show_bug.cgi?id=427333
--- Comment #36 from Simon Westersund ---
Created attachment 133247
--> https://bugs.kde.org/attachment.cgi?id=133247&action=edit
Debug logs + GDB backtrace from 3d387983fe
Here is a bit of the debug log and the backtraces again. I took the
https://bugs.kde.org/show_bug.cgi?id=427333
--- Comment #35 from Simon Westersund ---
(In reply to Maik Qualmann from comment #34)
> Did you activate the debug output with:
>
> export QT_LOGGING_RULES="digikam.*=true"
>
> I expect debug output like this:
>
&g
https://bugs.kde.org/show_bug.cgi?id=427333
--- Comment #33 from Simon Westersund ---
Created attachment 133246
--> https://bugs.kde.org/attachment.cgi?id=133246&action=edit
GDB backtrace with latest master 3d387983fe
Hello Gilles and Maik,
I rebuilt the master branch from today an
https://bugs.kde.org/show_bug.cgi?id=427333
--- Comment #29 from Simon Westersund ---
Maik and Gilles,
I'm using Manjaro's default kernels. They have their own Kernel settings
through which users can install some kernels, and that is what I have used.
I can try to look for a way to
https://bugs.kde.org/show_bug.cgi?id=427333
--- Comment #25 from Simon Westersund ---
Created attachment 132258
--> https://bugs.kde.org/attachment.cgi?id=132258&action=edit
GDB backtrace with latest master 925e074a71
Here is the latest backtrace. We are now back to the original pure
https://bugs.kde.org/show_bug.cgi?id=427333
--- Comment #24 from Simon Westersund ---
(In reply to Maik Qualmann from comment #23)
> There is this message in the last backtrace and it surprises me after
> research:
>
> __memmove_avx_unaligned_erms () at /usr/lib/libc.so.6
>
&g
https://bugs.kde.org/show_bug.cgi?id=427333
--- Comment #22 from Simon Westersund ---
Created attachment 132247
--> https://bugs.kde.org/attachment.cgi?id=132247&action=edit
GDB backtrace with latest master 66f96e26b5
With the latest master, there is a segmentation fault crash, ins
https://bugs.kde.org/show_bug.cgi?id=427333
--- Comment #20 from Simon Westersund ---
Created attachment 132231
--> https://bugs.kde.org/attachment.cgi?id=132231&action=edit
GDB backtrace with latest master 182bef3be8
Here is a backtrace from the latest testing. The face detection
https://bugs.kde.org/show_bug.cgi?id=427333
--- Comment #17 from Simon Westersund ---
Created attachment 132218
--> https://bugs.kde.org/attachment.cgi?id=132218&action=edit
GDB backtrace with latest master 793a18d716 after deleting
DImg_ImageMagick_Plugin.so
Then I tested d
https://bugs.kde.org/show_bug.cgi?id=427333
--- Comment #16 from Simon Westersund ---
Created attachment 132217
--> https://bugs.kde.org/attachment.cgi?id=132217&action=edit
GDB backtrace with latest master 793a18d716
I simply built the latest master, without r
https://bugs.kde.org/show_bug.cgi?id=427333
--- Comment #12 from Simon Westersund ---
Created attachment 132199
--> https://bugs.kde.org/attachment.cgi?id=132199&action=edit
GDB backtrace with latest master b12004d560
Tested again and this time digikam crashed again, unfortunate
https://bugs.kde.org/show_bug.cgi?id=427333
--- Comment #11 from Simon Westersund ---
(In reply to Maik Qualmann from comment #8)
> Git commit 6478053c9490a73bb8b8c499750b2961627e18d2 by Maik Qualmann.
> Committed on 07/10/2020 at 16:27.
> Pushed by mqualmann into branch 'master&
https://bugs.kde.org/show_bug.cgi?id=427333
--- Comment #6 from Simon Westersund ---
Created attachment 132178
--> https://bugs.kde.org/attachment.cgi?id=132178&action=edit
GDB backtrace with latest master b7d3d74918
Hi Maik,
I tested again with the latest master, but the same functio
https://bugs.kde.org/show_bug.cgi?id=427333
--- Comment #3 from Simon Westersund ---
I tested again with GDB enabled and now the face scan crashed with a
segmentation fault, after it printed the warning that was added. The backtrace
was as follows:
[New Thread 0x7fff390e8640 (LWP 92762
https://bugs.kde.org/show_bug.cgi?id=427333
--- Comment #1 from Simon Westersund ---
Created attachment 132117
--> https://bugs.kde.org/attachment.cgi?id=132117&action=edit
bootstrap.local output of CMake configuration
Attached also my build configuration, if it might help differentia
https://bugs.kde.org/show_bug.cgi?id=427333
Bug ID: 427333
Summary: Face detection crashes due to pure virtual method call
in LoadingCache
Product: digikam
Version: 7.2.0
Platform: Manjaro
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=425723
--- Comment #29 from Simon Westersund ---
Created attachment 131500
--> https://bugs.kde.org/attachment.cgi?id=131500&action=edit
gdb backtrace with latest master a06b3c5
With the a06b3c5 commit from yesterday the face detection was able to
https://bugs.kde.org/show_bug.cgi?id=425723
--- Comment #27 from Simon Westersund ---
Created attachment 131491
--> https://bugs.kde.org/attachment.cgi?id=131491&action=edit
gdb backtrace with latest master fb76325
I tested with the latest master, which includes the latest fixes whi
https://bugs.kde.org/show_bug.cgi?id=425723
--- Comment #26 from Simon Westersund ---
(In reply to caulier.gilles from comment #23)
> Hi Simon,
>
> Please read also the story form this bug:
>
> https://bugs.kde.org/show_bug.cgi?id=426175
>
> This touch code from git/m
https://bugs.kde.org/show_bug.cgi?id=425723
--- Comment #22 from Simon Westersund ---
Created attachment 131483
--> https://bugs.kde.org/attachment.cgi?id=131483&action=edit
gdb backtrace with latest gsoc20 branch c1861ba
Thank you for the information Maik! I read your comment too lat
https://bugs.kde.org/show_bug.cgi?id=425723
--- Comment #19 from Simon Westersund ---
Created attachment 131477
--> https://bugs.kde.org/attachment.cgi?id=131477&action=edit
gdb backtrace with latest master 5102e32
I retested the master branch. This time my collection was processed u
https://bugs.kde.org/show_bug.cgi?id=425723
--- Comment #17 from Simon Westersund ---
Created attachment 131350
--> https://bugs.kde.org/attachment.cgi?id=131350&action=edit
gdb backtrace with gsoc20 branch + latest master 2fb8679
I tried this again with the gsoc20-facesengine-reco
https://bugs.kde.org/show_bug.cgi?id=425723
--- Comment #15 from Simon Westersund ---
Created attachment 131186
--> https://bugs.kde.org/attachment.cgi?id=131186&action=edit
gdb backtrace with gsoc20 branch + b61d547a and b3baed64 patches
So I tried to apply Maik's earlier patch t
https://bugs.kde.org/show_bug.cgi?id=425723
--- Comment #14 from Simon Westersund ---
Created attachment 131183
--> https://bugs.kde.org/attachment.cgi?id=131183&action=edit
gdb backtrace with gsoc20 branch + b61d547a patch
I applied the patch which Maik commented, and now I got th
https://bugs.kde.org/show_bug.cgi?id=425723
--- Comment #12 from Simon Westersund ---
Created attachment 131182
--> https://bugs.kde.org/attachment.cgi?id=131182&action=edit
gdb backtrace with gsoc20-facesengine-recognition 477fd19
Thanks for the suggestion Gilles!
I did what you su
https://bugs.kde.org/show_bug.cgi?id=425723
--- Comment #10 from Simon Westersund ---
Created attachment 131178
--> https://bugs.kde.org/attachment.cgi?id=131178&action=edit
gdb backtrace with latest master 00883ba
I went ahead and built the latest master branch (up until
https://bugs.kde.org/show_bug.cgi?id=425723
--- Comment #9 from Simon Westersund ---
Created attachment 131176
--> https://bugs.kde.org/attachment.cgi?id=131176&action=edit
gdb backtrace with patch b3baed6
Thanks for your patch suggestion! I applied th
https://bugs.kde.org/show_bug.cgi?id=425723
--- Comment #6 from Simon Westersund ---
Created attachment 131158
--> https://bugs.kde.org/attachment.cgi?id=131158&action=edit
single-threaded gdb backtrace with digikam built from source
I tested without the "Work on all processor c
https://bugs.kde.org/show_bug.cgi?id=425723
Simon Westersund changed:
What|Removed |Added
Attachment #131156|gdb thread apply all|gdb 'thread apply all
descri
https://bugs.kde.org/show_bug.cgi?id=425723
--- Comment #4 from Simon Westersund ---
Created attachment 131156
--> https://bugs.kde.org/attachment.cgi?id=131156&action=edit
gdb thread apply all backtrace' with digikam built from source
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=425723
Simon Westersund changed:
What|Removed |Added
Attachment #131132|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=425723
--- Comment #2 from Simon Westersund ---
@Maik, thanks for pointing this out. I tried to follow the instructions here:
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_with_GDB
and only
https://bugs.kde.org/show_bug.cgi?id=425723
Bug ID: 425723
Summary: Digikam crashes after a while when detecting faces
using multiple CPU cores
Product: digikam
Version: 7.0.0
Platform: Manjaro
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=408468
Simon Westersund changed:
What|Removed |Added
CC||simon.westersund@tutanota.c
https://bugs.kde.org/show_bug.cgi?id=386114
Simon Westersund changed:
What|Removed |Added
CC||simon.westersund@tutanota.c
https://bugs.kde.org/show_bug.cgi?id=399014
Simon Westersund changed:
What|Removed |Added
Version|17.12.0 |18.12.1
--- Comment #4 from Simon
https://bugs.kde.org/show_bug.cgi?id=399014
--- Comment #1 from Simon Westersund ---
This bug also reproduces on KDE Neon with:
Kate version 18.08.1
KDE Frameworks 5.50.0
Qt 5.11.1
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=399014
Bug ID: 399014
Summary: Text editor jumps when inserting a new bracket with
auto-brackets.
Product: kate
Version: 17.12.0
Platform: Ubuntu Packages
OS: Linux
42 matches
Mail list logo
