After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 648582 - Giant keyboard layout indicator
Giant keyboard layout indicator
Status: RESOLVED DUPLICATE of bug 647646
Product: libgnomekbd
Classification: Core
Component: Drawing
unspecified
Other Linux
: Normal normal
: ---
Assigned To: libgnomekbd maintainers
Sergey V. Udaltsov
Depends on:
Blocks:
 
 
Reported: 2011-04-25 04:17 UTC by Richard
Modified: 2011-04-26 12:08 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Richard 2011-04-25 04:17:10 UTC 
When 'show keyboard layout' is selected from the gnome-shell keyboard panel icon, a giant keyboard layout window is shown (to big to fit on a single screen) with no close button.
Comment 1 Richard 2011-04-25 17:00:17 UTC 
Note: This only occurs with multiple monitor configurations. With a single monitor the window is properly sized (although has a 'Close' button down the bottom right of the window and no 'X' in the upper right).

The window size should be calculated to fit the display on which the panel with the keyboard configuration tray icon is located.
Comment 2 Owen Taylor 2011-04-25 20:20:23 UTC 
The layout indicator dialog comes from libgnomekbd - try:

 /usr/bin/gkbd-keyboard-display -g 0

While really the dialog should be sized according to the monitor where it is actually placed by the WM, I don't see any easy way to do that without resizing after being mapped, which would be ugly, so the easy, mostly correct thing to do is to use gdk_screen_get_primary_monitor()
Comment 3 Matthias Clasen 2011-04-26 12:08:22 UTC 
I think there was some problem where it used the screen size, rather than monitor dimensions. I thought it was fixed, but looks like it didn't: bug 647646
Comment 4 Matthias Clasen 2011-04-26 12:08:35 UTC 

*** This bug has been marked as a duplicate of bug 647646 ***