--
-- Forwarded message --
Date: Thu, 4 Aug 2016 21:04:05
From: tim
To: Jude DaShiell
Cc: supp...@sonargnulinux.com
Subject: Re: [Support] No sound after update?
I've fixed it! I had to downgrade libpulse, pulseaudio, pulseaudio-bluetooth,
pulseaudio-zeroconf, pulseaudio-li
--
-- Forwarded message --
Date: Thu, 4 Aug 2016 23:54:43
From: Jude DaShiell via Support
Reply-To: Jude DaShiell
To: tim
Cc: supp...@sonargnulinux.com
Subject: Re: [Support] No sound after update?
On archlinux, I don't get sound until after I log in even with everything se
On Thursday 04 August 2016 20:02:59 Felipe Sateler wrote:
> Out of curiosity, what distro is this?
Ubuntu 12.04 LTS with KDE4.
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
___
pulseaudio-discu
On 4 August 2016 at 13:49, Pali Rohár wrote:
> On Thursday 04 August 2016 19:35:57 Tanu Kaskinen wrote:
>> This may very well cause a regression for BlueZ 4, because I didn't
>> make the corresponding changes there. The code isn't identical with
>> BlueZ 5, and it would be a bit difficult for me t
On Thursday 04 August 2016 19:35:57 Tanu Kaskinen wrote:
> This may very well cause a regression for BlueZ 4, because I didn't
> make the corresponding changes there. The code isn't identical with
> BlueZ 5, and it would be a bit difficult for me to test with BlueZ 4.
> What do others think - shoul
pa_bluetooth_transport_put() assigns the transport to the device's
transports array, so the caller doesn't have to do that.
---
src/modules/bluetooth/backend-native.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/modules/bluetooth/backend-native.c
b/src/modules/bluetooth
The properties_received flag affects whether the device should be
considered valid, so let's update the valid flag after setting the
properties_received flag.
There's a call to device_update_valid() anyway later when setting
the device adapters, so this change isn't strictly necessary, but
this ma
module-card-restore should only restore the initial state of new
cards, but profile_available_changed_callback() changed the profile
whenever the saved profile became available. That caused interference
with module-bluetooth-policy, which also sets card profiles based on
the availability changes.
The CONNECTION_CHANGED hook is used to notify the discovery module
about new and removed devices. When a bluetooth device connects, the
hook used to be called immediately when the first profile connected.
That meant that only one profile was marked as available during the
card creation, other profi
The first three patches are small unrelated tidy-ups that I made while
working on the main patch. The unrelated patches are nevertheless
included in this series, because if they are not applied first, the
fourth patch might not apply cleanly.
The fourth patch delays bluetooth card creation until a
I was working on the bluetooth code, and I wanted to be sure that the
device couldn't be in an invalid state in pa_bluetooth_transport_put().
That made it a bit easier to reason about the code.
---
src/modules/bluetooth/backend-native.c | 3 +++
src/modules/bluetooth/backend-ofono.c | 3 +++
src/
On Thursday 04 August 2016 10:00:00 Felipe Sateler wrote:
> On 4 August 2016 at 06:59, Tanu Kaskinen wrote:
> > it doesn't make sense for module-card-restore to switch to a profile
> > when an alsa profile becomes available due to the user plugging
> > something in.
>
> Why doesn't it makes sense
On 4 August 2016 at 06:59, Tanu Kaskinen wrote:
> it doesn't make sense for module-card-restore to switch to a profile
> when an alsa profile becomes available due to the user plugging
> something in.
Why doesn't it makes sense? I think it makes a lot of sense. One of
the things I miss from KDE i
On Thursday 04 August 2016 14:59:59 Tanu Kaskinen wrote:
> On Thu, 2016-08-04 at 13:37 +0200, Pali Rohár wrote:
> > On Thursday 04 August 2016 13:59:33 Tanu Kaskinen wrote:
> > >
> > > I'd guess it's profile_available_changed_callback().
> >
> > Yes, that one. Will you prepare fix?
>
> Since the
On Thu, 2016-08-04 at 13:37 +0200, Pali Rohár wrote:
> On Thursday 04 August 2016 13:59:33 Tanu Kaskinen wrote:
> >
> > I'd guess it's profile_available_changed_callback().
>
> Yes, that one. Will you prepare fix?
Since the broken code is from me, I suppose it's only fair that I get
to fix it to
On Thursday 04 August 2016 13:59:33 Tanu Kaskinen wrote:
> I'd guess it's profile_available_changed_callback().
Yes, that one. Will you prepare fix?
--
Pali Rohár
pali.ro...@gmail.com
___
pulseaudio-discuss mailing list
pulseaudio-discuss@lists.freedes
On Thu, 2016-08-04 at 09:29 +0530, Arun Raghavan wrote:
> On Tue, 2 Aug 2016, at 12:50 AM, Pali Rohár wrote:
> >
> > When pa_card_set_profile is called with save=false then
> > module-card-restore
> > start fight with module-bluetooth-policy and every second is profile
> > changing between hsp and
On Thursday 04 August 2016 09:29:58 Arun Raghavan wrote:
> On Tue, 2 Aug 2016, at 12:50 AM, Pali Rohár wrote:
> > When pa_card_set_profile is called with save=false then
> > module-card-restore
> > start fight with module-bluetooth-policy and every second is profile
> > changing between hsp and a2d
18 matches
Mail list logo
