gnome-typing-monitor disappears from notification area via keyboard dialog

Bug #13180 reported by Jonathan Lim
12
Affects Status Importance Assigned to Milestone
gnome-control-center
Unknown
Medium
control-center (Ubuntu)
Invalid
Low
Ubuntu Desktop Bugs

Bug Description

Overview Description:
gnome-typing-monitor disappears from the notifications area when managed via the
keyboard dialog.
There is no apparent way to get it back via the keyboard dialog.

Steps to Reproduce
1) Open the Keyboard dialog Computer->Desktop Preferences->Keyboard
2) Select the Typing Break tab
3) Tick the Lock screen option
4) Close dialog
5) Right-click on typing break icon in notification area
6) Select Preferences
7) Deselect Lock screen

Actual Results
The typing-break icon disappears from the notifications area and will not
reappear using the keyboard dialog toggle.

Expected Results
The icon should remain in the bar, but greyed out.
This is the behaviour if you run gnome-typing-manager independently.

The gnome-typing-monitor via the Computer->Desktop Preferences->Keyboard dialog
enables and works fine.
However, if I disable it by toggling the Lock Screen, it disappears from the
notification area, and does not return when I try to toggle it on again.

If I start the gnome-typing-monitor from the command line, it greys out the icon
in the notifications area instead.

Build Date & Platform
capplets version 1:2.8.0-0ubuntu5 on Warty
-rwxr-xr-x 1 root root 44676 2004-10-12 19:10
/usr/bin/gnome-typing-monitor

http://bugzilla.gnome.org/show_bug.cgi?id=170452: http://bugzilla.gnome.org/show_bug.cgi?id=170452

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

I've opened an upstream bug for this:
http://bugzilla.gnome.org/show_bug.cgi?id=170452

Revision history for this message
Jason Toffaletti (jason) wrote :

I was able to reproduce on breezy the behavior of gnome-keyboard-preferences not
showing gnome-typing-monitor after a series of enables/disables and running
gnome-typing-monitor from the command line. Upstream's last comment is asking if
this is a debian/ubuntu specific bug, can anyone test this out on another
distro, Fedora, Gentoo, etc. and get back to upstream?

Revision history for this message
Martin Bergner (martin-bergner) wrote :

I can also reproduce this behaviour with dapper.

Changed in control-center:
status: Needs Info → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

Could somebody having that issue comment upstream?

Changed in control-center:
assignee: seb128 → desktop-bugs
Revision history for this message
Daniel Holbach (dholbach) wrote :

Does anybody still have the problem in Dapper or Edgy?

Revision history for this message
Martin Bergner (martin-bergner) wrote :

This still happens in Dapper, yes.

Revision history for this message
Wouter Stomp (wouterstomp-deactivatedaccount) wrote :

Is this still a problem in gutsy and/or hardy?

Changed in control-center:
status: Confirmed → Incomplete
Revision history for this message
Martin Bergner (martin-bergner) wrote :

Following the steps in the first comment, I can't reproduce the problem on gutsy anymore.

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

closing the bug

Changed in control-center:
status: Incomplete → Invalid
Changed in gnome-control-center:
importance: Unknown → Medium
status: Invalid → Unknown
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.