after update: A subprocess returned with an error

Thank you for taking your time to report this.

For using stream2ip with an Airport Express (1st generation) we need the following prerequisites:

1. `pulseaudio-module-raop' was installed.
2. The Airport Express was set up correctly (from Windows or OSX) and is present in the network.
3. The correct IP to the Airport Express was given.

In case you did not mean to use an Airport Express device please run the preferences program again with

    stream2ip --setup

to choose your preferred streaming solution. Also make sure that the option line for streams is correct (`asdf@ip' will not work for DLNA live. Try to re-discover your DLNA renderers using the looking glass next to the settings line). Save these settings with OK. Stream2ip will then use these settings on next run.

Alternatively we can reset all settings by deleting ~/.config/stream2ip/s2ip.cfg.

In case your issues can not be resolved by this please report here.

Ok, after running stream2ip --setup I changed the configuration to dlna-live. Unfortenately the package pulseaudio-dlna didn't install directly out of stream2ip because its not included in the sources or your ppa. After installing from ppa:qos/
pulseaudio-dlna i tried to start stream2ip....

$ stream2ip -v

(stream2ip.py:27899): Gtk-CRITICAL **: gtk_widget_grab_default: assertion 'gtk_widget_get_can_default (widget)' failed
<W> Python mutagen module not available
 [STREAM2IP] 2015-05-28:11:27:42>> *** Starting stream2ip 1.1.2 ('Ubuntu', '14.04', 'trusty') ***
 [STREAM2IP] 2015-05-28:11:27:42>> Default audio sink: 1
 [STREAM2IP] 2015-05-28:11:27:42>> We are using these settings:
 [STREAM2IP] 2015-05-28:11:27:42>> ['3', 'N', 'Auto', '/path/music', 'device@ip', '', 'Preferences to set up streaming', 'N', 'Y', 'N', 'Y', 'N', '', '6', '0', 'admin', 'hackme', 'N', 'Y']
 [STREAM2IP] 2015-05-28:11:27:42>> <I> DLNA live using device@ip to connect
 [STREAM2IP] 2015-05-28:11:27:43>> <I> Connecting pulseaudio-dlna with device@ip
 [STREAM2IP] 2015-05-28:11:27:43>> Pulseaudio-dlna PID:27915
 [STREAM2IP] 2015-05-28:11:27:43>> Waiting for sink to be established
Using localhost: ip:8080
INFO:urllib3.connectionpool:Starting new HTTP connection (1): ip
INFO:urllib3.connectionpool:Starting new HTTP connection (1): ip
INFO:urllib3.connectionpool:Starting new HTTP connection (1): ip
INFO:urllib3.connectionpool:Starting new HTTP connection (1): ip
INFO:urllib3.connectionpool:Starting new HTTP connection (1): ip
INFO:urllib3.connectionpool:Starting new HTTP connection (1): ip
INFO:root:Discovery complete.
INFO:root:Found devices:
<CoinedUpnpMediaRenderer name="device" short_name="device" state="idle">
INFO:root:You can now use your upnp devices!
Fehlgeschlagen: Modulinitialisierung fehlgeschlagen
ERROR:root:PulseAudio seems not to be running or pulseaudio dbus module could not be loaded.
 [STREAM2IP] 2015-05-28:11:27:58>> <E>Switching to DLNA-sink failed
 [STREAM2IP] 2015-05-28:11:27:58>> Connecting time loop: 6 seconds
 [STREAM2IP] 2015-05-28:11:28:04>> <I> DLNA live using device@ip to connect
 [STREAM2IP] 2015-05-28:11:28:05>> <I> Connecting pulseaudio-dlna with device@ip
 [STREAM2IP] 2015-05-28:11:28:05>> Pulseaudio-dlna PID:27947
 [STREAM2IP] 2015-05-28:11:28:05>> Waiting for sink to be established
Using localhost: ip:8080
INFO:urllib3.connectionpool:Starting new HTTP connection (1): ip
INFO:urllib3.connectionpool:Starting new HTTP connection (1): ip
INFO:urllib3.connectionpool:Starting new HTTP connection (1): ip
INFO:urllib3.connectionpool:Starting new HTTP connection (1): ip
INFO:urllib3.connectionpool:Starting new HTTP connection (1): ip
INFO:urllib3.connectionpool:Starting new HTTP connection (1): ip
INFO:root:Discovery complete.
INFO:root:Found devices:
<CoinedUpnpMediaRenderer name="device" short_name="device" state="idle">
INFO:root:You can now use your upnp devices!
Fehlgeschlagen: Modulinitialisierung fehlgeschlagen
ERROR:root:PulseAudio seems not to be running or pulseaudio dbus module could not be loaded.
^Z
[1]+ Angehalten stream2ip -v

Thanks for your help!

yeah, we did not want to add a ppa source programmatically because of potential security issues from this, and to make a custom installation possible if desired.

Nevertheless you managed to install it via the ppa - that's great!

Before experimenting further with stream2ip let me suggest you just run `pulseaudio-dlna' in a terminal to watch for possible errors.

By running pulseaudio-dlna it should load `pulseaudio module-dbus-protocol'. We should not unload this module or killing pulseaudio at runtime. To check for this we can issue

    paclt list short modules | grep dbus

while or after running pulseaudio-dlna. If it was not present we can manually load this module prior to starting pulseaudio-dlna with

    pactl load-module module-dbus-protocol

Also watch for error while doing so. You're welcome to post them here so we can try to debug your issue.

Note that at least one DLNA renderer needs to be present (and powered on) in your LAN, pulseaudio needs to be running, and the module-dbus-protocol needs to be loaded to provide an output sink to this DLNA renderer. It will then be shown and be selectable in `Sound Settings...' from the top panel.

I am pretty confident that once you got pulseaudio-dlna running you will be able to use stream2ip to switch and auto-connect to a DLNA renderer as expected.

Please also note that stream2ip needs both, a definite name (e.g. "Bubble UPnP") , the @-sign, and an IP (e.g. 192.168.148.50) of your specific device to be able to connect.

I do hope for success!

it seemed that the module is running and because of this its not possible to start it...How can I stop it, is it necessary or can stream2ip take it by self? I'm not well known in such things, thank you for motivating me...

One renderer is running and should be able to get found...
<CoinedUpnpMediaRenderer name="device" short_name="device" state="idle"> #internal ip/name of Device replaced for privacy

$ pulseaudio-dlna
Using localhost: ip:8080
INFO:urllib3.connectionpool:Starting new HTTP connection (1): ip
INFO:urllib3.connectionpool:Starting new HTTP connection (1): ip
INFO:urllib3.connectionpool:Starting new HTTP connection (1): ip
INFO:urllib3.connectionpool:Starting new HTTP connection (1): ip
INFO:urllib3.connectionpool:Starting new HTTP connection (1): ip
INFO:urllib3.connectionpool:Starting new HTTP connection (1): ip
INFO:root:Discovery complete.
INFO:root:Found devices:
<CoinedUpnpMediaRenderer name="device" short_name="device" state="idle">
INFO:root:You can now use your upnp devices!
Fehlgeschlagen: Modulinitialisierung fehlgeschlagen
ERROR:root:PulseAudio seems not to be running or pulseaudio dbus module could not be loaded.

$ pactl list short modules | grep dbus
25 module-dbus-protocol

The module only loads in case it is not yet present. People could e.g. load it by default.pa. So we do not have to remove it before running.

Your error reminds me of a recent bug report against pulseaudio-dlna:

https://github.com/masmu/pulseaudio-dlna/issues/48#issuecomment-104648800

when the solution was to install lame (which was not yet present on that system).

    sudo apt-get install lame

It's worth a try. Anyway the issue may also come from the pulseaudio side, or from pulseaudio-dlna. Running

    pulseaudio-dlna --debug

may give further insights.

Lame is still installed, this wasn't the problem. I'm not shure if I want to search for bugs in parts of pulseaudio...

Thanks for your help

Did `pulseaudio-dlna --debug' show anything more specific as to why a pulseaudio module could not be loaded? At present it is not clear which module could not be loaded, and more importantly why.

You may also ask at the pulseaudio-dlna bug track: https://github.com/masmu/pulseaudio-dlna/issues