Bug 1836 - Kimpanel package should have ibus backend version since we decided use ibus as default.
Summary: Kimpanel package should have ibus backend version since we decided use ibus a...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: New RPM package request (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
: 1907 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-06-17 15:55 CEST by Chih Wei Yao
Modified: 2011-07-01 18:36 CEST (History)
3 users (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Chih Wei Yao 2011-06-17 15:55:45 CEST 
Description of problem:
Currently we decided to use iBus as the default input method. Also, there's a plasma applet which can be used as the front end of input method called kimpanel.
What is weird is that originally the plasmoid is designed for iBus, then there's scim version, but we only have scim version in the repository, which is a pity.

Can we package a new rpm for the backend for iBus?

Version-Release number of selected component (if applicable):
4.6.4
Comment 1 Chih Wei Yao 2011-06-26 08:39:29 CEST 
Any process? I think it's important to help with the user experience. Especially for those who is used to the input method bar in Windows, it will certainly help.
Comment 2 You-Cheng Hsieh 2011-06-27 03:46:51 CEST 
*** Bug 1907 has been marked as a duplicate of this bug. ***

CC: (none) => yochenhsieh

Franklin Weng 2011-07-01 11:23:07 CEST

CC: (none) => franklin

Comment 3 Funda Wang 2011-07-01 18:34:31 CEST 
I've pushed kimpanel-backend-ibus and new ibus.

You may wan to test it by replacing ibus-daemon with ibus in /etc/sysconfig/i18n. It should start kimpanel by default in KDE. If not, please open another bug report on that issue.

CC: (none) => fundawang

Comment 4 Funda Wang 2011-07-01 18:36:30 CEST 
closing now.

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.