Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=659641
--- Comment #14 from fujiwara tfujiwar@redhat.com 2011-02-22 20:12:54 EST --- (In reply to comment #13)
The original description (https://bugzilla.redhat.com/show_bug.cgi?id=659641#c0) contains the exact steps followed to reproduce the problem.
I think this does not include the required steps to reproduce your problem. I tried the steps yesterday again but I still cannot reproduce your problem.
As I said earlier (https://bugzilla.redhat.com/show_bug.cgi?id=659641#c7). Direct access to my system is "not an option."
Then I think it's good to just wait for another bug report which will include the proper steps or provide the access.
As I've stated earlier, this is only reproducible immediately after a reboot. So restarting and directly running the GTK language panel doesn't make sense. A useful debugging technique would be a way to tap the IBus communication and observe the communication to GTK language panel. Is there an easy way to do that?
Not sure since I don't see any problems. Maybe I think it would not be your task.
Basically I have thought if it's a good bug report: - Report the exact steps and software & hardware environments which the bug evaluators can reproduce it - Provide the access of test environments - Report the root cause - Report the patch
Otherwise I'd think it would be a low priority.