Client should notify the user if the user lacks permission to use it
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
wicd |
Fix Released
|
Medium
|
Andrew Psaltis |
Bug Description
If wicd's dbus configuration file is set up to allow only users that belong to a specific group to actually use wicd, then the client should have some way of telling users that they can't use it. To be clear, what happens currently is this:
On login, even though the tray icon is set to run on startup, it does not, and there's absolutely no kind of notification about *why* it didn't start. Click the wicd icon in the desktop menu, and absolutely nothing happens. Nothing.
If I start the client from a terminal, here's the traceback:
$ wicd-client
Loading...
Connecting to daemon...
Connected.
warning: ignoring exception org.freedesktop
Traceback (most recent call last):
File "/usr/lib/
main(sys.argv)
File "/usr/lib/
if DBUS_AVAIL and daemon.
File "/usr/lib/
**keywords)
File "/usr/lib/
message, timeout)
dbus.exceptions
If I start the curses client, here's what happens:
$ wicd-curses
Traceback (most recent call last):
File "/usr/lib/
parser = OptionParser(
File "/usr/lib/
return self._proxy_
File "/usr/lib/
**keywords)
File "/usr/lib/
message, timeout)
dbus.exceptions
I don't know what the best way to handle this is, so discussion is welcome - I just think that we should do *something* besides nothing. :-)
Related branches
- Dan O'Reilly: Needs Fixing
- Robby Workman (community): Approve
- Diff: None lines
Changed in wicd: | |
milestone: | none → 1.6-testing-release |
Changed in wicd: | |
importance: | Undecided → Medium |
Changed in wicd: | |
milestone: | 1.6-alpha → 1.6.1-release |
In the curses client, that is literally the first thing called after DBus is initialized. So, I could wrap that in a try/except block and print out an error message if that the user were not "allowed" to use wicd.