Consider supporting application indicators
Bug #591317 reported by
Jorge Castro
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Application Indicators |
Invalid
|
Undecided
|
Unassigned | ||
Screenkey |
Fix Released
|
Medium
|
Pablo SEMINARIO |
Bug Description
Please consider supporting Ubuntu's application indicators!
https:/
description: | updated |
Changed in screenkey: | |
assignee: | nobody → Pablo Seminario (pabluk) |
status: | Confirmed → In Progress |
Changed in screenkey: | |
status: | In Progress → Fix Committed |
Changed in screenkey: | |
status: | Fix Committed → Fix Released |
milestone: | none → 0.2.0 |
Changed in indicator-application: | |
status: | New → Invalid |
To post a comment you must log in.
It already has support, however the problem is to do with how it is run.
If /dev/input/event0 has read access it runs and works fine, however if not, it has to be run with sudo.
When it is run with sudo, for some reason, appindicator hooks it into gtk.StatusIcon instead
This is a bug with appindicator and screenkey (only the necessary parts need be run was root)