Unnecessary gst-keyboard-xkb appearing in Notification Area when multiple keyboard layouts enabled

Bug #805747 reported by Andrew Cowie
374
This bug affects 75 people
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
Invalid
Low
Unassigned
gnome-shell (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

Running GNOME3 and enabling a second keyboard layout has caused a "[broken image] gst-keyboard-xkb" to appear in my Notification Area.

gnome-shell's active layout indicator up next to accessibility and volume is present and working. But a separate thing, calling itself "gst-keyboard-xkb" with a menu is incorrectly appearing in the Notification Area.

The annoying thing in the Notification Area would appear to be related to the libappindicator3-1 dependency but may be a GtkStatusIcon driven fallback.

Rebuilding the package to remove the appindicator support patches would likely fix the issue; that's not the right resolution of course but upstream does not consider this their problem since it arrises from an Ubuntu patch.

AfC

Revision history for this message
Robert Ancell (robert-ancell) wrote :

To reproduce:
1. Log into GNOME Shell
2. Add new layout: System Settings > Region and Language > Layouts, add new layout

Observed behaviour:
Broken icon is shown at bottom right of screen, hovering over it has test gsd-keyboard-xkb. Clicking on it shows the Unity indicator settings for keyboard layout.

Expected behaviour:
This element should not appear, as GNOME shell already has a keyboard layout switcher on the top of the screen

Changed in gnome-settings-daemon (Ubuntu):
status: New → Confirmed
Changed in gnome-shell (Ubuntu):
status: New → Confirmed
Revision history for this message
Vladimir Darak (vladimir-darak) wrote :

Same here.

Revision history for this message
alex diavatis (alexis-diavatis) wrote :

Same also

Revision history for this message
Sergey (litvin05) wrote :

now here is appearing gsd-keyboard-xkb "broken icon" :(

Revision history for this message
Stojan Dimitrovski (sdimitrovski) wrote :

This happens to me also. It is an annoying thing really.

Revision history for this message
Jeremy Bícha (jbicha) wrote :

Is this still reproducible? I still see the gsd-a11y-keyboard from System Settings>Universal Access>Typing>Turn on accessibility features from the keyboard, but I don't see gsd-keyboard-xkb.

Revision history for this message
Serhiy (xintx-ua) wrote :

Just updated my oneiric installation. It's still reproducible.

Revision history for this message
Reuben Thomas (rrt) wrote :

I just updated to oneiric and I'm getting this.

Revision history for this message
Michael Milligan (milli) wrote :

Absolutely quick and dirty fix for this...

$ apt-get source gnome-settings-daemon
...
$ sudo apt-get build-dep gnome-settings-daemon
...
$ sudo apt-get devscripts build-essential fakeroot patch patchutils
...
$ cd gnome-settings-daemon-3.2.0
$ patch -p1 < 0001-change.patch
$ debuild -uc -us -b
...
$ cd ..
$ sudo dpkg -i gnome-settings-daemon_3.2.0-*
...
$ sudo killall gnome-settings-daemon

gsd-keyboard-kbd applet should be GONE.

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "0001-change.patch" of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-sponsors please also unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]

tags: added: patch
Revision history for this message
Panagiotis (panagiotisgarbis) wrote :

i cant apply the patch above it gives me hunk failed...

Revision history for this message
Sebastien Bacher (seb128) wrote :

The indicator patch should only display an icon in the same case the upstream code displays an icon in the systray, could somebody check if that happens without the indicator patch?

Revision history for this message
Gabriel (misc-evotex) wrote :

super annoying...upgraded from 11.04 and I get this too.

Revision history for this message
Christopher Williams (crdlb) wrote :

GNOME Shell assigns known tray icons a 'role' based on their WM_CLASS. If the role that is filled by a native Shell status indicator, the icon is hidden. That list could be patched for a quick fix, but I'd prefer using the upstream icon as a fallback; is there any chance of that happening? The AppIndicator fallback does not identify the current layout.

Revision history for this message
Andriy Podanenko (podarokua) wrote :

the same for me
#9 just removes keyboard indicator from panel but not fix it 8(((

Revision history for this message
Sebastien Bacher (seb128) wrote :

the issue is not a gnome-settings-daemon but a gnome-shell whitelisting one then

Changed in gnome-shell (Ubuntu):
importance: Undecided → Low
Changed in gnome-settings-daemon (Ubuntu):
importance: Undecided → Low
status: Confirmed → Invalid
Revision history for this message
Sebastien Bacher (seb128) wrote :

> but I'd prefer using the upstream icon as a fallback; is there any chance of that happening? The AppIndicator fallback does not identify the current layout.

if you want to send a patch for that please do but that's non trivial since it requires having 2 different codepaths and a runtime selection, it's either to just use the indicator and let the automatic fallback do the work

tags: removed: patch
Revision history for this message
Dmitry Shachnev (mitya57) wrote :

Can someone please test if this bug occurs with the latest g-s-d in precise? I think it's a duplicate of bug 878951.

Revision history for this message
Yotam Benshalom (benshalom) wrote :

The problem seems to have been fixed in the latest Precise :)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.