Am Samstag, den 19.12.2009, 00:43 +0100 schrieb Andrea Veri: > Looking at the informations you just provide, the issue seems to be in bluez > itself, > I think that you should forward the results of your tests directly upstream > so we can > start having an idea of what's going on.
Update: Today I tried with bluez 4.42-2~bpo50+1 (the version which worked before) from backports and exact the same happened. So maybe it's not a regression in bluez, but indeed in gnome-bluetooth. However, from the changelog I cannot see any significant change between 2.28.3-1 and 2.28.3-2. Or maybe even my Bluetooth-stick is broken... :/ Cheers, Fabian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
