Bug 413137 - Global menu and fcitx make Krita's menu unusable
Summary: Global menu and fcitx make Krita's menu unusable
Status: RESOLVED DUPLICATE of bug 408015
Alias: None
Product: krita
Classification: Applications
Component: General (show other bugs)
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
Depends on:
Reported: 2019-10-18 11:21 UTC by Willem Sonke
Modified: 2019-10-18 11:49 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Screenshot of Krita without menu (80.92 KB, image/png)
2019-10-18 11:21 UTC, Willem Sonke

Note You need to log in before you can comment on or make changes to this bug.
Description Willem Sonke 2019-10-18 11:21:47 UTC
Created attachment 123315 [details]
Screenshot of Krita without menu

When fcitx (East-Asian / CJK input method) is used as the Qt IM module, and the Plasma global menu is active, Krita's global does not appear. Because the menu does not appear in the Krita window itself either, this makes Krita unusable for fcitx users, because menu commands are completely inaccessible.

This was reported before by Vladimir Yerilov in an unrelated closed bug (https://bugs.kde.org/show_bug.cgi?id=408015#c34).

(Tested on a freshly installed Kubuntu 19.10 VM.)
1. Right-click on the desktop, and do `Add Panel > Application Menu Bar`.
2. Open Konsole and verify the global menu bar works.
3. Install fcitx: `sudo apt install fcitx-bin`.
4. Install Krita: `sudo apt install krita`.
5. Run `QT_IM_MODULE=fcitx krita`.

No menu is present in the global menu, and the menu is not present in the Krita window either (see attached screenshot). Hence, the menu cannot be accessed.
In any other KDE/Qt applications (e.g. Konsole, Dolphin, Kate, Gwenview, ...) the global menu works correctly.

The global menu is present, or alternatively the menu is at least present in the Krita window itself.

Linux/KDE Plasma: Kubuntu 19.10 (Eoan)
KDE Plasma Version: 5.16.5
KDE Frameworks Version: 5.62.0
Qt Version: 5.12.4
Krita Version:

It looks like fcitx does not actually need to be running to trigger the bug. It being installed (and QT_IM_MODULE being set to `fcitx`) is enough to trigger the bug.

I do not know if this is a bug in the QPA, fcitx, or Krita, but I reported it in Krita due to the fact that it occurs only in Krita (and not in other applications).
Comment 1 Halla Rempt 2019-10-18 11:49:49 UTC
I'm sorry, but it's not really useful to report a bug that has been reported before again... We just cannot do anything about this in Krita. There really is no code in Krita that does anything special with the menu.

*** This bug has been marked as a duplicate of bug 408015 ***