https://bugs.kde.org/show_bug.cgi?id=488342

            Bug ID: 488342
           Summary: When installed package "fcitx5", Kdialog misleading
                    user to install package "kcm-fcitx" conflicts with
                    package "fcitx5"
    Classification: Applications
           Product: kdialog
           Version: 24.05.0
          Platform: Arch Linux
                OS: Linux
            Status: REPORTED
          Severity: minor
          Priority: NOR
         Component: general
          Assignee: br...@frogmouth.net
          Reporter: itzgeno_offic...@163.com
  Target Milestone: ---

***
If you're not sure this is actually a bug, instead post about it at
https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY
When installed package "fcitx5",
Kdialog misleading user to install package "kcm-fcitx" conflicts with package
"fcitx5".

STEPS TO REPRODUCE
1. sudo pacman -S fcitx5
2. choose fcitx5 in System Settings > Keyboard > Virtual Keyboard
3. Right clicking the keyboard icon at the right side of taskbar and choose
"configure"
4(!). Kdialog reporting to user to install package "kcm-fcitx"
5. sudo pacman -S kcm-fcitx, but did not succeeded because they are in conflict

OBSERVED RESULT
Two packages are in conflict (Because it's not for fcitx5) , and still not able
to configure file in GUI.

EXPECTED RESULT
Kdialog should let user install fcitx5-configtool instead, so user can
configure fcitx5 in GUI.

SOFTWARE/OS VERSIONS
Windows: -
macOS: -
Linux/KDE Plasma: Kernel version 6.6.32-1-lts (64-bit)
(available in About System)
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.1

ADDITIONAL INFORMATION
Actually "kcm-config" cannot be used by even "fcitx" even though it's optional
required by it,
so it's completely useless and misleading from any aspect.
Use "fcitx-configtool" for "fcitx".

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to