if you enable onscreen keyboard and then login/logout, onscreen stays checked but will not load automatically
Bug #973922 reported by
Mark Bokil
This bug affects 12 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Unity Greeter |
Fix Released
|
Undecided
|
Unassigned | ||
unity-greeter (Ubuntu) |
Fix Released
|
Low
|
Matt Fischer | ||
Bug Description
The onscreen keyboard menuitem shows a checked state but the keyboard is not visible. This forces the user to uncheck the onscreen keyboard menuitem and then select it again to make the keyboard visible. This occurs if the onscreen keyboard is used to login. Subsequent logins with the onscreen keyboard will show it as checked in the menu but its visibility is false. My guess is that the menu is defaulting to checked for onscreen keyboard but the keyboard visibility is false. The state of the onscreen keyboard menuitem needs to be unchecked if keyboard visibility is false when greeter screen is shown.
Related branches
lp:~mfisch/unity-greeter/unity-greeter-lp973922
- Unity Greeter Development Team: Pending requested
-
Diff: 77 lines (+21/-6)3 files modifiedsrc/main-window.vala (+5/-0)
src/menubar.vala (+15/-6)
src/unity-greeter.vala (+1/-0)
Changed in unity-greeter (Ubuntu): | |
status: | Confirmed → Triaged |
Changed in unity-greeter (Ubuntu): | |
assignee: | nobody → Matt Fischer (mfisch) |
summary: |
- onscreen keyboard menu item checked state wrong + if you enable onscreen keyboard and then login/logout, onscreen stays + checked but will not load automatically |
Changed in unity-greeter (Ubuntu): | |
assignee: | Matt Fischer (mfisch) → Michael Terry (mterry) |
Changed in unity-greeter (Ubuntu): | |
assignee: | Michael Terry (mterry) → Matt Fischer (mfisch) |
importance: | Undecided → Low |
Changed in unity-greeter (Ubuntu): | |
status: | Triaged → In Progress |
Changed in unity-greeter: | |
status: | New → Fix Committed |
Changed in unity-greeter (Ubuntu): | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
Status changed to 'Confirmed' because the bug affects multiple users.