X2Go Bug report logs - #535
PyHoca-GUI: Windows: "The X2Go PulseAudio system could not be started."

Reply or subscribe to this bug.

Toggle useless messages

Message #5 received at submit@bugs.x2go.org (full text, mbox, reply):

From: Michael DePaulo <mikedep333@gmail.com>

To: submit@bugs.x2go.org

Subject: PyHoca-GUI: Windows: "The X2Go PulseAudio system could not be started."

Date: Sun, 6 Jul 2014 19:36:35 -0400

Package: pyhoca-gui
Version: 0.4.0.8
Version: 0.5.0.0-preview

On Windows, whenever I launch PyHoca-GUI a 2nd time (or 3rd time,
etc),I get the error bubble/notification:
The X2Go PulseAudio system could not be started.

The pulseaudio.exe process is indeed not running, and sound does not work.

The simple workaround is to delete the folder:
%USERPROFILE%\.pulse

Or more specifically, delete the only file underneath it:
%USERPROFILE%\.pulse\%COMPUTERNAME%-runtime\pid

You'll have to delete that file after everytime you run PyHoca-GUI.

X2Go Client is not affected by this problem.

note, on Windows:
pyhoca-gui 0.4.0.8 has PulseAudio 1.1
pyhoca-gui 0.5.0.0 has PulseAudio 5.0

Message #12 received at 535@bugs.x2go.org (full text, mbox, reply):

From: Michael DePaulo <mikedep333@gmail.com>

To: 535@bugs.x2go.org

Subject: More test results

Date: Sun, 6 Jul 2014 21:06:58 -0400

For some reason, this affects my desktop, but not my XP VM.

Specifically, on the XP VM, the pid file is left behind. But it does
not cause PyHoca-GUI to display the message. (Nor does it prevent
PyHoca-GUI from launching pulseaudio.exe.)

Desktop (executor):
Windows 8.1 64-bit with update 1
Multiple sound adapters. Adapter listed below is the current default:
Audio driver name: SB Recon3D PCIe
Audio driver provider: CREATIVE
Audio driver date: 7/30/2013
Audio driver version: 6.0.101.57
Audio driver installer: SBRP_CD_LD_1_01_26.exe
Audio driver date (according to website): 29 Jan 14
Accessed locally

XP VM (mothership-xp):
Windows XP 32-bit SP3
Running on Fedora 20 kvm/libvirt
kvm/libvirt set to provide "ac97" audio
Audio driver name: Intel(r) 82801AA AC'97 Audio Controller
Audio driver provider: Microsoft
Audio driver date: 7/1/2001
Driver Version: 5.1.2535.0
Accessed over SPICE with Virt-Viewer 0.6.0 64-bit from said desktop.

Message #17 received at 535@bugs.x2go.org (full text, mbox, reply):

From: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>

To: Michael DePaulo <mikedep333@gmail.com>, 535@bugs.x2go.org

Subject: Re: [X2Go-Dev] Bug#535: More test results

Date: Mon, 07 Jul 2014 09:53:37 +0000

[Message part 1 (text/plain, inline)]

Hi Mike#2,

On  Mo 07 Jul 2014 03:06:58 CEST, Michael DePaulo wrote:

> For some reason, this affects my desktop, but not my XP VM.
>
> Specifically, on the XP VM, the pid file is left behind. But it does
> not cause PyHoca-GUI to display the message. (Nor does it prevent
> PyHoca-GUI from launching pulseaudio.exe.)
>
> Desktop (executor):
> Windows 8.1 64-bit with update 1
> Multiple sound adapters. Adapter listed below is the current default:
> Audio driver name: SB Recon3D PCIe
> Audio driver provider: CREATIVE
> Audio driver date: 7/30/2013
> Audio driver version: 6.0.101.57
> Audio driver installer: SBRP_CD_LD_1_01_26.exe
> Audio driver date (according to website): 29 Jan 14
> Accessed locally
>
> XP VM (mothership-xp):
> Windows XP 32-bit SP3
> Running on Fedora 20 kvm/libvirt
> kvm/libvirt set to provide "ac97" audio
> Audio driver name: Intel(r) 82801AA AC'97 Audio Controller
> Audio driver provider: Microsoft
> Audio driver date: 7/1/2001
> Driver Version: 5.1.2535.0
> Accessed over SPICE with Virt-Viewer 0.6.0 64-bit from said desktop.

I know this "The pulseaudio system could not be started." message from  
Windows desktop sessions running as RDP sessions. As if pulseaudio  
chokes on the RDP audio backend. If I launch pyhoca-gui locally on  
those systems (sitting in front of $SCREEN, not via RDP), then the  
pulseaudio subsystem comes up correctly.

Mike
-- 

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb

[Message part 2 (application/pgp-signature, inline)]

Send a report that this bug log contains spam.