Arch Linux

So you think that it is critical for you means that it is the upper most critical thing to fix in the whole distro? Yeah right.

Look at your error message. You get an error on "Could not open display", and an error on top of it that X refused your connection. Do you really think this is an archlinux bug instead of a stupid user bug?

It is Arch Linux's bug. I can open *ANY OTHER* X11 application application from a terminal, pygtk or not. The only one dying with this error is bluepin. Besides, look at the error more closely. It says "/home/jan/abs/pygtk....". This is NOT my home directory, it is YOUR home directory. Would you mind telling me how YOUR home folder appears on the error message of my installed application? It shouldn't be appearing here.

I can agree, it is always a user error. More specifically, seems to be yours this time. :P

It's definitely a bluepin error. Have you seen the code they use?
They redefine your $DISPLAY and $XAUTHORITY to values that are not right, the $XAUTHORITY gets lost in the initialization causing the error.

BTW: Bluepin is not system category and this bug is not critical.

>and this bug is not critical.

In my point of view, it is. I would not even start thinking Apple start selling Mac OS X Tiger without having their Bluetooth Pairing code working. That would be a "hard stop" for their release, because without having the pin number, you can't pair two Bluetooth devices. Sure, after googling away for a while I found that I could change the pin number on /etc/bluetooth/pin with a text editor, but the user of a 2005's modern operating system should NOT have to do this. That's why the GUI app of Bluepin was created in the first place. And most people don't want to start editing weird files on /etc (or loading manually drivers, as I had to do earlier today because Hotplug only does half the job) just to be able to talk to their Phone to download some pictures or exchange some files with another computer. These are the places where Linux needs to better itself: in the convenience of the user for everyday uses. I use Bluetooth for several uses, and so it's pretty critical to me. Maybe not critical to the system itself, but definetely critical in the overall impression of the system.

Hi Eugenia,

I don't use bluez-utils, but here is a workaround for the DISPLAY bug.

# xhost +localhost

After that, running bluepin would only output "ERR". Apparently it wants two arguments passed along with it.

syntax: bluepin <out|in> <addr>


It's a simple script, by the looks of it. I'm not really sure it does anything useful actually. Care to enlighten me?

It sets up the pin number so another bluetooth device can use that pin number to communicate with the linux bluetooth machine (e.g. another laptop, or many other bluetooth-enabled machines after you configure NAT-over-Bluetooth).