[digikam] [Bug 498213] Crash when starting with xkbmap de(sundeadkeys) set

2025-03-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=498213 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||8.7.0 -- You are receiving this mail

[digikam] [Bug 498213] Crash when starting with xkbmap de(sundeadkeys) set

2025-03-16 Thread Markus S.
https://bugs.kde.org/show_bug.cgi?id=498213 Markus S. changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|---

[digikam] [Bug 498213] Crash when starting with xkbmap de(sundeadkeys) set

2025-03-15 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=498213 --- Comment #7 from caulier.gil...@gmail.com --- Hi, This dysfunction is not relevant of digiKam at all. Crash appears in Chromium component of Qt6. The work around with the XKB definition file is system dependent. In others words, report this very spec

[digikam] [Bug 498213] Crash when starting with xkbmap de(sundeadkeys) set

2025-03-15 Thread Markus S.
https://bugs.kde.org/show_bug.cgi?id=498213 --- Comment #6 from Markus S. --- After more research it turned out that in the XKB definition file /usr/share/X11/xkb/symbols/de the section for sundeadkeys was missing. After adding there partial alphanumeric_keys xkb_symbols "sundeadkeys"

[digikam] [Bug 498213] Crash when starting with xkbmap de(sundeadkeys) set

2025-03-15 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=498213 --- Comment #5 from caulier.gil...@gmail.com --- Hi, digiKam 8.6.0 is just released: https://www.digikam.org/news/2025-03-15-8.6.0_release_announcement/ Problem still exists with this version? Thanks in advance Gilles Caulier -- You are receiving

[digikam] [Bug 498213] Crash when starting with xkbmap de(sundeadkeys) set

2025-01-05 Thread Markus S.
https://bugs.kde.org/show_bug.cgi?id=498213 --- Comment #4 from Markus S. --- Created attachment 177132 --> https://bugs.kde.org/attachment.cgi?id=177132&action=edit debug log The error appears at line 83 of the debug log. After that, there is the output of backtrace thread apply all wh

[digikam] [Bug 498213] Crash when starting with xkbmap de(sundeadkeys) set

2025-01-03 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=498213 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Portability-Runtime -- You are recei

[digikam] [Bug 498213] Crash when starting with xkbmap de(sundeadkeys) set

2025-01-03 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=498213 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #2 from Maik

[digikam] [Bug 498213] Crash when starting with xkbmap de(sundeadkeys) set

2025-01-03 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=498213 Maik Qualmann changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because:

[digikam] [Bug 498213] Crash when starting with xkbmap de(sundeadkeys) set

2025-01-03 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=498213 --- Comment #3 from Maik Qualmann --- If I need a corresponding keyboard, it will be difficult to fix/reproduce this. Please create a GDB backtrace as described here: https://www.digikam.org/contribute/#linux-host-1 Maik -- You are receiving this ma

[digikam] [Bug 498213] Crash when starting with xkbmap de(sundeadkeys) set

2025-01-03 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=498213 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment