Hi Vincent,
Your bug is likely different from the original poster's bug. As I
usually not deal with RAOP issues myself: if you have time to contact
upstream directly (the pulseaudio-disc...@lists.freedesktop.org list is
recommended) that would probably be your best odds of getting your bug
fixed.
For the record, digging a bit and running 'pulseaudio -vv', I get
(excerpt):
D: [pulseaudio] module-raop-discover.c: Found RAOP: Freebox Server
D: [pulseaudio] module-raop-discover.c: Found key: 'txtvers' with value: '1'
D: [pulseaudio] module-raop-discover.c: Found key: 'vs' with value: '110.63'
@David: I've got an oneiric setup where I found the error message
introduced by your patch.
I get it when trying to connect to an AitTunes Remote Audio server on my
LAN.
Did you get more information about what is causing this behavior ? Your
patch added a /* FIXME */ which I'd love to disappear ;
This bug was fixed in the package pulseaudio - 1:0.99.3-0ubuntu4
---
pulseaudio (1:0.99.3-0ubuntu4) oneiric; urgency=low
* Fix crash in jack detection patches (LP: #845468)
* Fix crash when reading volume when sink/source is unlinked (LP: #841968)
* Fix crash in RAOP (LP: #84528
** Branch linked: lp:~ubuntu-audio-dev/pulseaudio/ubuntu.oneiric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/845286
Title:
[raop] pulseaudio crashed with SIGABRT in __kernel_vsyscall()
To manage
The attachment "0001-RAOP-Don-t-crash-if-fd-is-not-open-when-trying-to-
cl.patch" of this bug report has been identified as being a patch. The
ubuntu-reviewers team has been subscribed to the bug report so that they
can review the patch. In the event that this is in fact not a patch you
can resol
** Patch added:
"0001-RAOP-Don-t-crash-if-fd-is-not-open-when-trying-to-cl.patch"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/845286/+attachment/2390439/+files/0001-RAOP-Don-t-crash-if-fd-is-not-open-when-trying-to-cl.patch
--
You received this bug notification because you are
Thanks for your bug report! I've made a patch out that hopefully will
fix this problem. I'm attaching it here and I've sent it to PulseAudio
upstream for discussion.
** Changed in: pulseaudio (Ubuntu)
Status: New => In Progress
** Changed in: pulseaudio (Ubuntu)
Assignee: (unassigned)
** Summary changed:
- pulseaudio crashed with SIGABRT in __kernel_vsyscall()
+ [raop] pulseaudio crashed with SIGABRT in __kernel_vsyscall()
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
