Bug 1981 - Configuring multiple layouts in kcm_keyboard does not show systray icon anymore in 4.6.90
Summary: Configuring multiple layouts in kcm_keyboard does not show systray icon anymo...
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-01 00:12 CEST by Radu Cristian Fotescu
Modified: 2011-07-01 00:27 CEST (History)
0 users

See Also:
Source RPM: kdebase4-workspace-4.6.90-3.mga2
CVE:
Status comment:


Attachments

Description Radu Cristian Fotescu 2011-07-01 00:12:37 CEST
Description of problem:

In KDE 4.6.4, having multiple keyboard layouts (configured using the standard panel 'kcmshell4 kcm_keyboard'), the system tray displayed a keyboard layout switcher/indicator.

After upgrading to KDE 4.6.90, the systray keyboard indicator is gone!

The only way to have an indication of the current layout is to use the Keyboard Layout Plasmoid, which is ugly, huge, and can't stay in the systray.

Also, when using the plasmoid, the upstream bug 276692 applies:
https://bugs.kde.org/show_bug.cgi?id=276692
and this is also a reason why the standard systray icon should work.

I have somehow the feeling that this is not an upstream bug but a Mageia one (otherwise the upstream would have had a proper bug report).

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
Comment 1 Radu Cristian Fotescu 2011-07-01 00:27:13 CEST
Sorry, after logging off and logging on, the systray keyboard layout icon shows up normally.

I suppose the cause was that I killed kded4, which uses 75% of CPU after upgrading to 4.6.90. 

A new KDE session started kded4, and I guess this fixed the indicator.

Marking bug as RESOLVED INVALID.

Status: NEW => RESOLVED
Resolution: (none) => INVALID


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