Issue 1 in socket-sentry: The "any" pseudo-device is not always available
socket...@googlecode.com
Owner: r...@hasselbaum.net
Labels: Type-Defect Priority-Medium
New issue 1 by r...@hasselbaum.net: The "any" pseudo-device is not always
available
http://code.google.com/p/socket-sentry/issues/detail?id=1
Socket Sentry defaults to the "any" pseudo-device in new widget instances,
but this device is not available in some builds of libpcap and/or the
kernel (e.g. Arch Linux). The widget should either default to an existing
device in these cases or at least guide the user toward selecting one.
Probably the latter will need to be done because guessing the correct
device creates its own set of problems.
Workaround: Users can choose another device from the config dialog and from
that point on, the "any" device will no longer show up as an option for
that widget.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
socket...@googlecode.com
Status: Fixed
Comment #1 on issue 1 by r...@hasselbaum.net: The "any" pseudo-device is
not always available
http://code.google.com/p/socket-sentry/issues/detail?id=1
Fixed in rev c4806df4e854 to land in release 0.9.2. Now, if the default
("any")
pseudo-device is not found and no other device has been selected, then the
applet
prompts the user to choose one.