Bug 314741 - system settings -> Service Manager, start/stop buttons do not update when navigating list by keyboard
Summary: system settings -> Service Manager, start/stop buttons do not update when nav...
Status: RESOLVED FIXED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_kded (show other bugs)
Version: 4.9.4
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Daniel Molkentin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-09 04:15 UTC by As Long Ago, Rebirth Has Map (anagram of my real name)
Modified: 2013-02-11 21:36 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 4.10
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description As Long Ago, Rebirth Has Map (anagram of my real name) 2013-02-09 04:15:01 UTC
When selecting items in the list of startup services, the start and stop buttons update correctly when using the mouse only. When using the keyboard, the buttons retain their most recent selection with the mouse, if any---this is also true when tabbing out to the other load-on-demand list where the start/stop buttons should Both be disabled. If start is enabled and you select a list option in startup services that is started, pressing start will cause an error, same thing vice-versa. 


Reproducible: Always

Steps to Reproduce:
1.go to service manager
2.click a service
3.press up or down arrows
Actual Results:  
the start/stop buttons enabled state does not change

Expected Results:  
the button's state should change

i am a keyboard user and seldomly use the mouse so for many, it would go unnoticed, but keyboard users or (ESPECIALLY) speech-driven environment users will definately notice, esp. handicapped users will be seriously inconveinenced!
Comment 1 Jekyll Wu 2013-02-09 09:29:13 UTC
Thanks, I can reproduce the problem.
Comment 2 Christoph Feck 2013-02-11 02:30:56 UTC
Should be fixed in 4.10, please check.
Comment 3 Christoph Feck 2013-02-11 21:36:45 UTC
Yep, the commit for bug 283117 also fixed this one.