On 11/26/2015 04:01 PM, Michael Biebl wrote:
> Am 26.11.2015 um 09:53 schrieb Mattia Belluco:
>> Package: systemd
>> Version: 228-2
>> Arch:amd64
>>
>> If bluetooth is disabled by soft rfkill (blueman applet) the status
>> survives reboot and sy
On 12/02/2015 09:53 PM, Michael Biebl wrote:
> Am 02.12.2015 um 20:30 schrieb Mattia Belluco:
>> On 11/26/2015 04:01 PM, Michael Biebl wrote:
>>> Am 26.11.2015 um 09:53 schrieb Mattia Belluco:
>>> I'm confused, why is this a bug in particular (you disabled bluetooth)
&
appears only if rfkill is
disabled and in fact if I issue:
rfkill unblock tpacpi_bluetooth_sw
the relevant directory appears and I can manually start the deamon with
systemctl start bluetooth.service
regards
Mattia Belluco
and wired.CheckPluggedIn() -- it is not verified because
of wired.CheckPluggedIn() returning 0 before settling to 1.
Mattia Belluco
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On 08/05/2014 12:17 PM, Michael Meskes wrote:
On Fri, Jul 25, 2014 at 06:26:38PM +0200, Mattia Belluco wrote:
With the lastest version I can no longer disable the integrated
touch pad on a dual tracking system such as Lenovo x220 nor lock the
screen with the screenlock button:
apparently both
:
Hi,
I installed bluez5 into unstable.
current pulseaudio needs bluez5. Could you check with bluze5?
NOTE: I confirmed that pulseaudio worked with bluez5.
Best regards,
Nobuhiro
2014-04-04 5:10 GMT+09:00 Mattia Belluco dewa...@ninthfloor.org:
Package: bluez
Version: 4.101-4.1
Arch: amd64
alternative way to achieve the same results.
Mattia Belluco
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
of Bluez, blueman does not have
to follow this in Debian.
maintainer of blueman is working about this.
I reassign this BTS to blueman.
Best regards,
Nobuhiro
2014-07-16 22:16 GMT+09:00 Mattia Belluco dewa...@ninthfloor.org:
package: bluez
version: 5.21-1
arch:amd64
As of last update I
on interface org.bluez.Manager
doesn't exist
I downgraded bluez to jessie's version and everything started to work again.
Mattia Belluco
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Hi all,
I feel like this bug is related to these two I reported:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743568
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743569
More specifically to make a bluetooth headset work in A2DP mode I had to
change settings in audio.conf:
Package: pulseaudio-module-bluetooth
Version: 4.0-6+b1
Arch: amd64
After much tinkering I found out one of the reasons my bluetooth audio
devs (A2DP and not) were not pairing was due to the module:
module-bluetooth-discover.so.
I use pulseaudio per-user and my default.pa reads:
###
Package: bluez
Version: 4.101-4.1
Arch: amd64
To make thing easier to use pulseaudio with bluez there should be more
comments on the config.
Specifically I suggest to change:
# SCO routing. Either PCM or HCI (in which case audio is routed to/from
ALSA)
# Defaults to HCI
To something :
#
12 matches
Mail list logo
