Hi,
My Compose key (set to the Menu key) is not working in digikam, whether started from Kubuntu (Plasma) or from Xubuntu (XFCE desktop). I am running digikam by directly executing the digikam-6.4.0-x86-64.appimage file. It is working in all other applications that I have tested. By not working, I mean that the key has no effect: typing Compose o a results in oa instead of å. The only thing I can think off setting digikam apart from other programs is that I'm starting digikam as an appimage file. Could this cause the Compose key to be not working? Perhaps because it's not properly "integrated" in the desktop environment? What can I do to debug and/or fix it and get the Compose key to work? From export | grep IM: declare -x GTK_IM_MODULE="xim" declare -x QT_IM_MODULE="xim" declare -x XDG_RUNTIME_DIR="/run/user/1000" I have considered to try to install digikam from source to see if it works then, but this is a bit more complicated than I thought so I have paused this for now, and I don't know if it would solve the problem. (also asked at https://askubuntu.com/q/1206957/36831) Gerrit. |
hi, what do you mean by compose key exactly ? can you share a screenshot ? Gilles Caulier Le ven. 31 janv. 2020 à 23:58, Gerrit Holl <[hidden email]> a écrit : Hi, |
Hi,
On Sat, 1 Feb 2020 at 00:07, Gilles Caulier <[hidden email]> wrote: > what do you mean by compose key exactly ? can you share a screenshot ? I mean this one: https://en.wikipedia.org/wiki/Compose_key In KDE, I enable it like this: https://userbase.kde.org/Tutorials/ComposeKey it works in all applications, but not in digikam. I can't think of a screenshot to share that shown anything. I configured my Menu key (on my keyboard) as an alias to the Compose key (because I don't have a physical Compose key) following the KDE Compose Key tutorial. When I then press the Menu key, the next key press is a "dead" key depending on the combination; <Menu> o a -> å, <Menu> ' o -> ó, <Menu> s s -> ß, etc. For some reason I don't know it doesn't work in digikam; I just get oa, 'o, ss in the above examples (the key never becomes "dead" to begin with). I wonder if the appimage means it is somehow bypassing the standard input methods configuration? Hope that clarifies what I mean, sorry for the confusion. Gerrit. |
Hi all,
this is a problem I can reproduce, with Digikam 6.4 from an AppImage under Debian 10. I noticed another problem, by the way: missing icons e.g. in the "Albums" tree. Gerrit, you could try another AppImage to see if the broken compose key is more a general AppImage problem, or actually a digiKam problem. Only in the latter case I'd suggest filing a bug ticket for digiKam. I'm not a big fan of AppImages, and I no longer really need to be running the latest digiKam (or latest anything for that matter) all the time. It's only because of my network setup, and my Arch laptop having updated to the latest digiKam, that I thought I'd better also update digiKam on the other computer... So, Gerrit, if you require recent digiKam, and the compose key, but don't mind trying a new distro... go for Archlinux! Best, Vlado Am 01.02.20 um 00:26 schrieb Gerrit Holl: |
Free forum by Nabble | Edit this page |