在 2013-10-15二的 23:23 +0900，Fuminobu TAKEYAMA写道：

Hello, M17N teammates,

I have noticed several problems with the ibus on 13.1 RC1:

(to be fixed soon) - ibus-lang is not installed https://bugzilla.novell.com/show_bug.cgi?id=845097 - ibus-ui-gtk3 does not show the current input mode on KDE https://bugzilla.novell.com/show_bug.cgi?id=845677

If you have 13.1, please test my patched package on home:ftake:branches:openSUSE:13.1

(will be fixed in 13.2) - xkb engines are not configured for GNOME https://bugzilla.novell.com/show_bug.cgi?id=844737

I have not checked carefully, but it seems that ibus-input-pad does not work at all because it is too old. It has been already dropped from 13.1.

# I am wondering why we do not have a classification category # like "input method" or "M17N" on the Bugzilla.

Best, -- Fuminobu TAKEYAMA

ibus-input-pad works fine under ibus 1.5.4 in openSUSE 12.3. I don't know what happened in your system. Perhaps, i should test it in openSUSE 13.1 later. I also think bnc#845677 must fix in openSUSE13.1, your patch is Ok. -- To unsubscribe, e-mail: opensuse-m17n+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-m17n+owner@opensuse.org

On Fri, Oct 18, 2013 at 2:12 AM, Fuminobu TAKEYAMA wrote:

...

...

(to be fixed soon) - ibus-lang is not installed https://bugzilla.novell.com/show_bug.cgi?id=845097 - ibus-ui-gtk3 does not show the current input mode on KDE https://bugzilla.novell.com/show_bug.cgi?id=845677

These bugs are fixed by SR from Marguerite yesterday. Thank you for testing my patch.

Hi, ftake, Actually I didn't fix those bugs...Yesterday I just ported an old fix I made to 12.3:Update to 13.1. Nothing more. Marguerite -- To unsubscribe, e-mail: opensuse-m17n+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-m17n+owner@opensuse.org

On Fri, Oct 18, 2013 at 2:11 PM, Fuminobu TAKEYAMA wrote:

...

Actually I didn't fix those bugs...Yesterday I just ported an old fix I made to 12.3:Update to 13.1.

There was an accident.

You did modify the package in M17N and submit to Factory and 13.1, right? I had fixed these bugs in M17N just before RC1 and submit it to Factory, but the submit was accepted for Factory but rejected for 13.1.

So I requested maintenance update, but your submit is a few hour earlier than my request...

...that's embrassed...sorry, my fault.

If the reviewers strictly followed the rule about updating 13.1 packages, they would have rejected your request because it includes update from 1.5.3 to 1.5.4...

Now the latest one is included 13.1. It is better.

13.1:Maintainence isn't alive yet...coolo said if you wanna something in 13.1, just add string "13.1 cherry-pickable" to your accepted view and forward... So I think they didn't "reject", but just didn't know you wanna that SR included.

A minor problem is that ibus.changes does not mention the bug reports. I think we may modify old entries just to add bnc#xxxxx.

don't know if it's possible. but anyway you can add a "no source change" changelog just to mention those two bugs have been fixed...this method is always possible :-) Marguerite -- To unsubscribe, e-mail: opensuse-m17n+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-m17n+owner@opensuse.org

Hello, Can anyone help me to fix the following bug? Updating to 1.5.4 causes a new problem. "Typed password on the GNOME lock screen is not hidden if IBus is active" https://bugzilla.novell.com/show_bug.cgi?id=847718 Then, gtk-im-modules installation macro has something wrong as reported in https://bugzilla.novell.com/show_bug.cgi?id=845861 Who is the maintainer of that macro? In Japan, the review of Ubuntu 13.10 is awful because it was shipped with many IBus 1.5 usability problems. Many people says "IBus 1.5 is useless" although some of the problems are Unity specific and they do not know a correct way for using IBus. (2013/10/15 23:23), Fuminobu TAKEYAMA wrote:

Hello, M17N teammates,

I have noticed several problems with the ibus on 13.1 RC1:

(to be fixed soon) - ibus-lang is not installed https://bugzilla.novell.com/show_bug.cgi?id=845097 - ibus-ui-gtk3 does not show the current input mode on KDE https://bugzilla.novell.com/show_bug.cgi?id=845677

If you have 13.1, please test my patched package on home:ftake:branches:openSUSE:13.1

(will be fixed in 13.2) - xkb engines are not configured for GNOME https://bugzilla.novell.com/show_bug.cgi?id=844737

I have not checked carefully, but it seems that ibus-input-pad does not work at all because it is too old. It has been already dropped from 13.1.

# I am wondering why we do not have a classification category # like "input method" or "M17N" on the Bugzilla.

Best,

-- Fuminobu TAKEYAMA -- To unsubscribe, e-mail: opensuse-m17n+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-m17n+owner@opensuse.org

Hi, friends,

"Typed password on the GNOME lock screen is not hidden if IBus is active" https://bugzilla.novell.com/show_bug.cgi?id=847718

You mean, when you lock screen and input password to get back, the input field just shows the password itself instead of "********", is that the case? If so...you don't need anyone to confirm. it is a security flaw. I'm now taking a look of the commit you mentioned. maybe later I'll start monkey coding again... And I suggest we just submit the fix directly to factory and ask coolo to copy it (RC2 will be released on Thursday next week, any _leaf_ SR before Monday will be in)

...

In Japan, the review of Ubuntu 13.10 is awful because it was shipped with many IBus 1.5 usability problems. I'm afraid that only few people are happy with the migration of IBUS on GNOME so far, mostly because of the unstability of IBUS 1.5 itself. IBUS 1.4 was nice and smooth, but 1.5 is far below that quality.

I'm afraid...*buntu + IBus will be everyone's worst nightmare forever. 1. *buntu didn't test as much as we do...they just see if their artwork works by raw eyes. They can't even do GNOME well. 2. IBus itself has been Fedora oriented or even Chrome OS oriented for a long time. RH people put too much hope on it. 3. And IBus maintainer for U doesn't even have time to care it. He now has been hired by Canonical full-time (Although he just went to university), working as a...well..."commercial support staff for fcitx" for "Ubuntu kylin", but most of the times he's working on "rejecting Unity crap C people made" to "guard free software territory" to "prevent those bad commits from ruining upstream libraries". So as I said a long time ago...man, you made a wrong comparison: In cases involving IBus, we should follow Fedora instead of Ubuntu...you could just ignore feedbacks from Ubuntu...actually Ubuntu itself has been deteriorating rapidly...most of its problems don't even exist on other distributions... PS: can you please update https://en.opensuse.org/openSUSE:Major_features ? add a paragraph that we have been migrating to IBus 1.5 together with GNOME 3.10, and mention all the efforts you have made...I don't know exactly what you did... Marguerite -- To unsubscribe, e-mail: opensuse-m17n+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-m17n+owner@opensuse.org

On Sunday, October 27, 2013 08:10:08 PM Marguerite Su Wrote:

Hi, friends,

...

"Typed password on the GNOME lock screen is not hidden if IBus is active" https://bugzilla.novell.com/show_bug.cgi?id=847718

You mean, when you lock screen and input password to get back, the input field just shows the password itself instead of "********", is that the case?

If so...you don't need anyone to confirm. it is a security flaw.

I'm now taking a look of the commit you mentioned. maybe later I'll start monkey coding again...

And I suggest we just submit the fix directly to factory and ask coolo to copy it (RC2 will be released on Thursday next week, any _leaf_ SR before Monday will be in)

...

...

In Japan, the review of Ubuntu 13.10 is awful because it was shipped with many IBus 1.5 usability problems.

I'm afraid that only few people are happy with the migration of IBUS on GNOME so far, mostly because of the unstability of IBUS 1.5 itself. IBUS 1.4 was nice and smooth, but 1.5 is far below that quality.

I'm afraid...*buntu + IBus will be everyone's worst nightmare forever.

1. *buntu didn't test as much as we do...they just see if their artwork works by raw eyes. They can't even do GNOME well.

2. IBus itself has been Fedora oriented or even Chrome OS oriented for a long time. RH people put too much hope on it.

3. And IBus maintainer for U doesn't even have time to care it. He now has been hired by Canonical full-time (Although he just went to university), working as a...well..."commercial support staff for fcitx" for "Ubuntu kylin", but most of the times he's working on "rejecting Unity crap C people made" to "guard free software territory" to "prevent those bad commits from ruining upstream libraries".

So as I said a long time ago...man, you made a wrong comparison: In cases involving IBus, we should follow Fedora instead of Ubuntu...you could just ignore feedbacks from Ubuntu...actually Ubuntu itself has been deteriorating rapidly...most of its problems don't even exist on other distributions...

PS: can you please update https://en.opensuse.org/openSUSE:Major_features ? add a paragraph that we have been migrating to IBus 1.5 together with GNOME 3.10, and mention all the efforts you have made...I don't know exactly what you did...

Marguerite Actually I don't see any "hiding" fix could make it work. Can you type the character you want with preedit or candidate shown in ****. Hide only preedit? or also hide candidate? None of them works for CJK user.

BTW, I don't think a "Unicode" Password make much sense. You can't even use input method in many case. Say if you use a Japanese Input method and set your password, then how can you ever get login into your tty? All input method solution (fbterm, and so on), need to be used after login into the tty. And if you set a website with some unicode password, you might have trouble login into it on your mobile phone. (For example, android doesn't let you to use non-Ascii password with default keyboard implementation). The reality doesn't allow you to use non-ascii password in so many case. (And does the website server can process it correctly?) Regards, Xuetian Weng

At Sun, 27 Oct 2013 20:23:42 +0800, Marguerite Su wrote:

On Sun, Oct 27, 2013 at 8:10 PM, Marguerite Su wrote:

...

I'm now taking a look of the commit you mentioned. maybe later I'll start monkey coding again...

I talked to phuang...he'll fix this issue in framework level instead of engine level ASAP.

Thanks, that'll be much better.

I'm afarid I can't do anything now because ibus-pinyin/chewing is written in C instead of python...those anthy fixes can't help us monkey coder...

OK, let's wait for seeing whether Phuang comes up with a better solution in IBUS core side. Takashi -- To unsubscribe, e-mail: opensuse-m17n+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-m17n+owner@opensuse.org