| Summary: | Crash when starting with xkbmap de(sundeadkeys) set | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Markus S. <markus.schwarzenberg> |
| Component: | Portability-Runtime | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | crash | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 8.5.0 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | 8.7.0 | |
| Sentry Crash Report: | |||
| Attachments: | debug log | ||
|
Description
Markus S.
2025-01-03 17:44:01 UTC
Did you run the AppImage bundle ? I also have openSUSE Tumbleweed, but I get the following error, what am I missing? maik@linux:~> setxkbmap de -variant sundeadkeys Error loading new keyboard description Maik 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 Created attachment 177132 [details]
debug log
The error appears at line 83 of the debug log.
After that, there is the output of
backtrace
thread apply all where
Then I continued (line 642) and SIGILL is issued
The output of "backtrace", and "thread apply all where" follows after that.
After the next continue the program finally terminates.
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 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" {
include "de(nodeadkeys)"
name[Group1] = "German (Sun dead keys)";
};
digikam (and one more qt6-app having the same problem) starts correctly again.
Markus
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 specific problem to the OpenSuse team as UPSTREAM. Best Gilles Caulier Understood. (But I didn't know this when I opened the bug). Thanks for your support. Markus |