Description: Many thanks to the testers for the help. K-Blueproximity is ready to upload. The result: about the 90 % of the mobile phones works well with this application.
Blueproximity is a security application. It can lock your computer if you leave your room, and can unlock it if you come back. Alternatively, you can also define other "proximity" actions. (See the third picture!) You only need a configured bluetooth device and a compatible mobile phone.
K-Blueproximity is a KDE frontend to the original Blueproximity application with a gtk frontend by Lars Friedrichs.
I think, you will not have problems on debian based systems as the dependecies are correct.
If you have the original gnome version of Blueproximity, uninstall it before! (If you need the GTK version, install the enclosed blueproximity-gtk package! It also works on debian ETCH, an egg.statusicon support module was added to the gtk based version.) For KDE, install only the blueproximity and blueproximity-kde packages!
On non-debian based systems, convert the blueproximity packages to rpm/tgz format, e.g.: alien --scripts blueproximity_version_all.deb
Dependencies for the KDE frontend: package bluez-utils, PyQt/PyKDE (python-qt3, python-kde3), ConfigObj (python-configobj) and Bluetooth (python-bluez or pybluez) extensions for python.
On my SuSE 10.2, the following packages are installed as dependencies:
bluez-libs 3.7-14 bluez-utils 3.7-29 gnome-bluetooth 0.8.0-26 kdebluetooth 0.99svn576598-38 libbtctl 0.8.0-26 (yast2-bluetooth 2.14.0-33) pybluez 0.9.2-47, I enclosed the source for this package.
Compile it with the command rpmbuild --rebuild pybluez-0.9.2-47.src.rpm, then install the package /usr/src/packages/RPMS/pybluez-0.9.2-47.i586.rpm!
You also need to download the package python-configobj from the packman site (http://packman.links2linux.de). I used the python-configobj-4.4.0-0.pm.1.i586.rpm (you can find it enclosed).
OpenSuSE 10.3: Similarly, but python-configobj must be compiled from the source: http://packman.links2linux.de/downloadsource/23295/python-configobj-4.4.0-0.pm.1.src.rpm and you need not compile pybluez. It is on the installation DVD.
Start K-Blueproximity from the KDE menu, and read the "KDE specific issues" section from the Help first!
Hi all,
I recommend you to use your distro's BlueProximity Package as this one does not work anymore with KDE4, because of the lack of xscreensaver (not installed as a default).
I use KDE4 with Kubuntu 8.04.1 and BP package is 1.24. You might use these commands to lock and unlock your screen :
lock : qdbus org.kde.screensaver /ScreenSaver Lock
unlock : killall -9 krunner_lock
This works here.
Also you might have a look at kbluelock, which intend to do the same thing as BlueProximity, but with a lack of functionnality and settings I think.
Also kbluemon and kblueplugd will gain your interest.
Good locking/unlocking :-)
Thank you BP team.
Fred.
I once again had to rebuild my workstation for various reasons. I've installed your app again and have configured it in addition to linking my phone to my bluetooth adapter. I'm now having problems keeping the connection between kblueproximity and my phone steady. It will connect then go gray saying no connection is established. It just cycles through gray->yellow->green->gray non-stop.
Any thoughts on what might be the problem?
I'm using KDE 3.5.x, my phone is a T-Mobile Dash and my bluetooth adapter is made by Kensington.
I've recently had to rebuild my system and in the process lost my configs for this. I've downloaded and installed it again but when I run it from the menu I get a version which I've always had problems with. This being the straight proximity.sh which is invoked from start_proximity.sh.
It never runs the kscreensaver options and locks no matter how close I am. I think I used to use the GTK version as is shown in the screenshots. However, now I run a different interface when invoked using the method above.
If I attempt to run kproximity.sh directly I get the following error:
Traceback (most recent call last):
File "/usr/bin/kproximity.py", line 132, in <module>
from proximity_api import *
ImportError: No module named proximity_api
I've installed pybluez, python-devel, python-configobj, libbtctl, kdebluetooth, bluez-libs and bluez-utils. Why won't it run?
The proximity_api is present in the package
blueproximity_1.2.2_all.deb
If you use a debian based system, you have installed it with a forced option or the dpkg is broken as it is on Etch.
If you use kde, install the package blueproximity-kde_1.2.2_all.deb.
If you prefer the gtk version install the
blueproximity-gtk_1.2.2_all.deb,
but it must be the last chance...
I've installed v1.2.2-2 on OpenSuSE 10.2. It works...for the most part.
The KDE part doesn't (throws some kind of python error) but the GTK frontend does. However, for some reason, I'm getting negative distances from my device. As a result I've had to set the lock distance to 2 in order for it to lock when I'm about 15 ft away. I've set the unlock distance to 1 and it unlocks about 12 feet out.
Is there a way to fix this or no?
Bluetooth is not a distance measuring device. The displayed value depends on your devices.
You mean: the KDE frontend does not work.
Try to start from command line:
python /usr/share/blueproximity/kproximity.py
Send me the output.
> Bluetooth is not a distance measuring device. The
> displayed value depends on your devices.
Perhaps, however, on a system running OpenSuSE 10.3 with a Kensington BT USB
adapter, it works perfectly. That package is blueproximity-1.2-1.2.noarch.rpm.
I've installed the package downloaded from KDE-Apps.org and ran `alien --scripts
-r` against the .deb packages to give me blueproximity-1.2-2.2.noarch.rpm. This
one gives me distance problems using the same adapter. Why would one version on
one system give me the distance problems while the other version on another
system not?
> You mean: the KDE frontend does not work.
> Try to start from command line:
> python /usr/share/blueproximity/kproximity.py
>
> Send me the output.
>
langs: ['en_US', 'en']
Traceback (most recent call last):
File "./kproximity.py", line 152, in <module>
Kproximity_Ui.__dict__["_Kproximity_Ui__tr"]=trans
TypeError: 'dictproxy' object does not support item assignment
This is on OpenSuSE 10.2
Unfortunately, for SuSE 10.2 there is not up-to-date pybluez. I think, you compiled from the enclosed src.rpm. You may try to compile from the src.rpm of SuSE 10.3.
The following error is a bug on SuSE:
"TypeError: 'dictproxy' object does not support item assignment"
Item assignment is a basic feature of python dictionaries. SuSE may use tuple, but it is a bug. The __dict__ is a dictionary not a tuple.
I try to find out another solution. The problem is only the translation stuff...
You need not it as:
langs: ['en_US', 'en'].
Unfortunately, for SuSE 10.2 there is not up-to-date pybluez. I think, you compiled from the enclosed src.rpm. You may try to compile from the src.rpm of SuSE 10.3.
The following error is a bug on SuSE:
"TypeError: 'dictproxy' object does not support item assignment"
Item assignment is a basic feature of python dictionaries. SuSE may use tuple, but it is a bug. The __dict__ is a dictionary not a tuple.
I try to find out another solution. The problem is only the translation stuff...
You need not it as:
langs: ['en_US', 'en'].
You can delete the line 152
Kproximity_Ui.__dict__["_Kproximity_Ui__tr"]=trans
in the file
/usr/share/blueproximity/kproximity.py.
(Translation will be disabled for the GUI.)
I've recently upgraded to openSuSE 10.3 and installed your app again with no problems. It runs but I'm unable to find my phone anymore. However, the adapter continuously sends out pairing requests. Any idea how I can turn this off. It seems to be something that pops up only after I install blueproximity after uninstalling it.
You can ignore the previous comment about the constant pairing requests. Turns out to have been a process that I didn't die.
I now have kproximity.py running relatively smoothly. However, I do have one concern. I've selected kscreensaver as my screensaver of choice but it doesn't fire off. The key goes red and the status indicates that my phone is "gone" but still, no screen locking. Do I have to configure it in some special way that isn't the same as gnome-screensaver or xscreensaver?
Ok, you can ignore that last one too. I guess I need to have xscreensaver running in order for KScreensaver to work.
I'm all good. I promise I'm not insane
Convert it to tar.gz with alien.
It does not contain any architecture/distribution specific part. You need not compile anything.
You may link the .desktop file if the K-menu fails to display Blueproximity.
1. The GTK frontend cannot be integrated into KDE. The systemtray policy is different.
2. The KScreenSaver works completely differently then the gnome-screensaver.
3. The GTK version is compatible only with unstable GTK versions. It does not work on debian ETCH.
4. The documentation with the instructions will be different. How can you use a gnome systemtray applet on KDE to setup your devices?
5. I am not an expert in GTK programming, but I understand KDE. I think, Lars Friedrichs is not an expert in QT/KDE programming, but he is an expert in Gnome
6. The fromtend is only a small part of the application. The API is the same for the two versions.
well said :-)
Although I might change some bits in my frontend to
a) make it KDE-friendlier (it will always stay a GNOMEized GTK+ based version)
b) may add support for stable pyGTK versions
once I have more time left. I'm doing my semester's test atm and my wife's expecting this month so I am quite busy...
Bye
Lars
i've tested your applications with positive feedback, from dpkg-tools-fe to PyWireless
wich is the main difference between this app and the new kbluetooth with bluelock inside?
tnx for answer
I only know this application:
"Bluelock is a small bash-scipt. Bluelock is written to check if a bluetooth device of you is available, if it's not it will lock your computer. So the idea is that if you walk away from your computer and you forget often to lock it, this script will do. But on the other hand if you stay near your computer, it won't lock, because you are close to him :)
To start it, you need to run the command:
bluelockd"
It cannot be configured at all.
Has the new KBluetoothD got also this feature?
I don't know it.
Could you send me a screenshot?
Hmm, this is probably the best example I've seen of the problem with linux. Can't beleive you went to the trouble of re coding the GUI just to match KDE! Nice work though, if I used KDE Im sure Id be happy :)
sheesh, you re-do it in QT and they complain about re-inventing the wheel...you don't, and they complain how "Linux has no consistent look and feel" from GTK apps in KDE/QT apps in GNOME.
Kinda makes you pine for Microsoft's "this is what you will use and this is what your apps will look like, have a nice day" philosophy, huh? :P
Ratings & Comments
27 Comments
Hi all, I recommend you to use your distro's BlueProximity Package as this one does not work anymore with KDE4, because of the lack of xscreensaver (not installed as a default). I use KDE4 with Kubuntu 8.04.1 and BP package is 1.24. You might use these commands to lock and unlock your screen : lock : qdbus org.kde.screensaver /ScreenSaver Lock unlock : killall -9 krunner_lock This works here. Also you might have a look at kbluelock, which intend to do the same thing as BlueProximity, but with a lack of functionnality and settings I think. Also kbluemon and kblueplugd will gain your interest. Good locking/unlocking :-) Thank you BP team. Fred.
Hmm I can lock the screen but this is only oneway, the unlock command doesn't work, any idea why? KDE 4.4.2
I once again had to rebuild my workstation for various reasons. I've installed your app again and have configured it in addition to linking my phone to my bluetooth adapter. I'm now having problems keeping the connection between kblueproximity and my phone steady. It will connect then go gray saying no connection is established. It just cycles through gray->yellow->green->gray non-stop. Any thoughts on what might be the problem? I'm using KDE 3.5.x, my phone is a T-Mobile Dash and my bluetooth adapter is made by Kensington.
I've recently had to rebuild my system and in the process lost my configs for this. I've downloaded and installed it again but when I run it from the menu I get a version which I've always had problems with. This being the straight proximity.sh which is invoked from start_proximity.sh. It never runs the kscreensaver options and locks no matter how close I am. I think I used to use the GTK version as is shown in the screenshots. However, now I run a different interface when invoked using the method above. If I attempt to run kproximity.sh directly I get the following error: Traceback (most recent call last): File "/usr/bin/kproximity.py", line 132, in <module> from proximity_api import * ImportError: No module named proximity_api I've installed pybluez, python-devel, python-configobj, libbtctl, kdebluetooth, bluez-libs and bluez-utils. Why won't it run?
The proximity_api is present in the package blueproximity_1.2.2_all.deb If you use a debian based system, you have installed it with a forced option or the dpkg is broken as it is on Etch. If you use kde, install the package blueproximity-kde_1.2.2_all.deb. If you prefer the gtk version install the blueproximity-gtk_1.2.2_all.deb, but it must be the last chance...
I've installed v1.2.2-2 on OpenSuSE 10.2. It works...for the most part. The KDE part doesn't (throws some kind of python error) but the GTK frontend does. However, for some reason, I'm getting negative distances from my device. As a result I've had to set the lock distance to 2 in order for it to lock when I'm about 15 ft away. I've set the unlock distance to 1 and it unlocks about 12 feet out. Is there a way to fix this or no?
Bluetooth is not a distance measuring device. The displayed value depends on your devices. You mean: the KDE frontend does not work. Try to start from command line: python /usr/share/blueproximity/kproximity.py Send me the output.
> Bluetooth is not a distance measuring device. The > displayed value depends on your devices. Perhaps, however, on a system running OpenSuSE 10.3 with a Kensington BT USB adapter, it works perfectly. That package is blueproximity-1.2-1.2.noarch.rpm. I've installed the package downloaded from KDE-Apps.org and ran `alien --scripts -r` against the .deb packages to give me blueproximity-1.2-2.2.noarch.rpm. This one gives me distance problems using the same adapter. Why would one version on one system give me the distance problems while the other version on another system not? > You mean: the KDE frontend does not work. > Try to start from command line: > python /usr/share/blueproximity/kproximity.py > > Send me the output. > langs: ['en_US', 'en'] Traceback (most recent call last): File "./kproximity.py", line 152, in <module> Kproximity_Ui.__dict__["_Kproximity_Ui__tr"]=trans TypeError: 'dictproxy' object does not support item assignment This is on OpenSuSE 10.2
Unfortunately, for SuSE 10.2 there is not up-to-date pybluez. I think, you compiled from the enclosed src.rpm. You may try to compile from the src.rpm of SuSE 10.3. The following error is a bug on SuSE: "TypeError: 'dictproxy' object does not support item assignment" Item assignment is a basic feature of python dictionaries. SuSE may use tuple, but it is a bug. The __dict__ is a dictionary not a tuple. I try to find out another solution. The problem is only the translation stuff... You need not it as: langs: ['en_US', 'en'].
Unfortunately, for SuSE 10.2 there is not up-to-date pybluez. I think, you compiled from the enclosed src.rpm. You may try to compile from the src.rpm of SuSE 10.3. The following error is a bug on SuSE: "TypeError: 'dictproxy' object does not support item assignment" Item assignment is a basic feature of python dictionaries. SuSE may use tuple, but it is a bug. The __dict__ is a dictionary not a tuple. I try to find out another solution. The problem is only the translation stuff... You need not it as: langs: ['en_US', 'en'].
You can delete the line 152 Kproximity_Ui.__dict__["_Kproximity_Ui__tr"]=trans in the file /usr/share/blueproximity/kproximity.py. (Translation will be disabled for the GUI.)
I've recently upgraded to openSuSE 10.3 and installed your app again with no problems. It runs but I'm unable to find my phone anymore. However, the adapter continuously sends out pairing requests. Any idea how I can turn this off. It seems to be something that pops up only after I install blueproximity after uninstalling it.
You can ignore the previous comment about the constant pairing requests. Turns out to have been a process that I didn't die. I now have kproximity.py running relatively smoothly. However, I do have one concern. I've selected kscreensaver as my screensaver of choice but it doesn't fire off. The key goes red and the status indicates that my phone is "gone" but still, no screen locking. Do I have to configure it in some special way that isn't the same as gnome-screensaver or xscreensaver?
Ok, you can ignore that last one too. I guess I need to have xscreensaver running in order for KScreensaver to work. I'm all good. I promise I'm not insane
Could you post a link to tar.gz file? I'm on Gentoo and would like to try your application as well. DK
Convert it to tar.gz with alien. It does not contain any architecture/distribution specific part. You need not compile anything. You may link the .desktop file if the K-menu fails to display Blueproximity.
1. The GTK frontend cannot be integrated into KDE. The systemtray policy is different. 2. The KScreenSaver works completely differently then the gnome-screensaver. 3. The GTK version is compatible only with unstable GTK versions. It does not work on debian ETCH. 4. The documentation with the instructions will be different. How can you use a gnome systemtray applet on KDE to setup your devices? 5. I am not an expert in GTK programming, but I understand KDE. I think, Lars Friedrichs is not an expert in QT/KDE programming, but he is an expert in Gnome 6. The fromtend is only a small part of the application. The API is the same for the two versions.
well said :-) Although I might change some bits in my frontend to a) make it KDE-friendlier (it will always stay a GNOMEized GTK+ based version) b) may add support for stable pyGTK versions once I have more time left. I'm doing my semester's test atm and my wife's expecting this month so I am quite busy... Bye Lars
What's the simplest Bluetooth device that could be used in conjuction with this application?
You need a linux compatible bluetooth device and a compatible mobile phone with bluetooth feature.
My bluetooth headset works well too
i've tested your applications with positive feedback, from dpkg-tools-fe to PyWireless wich is the main difference between this app and the new kbluetooth with bluelock inside? tnx for answer
I only know this application: "Bluelock is a small bash-scipt. Bluelock is written to check if a bluetooth device of you is available, if it's not it will lock your computer. So the idea is that if you walk away from your computer and you forget often to lock it, this script will do. But on the other hand if you stay near your computer, it won't lock, because you are close to him :) To start it, you need to run the command: bluelockd" It cannot be configured at all. Has the new KBluetoothD got also this feature? I don't know it. Could you send me a screenshot?
Hmm, this is probably the best example I've seen of the problem with linux. Can't beleive you went to the trouble of re coding the GUI just to match KDE! Nice work though, if I used KDE Im sure Id be happy :)
sheesh, you re-do it in QT and they complain about re-inventing the wheel...you don't, and they complain how "Linux has no consistent look and feel" from GTK apps in KDE/QT apps in GNOME. Kinda makes you pine for Microsoft's "this is what you will use and this is what your apps will look like, have a nice day" philosophy, huh? :P