This bug is still outstanding in Feisty, for bluetooth:// URIs at least. Is there something we can do to get it sorted out?
This bug is still outstanding in Feisty, for bluetooth:// URIs at least. Is there something we can do to get it sorted out?