Qt5 Frontend of input method like Fcitx or hime can not be installed because they require qtbase-abi-5-5-1. qtbase-api-5-5-1 is a virtual package provide by libqt5core5a, but it can't be provided by current version . Without Qt5 Frontend, we can't type Chinese under Qt5 Apps. Reproducible: Always Steps to Reproduce: 1. # apt-get install fcitx-frontend-qt5 hime-qt5-immodule 2. # apt-get install qtbase-abi-5-5-1 3. Actual Results: It will tell us that our libqt5core5a is too new for qtbase-abi-5-5-1. Expected Results: Maybe we should have a new fcitx-frontend-qt5 package instead.
needs archive rebuilder added to our build system to rebuild some of these packages, work in progress..
I can confirm this is an issue in latest KDE Neon packages. I cannot input any CJK language in Qt5 apps due to this. I can in Chrome that is not Qt app. Below the output of apt-get: sudo apt-get install fcitx-frontend-qt5 Reading package lists... Done Building dependency tree Reading state information... Done Starting pkgProblemResolver with broken count: 1 Starting 2 pkgProblemResolver with broken count: 1 Investigating (0) fcitx-frontend-qt5:amd64 < none -> 1.1.1-1build3 @un puN Ib > Broken fcitx-frontend-qt5:amd64 Depends on qtbase-abi-5-9-5:amd64 < none @un H > Considering libqt5core5a:amd64 2981 as a solution to fcitx-frontend-qt5:amd64 10004 Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: fcitx-frontend-qt5 : Depends: qtbase-abi-5-9-5 E: Unable to correct problems, you have held broken packages.
I have latest neon and all packages upgraded. > cat /etc/issue KDE neon 5.13 \n \l
Is this issue still relevant for the 18.04.1-based Neon?
*** Bug 399321 has been marked as a duplicate of this bug. ***
I think this thread can be closed because this issue is resolved in https://bugs.kde.org/show_bug.cgi?id=461620