https://bugs.kde.org/show_bug.cgi?id=475647
Bug ID: 475647
Summary: Uses CPU when idle
Classification: Applications
Product: kapman
Version: unspecified
Platform: Neon
OS: Linux
Status: REPORTED
Severi
https://bugs.kde.org/show_bug.cgi?id=475549
--- Comment #5 from Gary S. Martin ---
Apparently, the browser (Firefox) issue is resolved by setting the environment
variable MOZ_ENABLE_WAYLAND=1. (In Archlinux, you can set variables per wayland
session in ~/.config/environment.d/envvars.conf, as des
https://bugs.kde.org/show_bug.cgi?id=467713
--- Comment #12 from caulier.gil...@gmail.com ---
Git commit bbb2603eb75c734a56682bd86fdf53ce99a32939 by Gilles Caulier.
Committed on 15/10/2023 at 09:49.
Pushed by cgilles into branch 'master'.
digiKam online doc: remove the map of transcription of IPT
https://bugs.kde.org/show_bug.cgi?id=466938
caulier.gil...@gmail.com changed:
What|Removed |Added
Version Fixed In|8.0.0 |8.2.0
Status|REOPENED
https://bugs.kde.org/show_bug.cgi?id=466837
--- Comment #4 from caulier.gil...@gmail.com ---
@randy.w...@gmail.com,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last
https://bugs.kde.org/show_bug.cgi?id=465791
--- Comment #5 from caulier.gil...@gmail.com ---
@j...@acm.org,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last Qt frame
https://bugs.kde.org/show_bug.cgi?id=465002
--- Comment #3 from caulier.gil...@gmail.com ---
@514631...@qq.com,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last Qt f
https://bugs.kde.org/show_bug.cgi?id=475648
Bug ID: 475648
Summary: kwin_wayland crashing when starting Firefox Nightly
with Wayland backend
Classification: Plasma
Product: kwin
Version: git master
Platform: Compiled So
https://bugs.kde.org/show_bug.cgi?id=475648
--- Comment #1 from Kyle Devir ---
Generating the GDB backtrace was consuming all of my RAM, so I had to kill it,
but got this info:
#0 0x7f3e11f91324 in std::__uniq_ptr_impl >::_M_ptr (this=0x10) at
/usr/include/c++/13.2.1/bits/unique_ptr.h:199
1
https://bugs.kde.org/show_bug.cgi?id=475648
Kyle Devir changed:
What|Removed |Added
CC||kyle.de...@mykolab.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=464853
caulier.gil...@gmail.com changed:
What|Removed |Added
Summary|Adding new Keyword results |Adding new Keyword results
https://bugs.kde.org/show_bug.cgi?id=464266
--- Comment #16 from caulier.gil...@gmail.com ---
@n...@nickme.com,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last Qt f
https://bugs.kde.org/show_bug.cgi?id=464174
--- Comment #4 from caulier.gil...@gmail.com ---
@Andrew Sayman,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last Qt fram
https://bugs.kde.org/show_bug.cgi?id=464084
caulier.gil...@gmail.com changed:
What|Removed |Added
Version Fixed In||8.2.0
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=463760
--- Comment #4 from caulier.gil...@gmail.com ---
@fuerall...@gmail.com,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last
https://bugs.kde.org/show_bug.cgi?id=475649
Bug ID: 475649
Summary: Data loss when syncing Google contacts to Kaddressbook
due to missing fields, wrong mapping and edits not
saving.
Classification: Applications
Product:
https://bugs.kde.org/show_bug.cgi?id=463197
--- Comment #14 from caulier.gil...@gmail.com ---
@Metal450,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last Qt framewor
https://bugs.kde.org/show_bug.cgi?id=460941
--- Comment #5 from caulier.gil...@gmail.com ---
@Steve,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last Qt framework 5.
https://bugs.kde.org/show_bug.cgi?id=475649
Joel changed:
What|Removed |Added
CC||qrf4c5...@mozmail.com
--
You are receiving this mail be
https://bugs.kde.org/show_bug.cgi?id=460168
--- Comment #4 from caulier.gil...@gmail.com ---
@Julian,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last Qt framework 5
https://bugs.kde.org/show_bug.cgi?id=459875
--- Comment #6 from caulier.gil...@gmail.com ---
@Glen,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last Qt framework 5.1
https://bugs.kde.org/show_bug.cgi?id=459403
--- Comment #8 from caulier.gil...@gmail.com ---
@ludwigb...@aol.com,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last Qt
https://bugs.kde.org/show_bug.cgi?id=459163
--- Comment #21 from caulier.gil...@gmail.com ---
@maison,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last Qt framework
https://bugs.kde.org/show_bug.cgi?id=458720
--- Comment #7 from caulier.gil...@gmail.com ---
@OurKarma,
Do you seen my previous message ?
Gilles Caulier
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=422682
leodream2...@gmail.com changed:
What|Removed |Added
CC||leodream2...@gmail.com
--
You are rece
https://bugs.kde.org/show_bug.cgi?id=458584
--- Comment #3 from caulier.gil...@gmail.com ---
@j...@acm.org
Maik ask you to provide files tagged with GeoSetter application. Without this,
we cannot hack your problem.
Thanks in advance
Gilles Caulier
--
You are receiving this mail because:
You a
https://bugs.kde.org/show_bug.cgi?id=458583
--- Comment #5 from caulier.gil...@gmail.com ---
@j...@acm.org,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last Qt frame
https://bugs.kde.org/show_bug.cgi?id=458143
--- Comment #6 from caulier.gil...@gmail.com ---
@Jean-fred,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last Qt framewor
https://bugs.kde.org/show_bug.cgi?id=456926
--- Comment #3 from caulier.gil...@gmail.com ---
@Arnon,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last Qt framework 5.
https://bugs.kde.org/show_bug.cgi?id=456849
--- Comment #3 from caulier.gil...@gmail.com ---
@Viki,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last Qt framework 5.1
https://bugs.kde.org/show_bug.cgi?id=453880
--- Comment #7 from caulier.gil...@gmail.com ---
@gandanor...@gmail.com,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last
https://bugs.kde.org/show_bug.cgi?id=453815
--- Comment #4 from caulier.gil...@gmail.com ---
@herb,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last Qt framework 5.1
https://bugs.kde.org/show_bug.cgi?id=475650
Bug ID: 475650
Summary: DRD does not work with C11 threads
Classification: Developer tools
Product: valgrind
Version: unspecified
Platform: Archlinux
OS: Linux
Status:
https://bugs.kde.org/show_bug.cgi?id=475651
Bug ID: 475651
Summary: Add right click context menu in the Note text window
for Paste and Paste without Formatting
Classification: Applications
Product: Marknote
Version: unspecified
https://bugs.kde.org/show_bug.cgi?id=475553
Igor Kushnir changed:
What|Removed |Added
Ever confirmed|0 |1
CC|
https://bugs.kde.org/show_bug.cgi?id=475650
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=475400
--- Comment #10 from maizjo...@gmail.com ---
@bart
Unfortunately the problem has reappeared on my end in regard to both, no matter
if I there is VPN connection or not, so I have reinstalled the flatpak. Issue
briefly disappeared, but right now it still o
https://bugs.kde.org/show_bug.cgi?id=474609
Jérôme Poisson changed:
What|Removed |Added
CC||go...@goffi.org
--
You are receiving this mai
https://bugs.kde.org/show_bug.cgi?id=475652
Bug ID: 475652
Summary: Missing suppression for __wcsncpy_avx2
(strncpy-avx2.S:308)?
Classification: Developer tools
Product: valgrind
Version: 3.22 GIT
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=475549
Gary S. Martin changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=475653
Bug ID: 475653
Summary: Primary monitor is switched when coming back from
suspend/rebooting
Classification: Plasma
Product: kwin
Version: 5.27.8
Platform: Archlinux
https://bugs.kde.org/show_bug.cgi?id=475654
Bug ID: 475654
Summary: The right mouse button opens the desktop background
setting and gets stuck for about 1 minute.
Classification: Plasma
Product: plasmashell
Version: master
https://bugs.kde.org/show_bug.cgi?id=475652
Paul Floyd changed:
What|Removed |Added
Assignee|jsew...@acm.org |pjfl...@wanadoo.fr
CC|
https://bugs.kde.org/show_bug.cgi?id=475650
Paul Floyd changed:
What|Removed |Added
Assignee|bart.vanassche+...@gmail.co |pjfl...@wanadoo.fr
|m
https://bugs.kde.org/show_bug.cgi?id=416687
Yannis changed:
What|Removed |Added
CC||ya...@mailbox.org
--
You are receiving this mail beca
https://bugs.kde.org/show_bug.cgi?id=475650
--- Comment #1 from Paul Floyd ---
For reference
https://en.cppreference.com/w/c/thread/thrd_create
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=439610
Yannis changed:
What|Removed |Added
CC||ya...@mailbox.org
--
You are receiving this mail beca
https://bugs.kde.org/show_bug.cgi?id=466293
Yannis changed:
What|Removed |Added
CC||ya...@mailbox.org
--
You are receiving this mail beca
https://bugs.kde.org/show_bug.cgi?id=448866
--- Comment #15 from Dennis ---
My current solution is from the login screen via SDDM select X11 instead of
Wayland. NVIDIA drivers doesn't seem to like Wayland.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=453768
--- Comment #5 from caulier.gil...@gmail.com ---
@wodan71...@duetube.com,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on las
https://bugs.kde.org/show_bug.cgi?id=452874
--- Comment #5 from caulier.gil...@gmail.com ---
@Mr.D,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last Qt framework 5.1
https://bugs.kde.org/show_bug.cgi?id=452441
--- Comment #16 from caulier.gil...@gmail.com ---
@Steve Franks,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last Qt fram
https://bugs.kde.org/show_bug.cgi?id=452268
--- Comment #13 from caulier.gil...@gmail.com ---
@AlanB,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last Qt framework 5
https://bugs.kde.org/show_bug.cgi?id=452185
--- Comment #4 from caulier.gil...@gmail.com ---
@Marcin,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last Qt framework 5
https://bugs.kde.org/show_bug.cgi?id=468597
Maik Qualmann changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=450348
--- Comment #10 from caulier.gil...@gmail.com ---
@verweis-buergerin-0o,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last
https://bugs.kde.org/show_bug.cgi?id=468597
--- Comment #15 from Maik Qualmann ---
Note: The changes only take effect with the second digiKam installation.
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=450117
--- Comment #33 from caulier.gil...@gmail.com ---
@Rex Lee,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last Qt framework
https://bugs.kde.org/show_bug.cgi?id=449637
--- Comment #13 from caulier.gil...@gmail.com ---
@josh,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last Qt framework 5.
https://bugs.kde.org/show_bug.cgi?id=475652
--- Comment #1 from Paul Floyd ---
Python source here:
https://github.com/python/cpython/blob/84b7e9e3fa67fb9b92088d17839d8235f1cec62e/Python/fileutils.c#L2104
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=475652
--- Comment #2 from Paul Floyd ---
And
https://en.cppreference.com/w/c/string/wide/wcsncpy
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=475655
Bug ID: 475655
Summary: KDE Connect SMS hotkey mapped itself after updating
Classification: I don't know
Product: kde
Version: unspecified
Platform: Debian stable
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=446363
--- Comment #16 from caulier.gil...@gmail.com ---
@wuye9...@gmail.com,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last
https://bugs.kde.org/show_bug.cgi?id=444160
--- Comment #7 from caulier.gil...@gmail.com ---
@Jonathan,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last Qt framewor
https://bugs.kde.org/show_bug.cgi?id=439504
caulier.gil...@gmail.com changed:
What|Removed |Added
Severity|minor |wishlist
--
You are receiving this m
https://bugs.kde.org/show_bug.cgi?id=438429
--- Comment #9 from caulier.gil...@gmail.com ---
@Alessandro,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last Qt framew
https://bugs.kde.org/show_bug.cgi?id=475652
--- Comment #3 from Paul Floyd ---
Finally
https://elixir.bootlin.com/glibc/glibc-2.38/source/sysdeps/x86_64/multiarch/strncpy-avx2.S
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=437771
--- Comment #7 from caulier.gil...@gmail.com ---
@clara,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last Qt framework 5
https://bugs.kde.org/show_bug.cgi?id=437737
caulier.gil...@gmail.com changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Version Fixed In|
https://bugs.kde.org/show_bug.cgi?id=437658
--- Comment #4 from caulier.gil...@gmail.com ---
@herb,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last Qt framework 5.
https://bugs.kde.org/show_bug.cgi?id=437588
--- Comment #4 from caulier.gil...@gmail.com ---
Maik,
What's about to integrate this patch officially, in order in close also the bug
#437646 ?
Gilles
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=436975
--- Comment #5 from caulier.gil...@gmail.com ---
@herb,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last Qt framework 5.
https://bugs.kde.org/show_bug.cgi?id=438109
--- Comment #2 from caulier.gil...@gmail.com ---
@hann...@hot.ee,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last Qt fr
https://bugs.kde.org/show_bug.cgi?id=474740
hexchain changed:
What|Removed |Added
Ever confirmed|1 |0
Resolution|WAITINGFORINFO |--
https://bugs.kde.org/show_bug.cgi?id=436910
caulier.gil...@gmail.com changed:
What|Removed |Added
Summary|AdjustTimeDate changes the |Online doc: add
|va
https://bugs.kde.org/show_bug.cgi?id=436544
--- Comment #8 from caulier.gil...@gmail.com ---
@Thomas,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last Qt framework
https://bugs.kde.org/show_bug.cgi?id=435868
--- Comment #4 from caulier.gil...@gmail.com ---
@Ramon,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last Qt framework 5
https://bugs.kde.org/show_bug.cgi?id=435343
caulier.gil...@gmail.com changed:
What|Removed |Added
Resolution|--- |FIXED
Version Fixed In|8.1.0
https://bugs.kde.org/show_bug.cgi?id=434603
--- Comment #7 from caulier.gil...@gmail.com ---
@geekgu...@gmail.com,
Please take a care to my last comment, and review all points listed here with
the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/dig
https://bugs.kde.org/show_bug.cgi?id=434341
--- Comment #4 from caulier.gil...@gmail.com ---
@Jerry S,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last Qt framework
https://bugs.kde.org/show_bug.cgi?id=437588
Maik Qualmann changed:
What|Removed |Added
Resolution|--- |FIXED
Latest Commit|
https://bugs.kde.org/show_bug.cgi?id=432760
--- Comment #31 from caulier.gil...@gmail.com ---
@José Oliver-Didier,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last
https://bugs.kde.org/show_bug.cgi?id=431797
--- Comment #12 from caulier.gil...@gmail.com ---
@iain,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last Qt framework 5
https://bugs.kde.org/show_bug.cgi?id=431037
--- Comment #19 from caulier.gil...@gmail.com ---
@dajomu,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last Qt framework
https://bugs.kde.org/show_bug.cgi?id=431035
--- Comment #7 from caulier.gil...@gmail.com ---
@Samuel,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last Qt framework
https://bugs.kde.org/show_bug.cgi?id=430797
--- Comment #4 from caulier.gil...@gmail.com ---
@Nick,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last Qt framework 5.
https://bugs.kde.org/show_bug.cgi?id=475562
--- Comment #12 from Halla Rempt ---
That's dependent on the distribution... You probably need to configure
something that prevents stripping out debug info.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=429963
--- Comment #23 from caulier.gil...@gmail.com ---
@vadeinpa...@gmail.com,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on la
https://bugs.kde.org/show_bug.cgi?id=475617
Halla Rempt changed:
What|Removed |Added
CC||ha...@valdyas.org
--- Comment #1 from Halla Rempt
https://bugs.kde.org/show_bug.cgi?id=429230
--- Comment #6 from caulier.gil...@gmail.com ---
@alain.pouchard1...@free.fr,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based o
https://bugs.kde.org/show_bug.cgi?id=428187
--- Comment #10 from caulier.gil...@gmail.com ---
@Lrnt,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last Qt framework 5
https://bugs.kde.org/show_bug.cgi?id=475625
Halla Rempt changed:
What|Removed |Added
CC||ha...@valdyas.org
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=426355
caulier.gil...@gmail.com changed:
What|Removed |Added
Severity|crash |normal
--
You are receiving this mai
https://bugs.kde.org/show_bug.cgi?id=426355
caulier.gil...@gmail.com changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=426355
caulier.gil...@gmail.com changed:
What|Removed |Added
Version Fixed In||8.2.0
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=426000
--- Comment #22 from caulier.gil...@gmail.com ---
@Rex Lee,
This problem still reproducible with the new digiKam 8.2.0 pre-release Windows
installer available at usual place:
https://files.kde.org/digikam/
This new bundle is based on last Qt framewor
https://bugs.kde.org/show_bug.cgi?id=444160
Hans Lauter changed:
What|Removed |Added
CC||lavaw...@getnada.com
--- Comment #8 from Hans Lau
https://bugs.kde.org/show_bug.cgi?id=444160
--- Comment #9 from Hans Lauter ---
Created attachment 162319
--> https://bugs.kde.org/attachment.cgi?id=162319&action=edit
Wrong image recognition
An example: If I go on the suggestions for myself as a person in digikam.
Around 50-100 different peop
https://bugs.kde.org/show_bug.cgi?id=469623
--- Comment #13 from Alex Tucker ---
I finally managed to reproduce the bug, after paring down my system to just the
AMD GPU I was originally using ("APU" 5700G CPU with GPU) and restricting the
VRAM in the BIOS to 1GB. I believe it was 4GB when I origi
https://bugs.kde.org/show_bug.cgi?id=475656
Bug ID: 475656
Summary: Crash in QV4 engine upon Merkuro startup
Classification: Applications
Product: Merkuro
Version: 23.08.2
Platform: openSUSE
OS: Linux
Status: RE
1 - 100 of 302 matches
Mail list logo
