play fails on remote pulseaudio server

Bug #352523 reported by Pasi Savolainen
6
Affects Status Importance Assigned to Milestone
banshee (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: banshee

When using remote pulseaudio server, playing fails.
output in console is:

---
[Debug 19:43:56.572] Player state change: Idle -> Loading
[Debug 19:43:56.702] Player state change: Loading -> Loaded
[Debug 19:43:56.724] (libbanshee:player) bp_stop: setting state to GST_STATE_NULL
[Debug 19:43:56.724] Player state change: Loaded -> Idle
[Error 19:43:56.727] GStreamer resource error: Failed
[Debug 19:43:56.789] Creating Pango.Layout, configuring Cairo.Context
[Debug 19:43:56.789] Creating Pango.Layout, configuring Cairo.Context
---

When redirecting to local PA server, playing works just fine. Same PA server outputs nicely xine & rhythmbox -originated audio, so it should be ok.

Here is "pulseaudio -vv" output from time when playing is attempted:
---
I: socket-server.c: TCP connection accepted by tcpwrap.
I: client.c: Created 4 "Native client (TCP/IP client from 192.168.1.128:34212)"
I: client.c: Client 4 changed name from "Native client (TCP/IP client from 192.168.1.128:34212)" to "Banshee"
I: module-volume-restore.c: Restoring sink for <pulsecore/protocol-native.c$Banshee>
I: module-volume-restore.c: Restoring volume for <pulsecore/protocol-native.c$Banshee>
D: module-suspend-on-idle.c: Sink alsa_output.pci_1274_1371_sound_card_0_alsa_playback_0 becomes busy.
I: resampler.c: Forcing resampler 'copy', because of fixed, identical sample rates.
I: resampler.c: Using resampler 'copy'
I: resampler.c: Using float32le as working format.
I: sink-input.c: Created input 3 "Playback Stream" on alsa_output.pci_1274_1371_sound_card_0_alsa_playback_0 with sample spec float32le 2ch 44100Hz and channel map front-left,front-right
D: memblock.c: Memory block too large for pool: 17640 > 16376
D: memblockq.c: memblockq requested: maxlength=141120, tlength=70560, base=8, prebuf=70560, minreq=3528
D: memblockq.c: memblockq sanitized: maxlength=141120, tlength=70560, base=8, prebuf=70560, minreq=8
D: module-suspend-on-idle.c: Sink alsa_output.pci_1274_1371_sound_card_0_alsa_playback_0 becomes busy.
D: module-suspend-on-idle.c: Sink alsa_output.pci_1274_1371_sound_card_0_alsa_playback_0 becomes idle.
D: module-suspend-on-idle.c: Sink alsa_output.pci_1274_1371_sound_card_0_alsa_playback_0 becomes idle.
I: sink-input.c: Freeing output 3 "'Whiskey in the Jar' by 'Metallica'"
I: client.c: Freed 4 "Banshee"
I: protocol-native.c: connection died.
---

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/lib/banshee-1/Banshee.exe
InterpreterPath: /usr/bin/mono
NonfreeKernelModules: nvidia
Package: banshee 1.4.3-3ubuntu2
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: banshee
Uname: Linux 2.6.28-11-generic x86_64

Revision history for this message
Pasi Savolainen (pasi.savolainen) wrote :
Revision history for this message
Andrew Conkling (andrewski) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information. Would you please add the information requested from https://wiki.ubuntu.com/DebuggingSoundProblems#Reporting%20Sound%20Bugs as separate attachments? Thanks in advance.

Changed in banshee:
status: New → Incomplete
Revision history for this message
Pasi Savolainen (pasi.savolainen) wrote :

Alsa-info.sh output.

This doesn't look like it contains many pulseaudio related things though.

Changed in banshee:
status: Incomplete → New
Revision history for this message
Neil Munro (neilmunro-deactivatedaccount) wrote :

Can you please install and test the 1.5 version from the Banshee PPA if nothing else to confirm it still exists in the current development version.

Thanks for taking the time to report this bug and for helping to make Ubuntu better.

Changed in banshee (Ubuntu):
status: New → Incomplete
Revision history for this message
Monkey (monkey-libre) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in banshee (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.