What steps will reproduce the problem?
1. Run a script via Windows XP's Scheduled Tasks under SYSTEM account and
pybluez fails to detect that a widcomm adapter is ready. The script I used
was actually compiled to exe with py2exe, but I don't think it makes any
difference.
2. Note that if the same script is run under "user" account everything
works fine
What is the expected output? What do you see instead?
widcomm.inquirer.is_device_ready() in __init__.py should return True and
pyblues should select widcomm stack. Instead, for some reason the function
fails to return True (needs more time?, etc?) and I end up with msbt, which
of course fails to find my widcomm device.
What version of the product are you using? On what operating system?
PyBluez-0.18.win32-py2.6 with python 2.6.4 on Windows XP/SP3
Please provide any additional information below.
If I use:
widcomm.inquirer.get_local_device_address() != None
as means of detecting if device is present or not whenever widcomm stack is
detected then it seems to work both under user and SYSTEM accounts.
Attaching patch that changes __init__.py to use the method described above.
Original issue reported on code.google.com by htren...@gmail.com on 2 Dec 2009 at 2:49
Original issue reported on code.google.com by
htren...@gmail.comon 2 Dec 2009 at 2:49Attachments: