ibus/indicator-keyboard call for testing

**jbicha** · July 17th, 2013

We are looking for people to try out the latest ibus and the new indicator-keyboard and report any issues they find. ibus is most commonly to input text in east Asian languages but indicator-keyboard will be useful to anyone using Unity that has a need for multilingual typing. More details are available at the following links:

https://lists.ubuntu.com/archives/ub...ly/037462.html

https://lists.ubuntu.com/archives/ub...ly/037486.html

**tista** · July 17th, 2013

Hi Jeremy

OK, I can join the test, so let me know what I should do for it?
I now am using stock ibus on saucy and "anthy" Japanese input engine.

Regards,
Tista

**jbicha** · July 17th, 2013

Originally Posted by tista

Hi Jeremy

OK, I can join the test, so let me know what I should do for it?

Did you read the links I posted?

Anyway, it's

Code:

sudo add-apt-repository ppa:ubuntu-desktop/ppa
sudo apt-get update
sudo apt-get upgrade
sudo apt-get install indicator-keyboard

...then log out and log back in. You can use System Settings>Region & Language>Text Entry to add your ibus engine or keyboard layout.

**tista** · July 17th, 2013

@Jeremy

Thanks for your advices!

Then now I've updated some packages and re-login...
As following your suggestions, I've added English as "keyboard layout" (since my PCs have US keyboard), and added Mozc as "Input Engine".

Surely Gnome-shell could show the "changing input" notification when pressing "Super+Space" key-bindings like this:

But...
The indicator of top panel could not follow this key-bindings and actual input method as well!

Only this could work with "Shift+Super+Space", yeah means "select the previous method or layout" you know...
And I've found this key-binding could not show that notification at all.

So next I've tested the context menu of top panel indicator, but no lock!
The context menu could not change input method (US natural input to Japanese Mozc input engine) at all.

Concluded, I could change the actual input method of ibus with this way only:
Pressing "Shift+Super+Space" key-binding.
It seems to give more love to new ibus today...

Regards,
Tista

**jbicha** · July 17th, 2013

Tista, thanks for the reply.

I installed ibus-mozc and logged out and logged back in. I then added mozc in System Settings>Region & Language. Super+Space works fine here as does GNOME Shell's keyboard layout status menu.

What version of gnome-shell are you using? Are you using any related PPAs? Except for the ubuntu-desktop PPA, I'm running almost "vanilla" Saucy today.

**tista** · July 18th, 2013

@Jeremy,

I installed ibus-mozc and logged out and logged back in. I then added mozc in System Settings>Region & Language. Super+Space works fine here as does GNOME Shell's keyboard layout status menu.

Really!? How nice...

What version of gnome-shell are you using? Are you using any related PPAs? Except for the ubuntu-desktop PPA, I'm running almost "vanilla" Saucy today.

Obviously I've been living with Ricotz Testing PPA. If so, there might be something wrong with it.
So ASAP I would re-install latest saucy daily build and employ ubuntu-desktop ppa only...

Cheers,
Tista

**zika** · July 18th, 2013

Originally Posted by tista

@Jeremy,

Really!? How nice...

Obviously I've been living with Ricotz Testing PPA. If so, there might be something wrong with it.
So ASAP I would re-install latest saucy daily build and employ ubuntu-desktop ppa only...

Cheers,
Tista

I think it is not Ricotz's PPA to blame... At least that feature works at my place (full Ricotz's treatment)...

**tista** · July 18th, 2013

@Jeremy

Today I'm tracking some logs down with my issue, and I've found some logs in .cache/gdm/session.log:

Code:

(gnome-shell:1508): Gjs-WARNING **: JS ERROR: Exception in callback for signal: destroy: Error: No signal connection 5 found
_disconnect@/usr/share/gjs-1.0/signals.js:74
PopupMenuBase<.addMenuItem/<@/usr/share/gnome-shell/js/ui/popupMenu.js:892
_emit@/usr/share/gjs-1.0/signals.js:124
PopupBaseMenuItem<.destroy@/usr/share/gnome-shell/js/ui/popupMenu.js:160
wrapper@/usr/share/gjs-1.0/lang.js:213
_parent@/usr/share/gjs-1.0/lang.js:175
PopupSubMenuMenuItem<.destroy@/usr/share/gnome-shell/js/ui/popupMenu.js:1362
wrapper@/usr/share/gjs-1.0/lang.js:213
PopupMenuBase<.removeAll@/usr/share/gnome-shell/js/ui/popupMenu.js:984
wrapper@/usr/share/gjs-1.0/lang.js:213
InputSourceIndicator<._buildPropSection@/usr/share/gnome-shell/js/ui/status/keyboard.js:678
wrapper@/usr/share/gjs-1.0/lang.js:213
InputSourceIndicator<._currentInputSourceChanged@/usr/share/gnome-shell/js/ui/status/keyboard.js:502
wrapper@/usr/share/gjs-1.0/lang.js:213

I'm not sure whether that log could relate my issue, anyway this could help you guys...

EDIT
And did you read this upstream bug report already?
https://bugzilla.gnome.org/show_bug.cgi?id=695723
It seems similar situation with mine..

Regards,
Tista

**jbicha** · July 18th, 2013

No, bug 695723 isn't really relevant now since the root problem was that Ubuntu had to revert changes in gnome-settings-daemon and gnome-control-center since we weren't ready for ibus 1.5 yet. That's no longer the case in the Desktop PPA and soon in Saucy.

Honestly, I'm simply not able to support the bleeding-edge Ricotz PPAs because I'm more interested in making sure regular Saucy works.

**tista** · July 19th, 2013

Originally Posted by jbicha

No, bug 695723 isn't really relevant now since the root problem was that Ubuntu had to revert changes in gnome-settings-daemon and gnome-control-center since we weren't ready for ibus 1.5 yet. That's no longer the case in the Desktop PPA and soon in Saucy.

Honestly, I'm simply not able to support the bleeding-edge Ricotz PPAs because I'm more interested in making sure regular Saucy works.

Hi Jeremy

I agree that stock "vanilla" Ubuntu-Gnome should be stable out of the box.
Then back to my issue, just now I've found the outside of gnome-shell, like flashback, seems to handle those input sources with "ibus's next input method" shortcuts:

It surely works great!

And if so, the configuration in gnome-control-center was avoided completely in flashback session. On the other side, I thought there is few reasons to test classic session because today classic session becomes "scaled-down gnome-shell" flavor, right?
(BTW: my flashback is very different with stock gnome's one. Since I now am trying to rebuilding lots of elementary crafts on saucy; gala window manager, wingpanel, slingshot launcher, plank dock, switchboard configuration tool, and more... So that shot actually showed the notification by gala. you know those shapes of notification was shown in mutter's stand-alone session mode. But in this time, I could not see any tray icons of keyboard/ibus).

Anyway I should do ppa-purging some PPAs or re-installing stock saucy, Not to miss the point of new ibus/gnome-shell integration stage...

Keep up the great work, Jeremy!
Tista