Strange issues with pybluez

[Lukas Hetzenecker]

Hello,

i packaged my application with Pyinstaller 1.3 for Windows, but I've got into
troubles.

I used pybluez to connect to a bluetooth device and it worked correctly on my
computer, but some users reported problems:
> I installed Remote but when running the wizard setting, my device is not
detected.
> From sources, it was possible to run it!

I was able to reproduce the problem on the notebook of a classmate: Pybluez
didn't find any devices if it was packaged with Pyinstaller, but worked
correctly if it was run from sources.

I couldn't see any differences between the two notebook (both use the widcomm
bluetooth stack).

The application is located here: http://series60-remote.sf.net

Dowloads are located here:
http://sourceforge.net/project/showfiles.php?group_id=204429&package_id=243942

And here is the discussion in the Nokia forum:
http://discussion.forum.nokia.com/forum/showpost.php?p=540092&postcount=13

Does anybody know what could be the problem or a way to debug this?

Thanks for your help,
Lukas

[Gianni Valdambrini]

On 28 Giu, 01:54, Lukas Hetzenecker <L...@gmx.at> wrote:
> Hello,
>
> i packaged my application with Pyinstaller 1.3 for Windows, but I've got into
> troubles.

You should try with PyInstaller from SVN.. (PyInstaller 1.3 is
obsolete)

[Lukas Hetzenecker]

I tried it with the latest svn revision, but I get the same error... :-
(

On 29 Jun., 14:35, Gianni Valdambrini <gianni.valdambr...@gmail.com>
wrote:

[Giovanni Bajo]

On 7/1/2009 12:17 PM, Lukas Hetzenecker wrote:
> I tried it with the latest svn revision, but I get the same error... :-
> (

Hi Lucas,

by inspecting PyBluez, I see that in bluetooth/__init__.py it selects
between two alternatives method: widcomm and msbt (Microsoft). It does
this selection by looking for the wbtapi.dll in system folders.

Is it possible that, for instance, it selects the widcomm API in your
computer and the Microsoft API in your classmate's? Or viceversa?

You should try commenting the "return" line at the top of the module in
the _dbg() function to see the debug messages.

Basically, try putting "print" everywhere to find out what it is going
on. Also, please build your executable in debug mode (edit the spec file
and change debug=0 into debug=1) to see the standard output and see if
there is any traceback.
--
Giovanni Bajo
Develer S.r.l.
http://www.develer.com