Bug 700978 - Keyboard layout indicator shows no icon, no text
Summary: Keyboard layout indicator shows no icon, no text
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 15
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-30 07:23 UTC by Nicholas Kudriavtsev
Modified: 2012-07-26 05:41 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-07-26 05:41:55 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Screenshot with blank keyboard indicator (1.06 MB, image/png)
2011-05-01 16:13 UTC, Nicholas Kudriavtsev
no flags Details
Screenshot with blank keyboard indicator and removed extensions (1.06 MB, image/png)
2011-05-02 16:27 UTC, Nicholas Kudriavtsev
no flags Details

Description Nicholas Kudriavtsev 2011-04-30 07:23:46 UTC
Description of problem: Gnome-shell panel's keyboard layout indicator shows no icon, no text

Version-Release number of selected component (if applicable):
gnome-shell-3.0.1-1

How reproducible: always

Steps to Reproduce:
I have two keyboard layouts.
  
Actual results:
The keyboard indicator button is blank.

Expected results:
Keyboard indicator should show flag (preferable) or text which is corresponding to current keyboard layout.

Comment 1 Elad Alfassa 2011-05-01 06:14:30 UTC
Please attach a screenshot.

Comment 2 Nicholas Kudriavtsev 2011-05-01 16:13:54 UTC
Created attachment 496074 [details]
Screenshot with blank keyboard indicator

Computer Accessibility icon is removed deliberately.

Comment 3 Elad Alfassa 2011-05-01 16:18:20 UTC
Have you edited gnome-shell files to make that change?
if so, yum reinstall gnome-shell will probably fix your problem.

Comment 4 Nicholas Kudriavtsev 2011-05-01 16:35:55 UTC
I have not edited any gnome-shell files, it is an extension. Keyboard indicator was blank after installation and consecutive updates and before I installed any extension.

Comment 5 Elad Alfassa 2011-05-01 17:09:48 UTC
Are the layouts shown properly in "System Settings"?

Comment 6 Nicholas Kudriavtsev 2011-05-01 18:35:17 UTC
Yes, they are shown properly. And also in drop down menu of keyboard indicator.

Comment 7 Owen Taylor 2011-05-02 14:26:57 UTC
Please remove the extension and retest. If the problem is reproducible without the extension, please tell us what keyboard layouts you have installed.

Comment 8 Nicholas Kudriavtsev 2011-05-02 16:27:34 UTC
Created attachment 496296 [details]
Screenshot with blank keyboard indicator and removed extensions

I have Russian and English (US) layouts.

Comment 9 Nicholas Kudriavtsev 2011-05-06 17:42:58 UTC
Well...

The default value of showFlags key in keyboard.js is true. Where is that key in GConf tree now?

Gnome-shell does not find flag icons for the indicator. Previously they were in /usr/share/pixmaps/flags. Where are they placed now? What is the package which contains them?

When I've patched keyboard.js as follow:

    _sync_config: function() {
        this._showFlags = this._config.if_flags_shown();
        this._showFlags = false; // ADDED THIS LINE
        if (this._showFlags) {
            this._container.set_skip_paint(this._iconActor, false);
        } else {
            this._container.set_skip_paint(this._iconActor, true);
        }

I can see text indicator.

Comment 10 Elad Alfassa 2011-05-06 18:52:16 UTC
gnome-shell doesn't use gconf, see http://live.gnome.org/GnomeGoals/GSettingsMigration

Comment 11 Nicholas Kudriavtsev 2011-05-07 07:38:45 UTC
OK!

'gsettings set org.gnome.libgnomekbd.indicator show-flags false' did the trick.

What about icons? Where should I place them to gnome-shell find them?

Comment 12 Nicholas Kudriavtsev 2011-05-07 19:26:42 UTC
Correct names for flag icons aren't us, ru and so on, but us-symbolic, ru-symbolic, etc. Works with png and svg icons.

Comment 13 Parag Nemade 2012-07-26 05:41:55 UTC
Keyboard Indicator is working fine in F17.


Note You need to log in before you can comment on or make changes to this bug.