Comment 47 for bug 146145

Okay, I have used test devices as such:
* Desktop running Kubuntu Gutsy AMD64 without hack-fix (see earlier comment)
* Laptop running WinXP
* UMPC dual-booting Kubuntu Hardy Current and WinVista, as well as booting off USB stick to an older version of Hardy Live CD
* Mobile running Symbian (Nokia N95)

And I see behavior like this:
* Desktop can send to UMPC/KubuntuHC
* Laptop can send to UMPC/KubuntuHC
* Mobile can send to Desktop
* Mobile can send to Laptop
* UMPC/Kubuntu can send to mobile
* Mobile can send to UMPC/WinVista
* Mobile cannot send to Desktop (original bug in Gutsy)
* Mobile can send to UMPC/KubuntuLiveCD (bug was fixed?)
* Mobile cannot send to UMPC/KubuntuHC (bug has reappeared?)

So: from the above I theoretize that the Obex server itself is running and working properly, but there is something wrong that is specific to how this Nokia phone is sending the BT Push message. It appears that the original problem has been fully fixed at some point, but after that has been partially re-broken. I tested also running UMPC/KubuntuHC as root, so that personal settings are not a factor. This did not help - still could not send the file.

I am also using the N95 as a dial-up modem, but for these tests I commented out the entry in /etc/bluetooth/rfcomm.conf and removed the trusted device pairing. This did not affect test results either.

One more note: upon sending the file, UMPC reports that the phone has connected, and then immediately the phone says that sending failed, but then the KDE Bluetooth icon remains lit for a few more seconds.

Soo... a weird incident specific to myself somehow, or a partial regression?