X2Go Bug report logs - #1189
High CPU usage for "Windows Audio Device Graph Isolation" (again)

Package: x2goclient; Maintainer for x2goclient is X2Go Developers <x2go-dev@lists.x2go.org>; Source for x2goclient is src:x2goclient.

Reported by: s.yu@protonmail.com

Date: Sat, 8 Jul 2017 15:10:02 UTC

Severity: normal

Found in version 4.1.0.0

Reply or subscribe to this bug.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to x2go-dev@lists.x2go.org, X2Go Developers <x2go-dev@lists.x2go.org>:
Bug#1189; Package x2goclient. (Sat, 08 Jul 2017 15:10:02 GMT) (full text, mbox, link).

Acknowledgement sent to s.yu@protonmail.com:
New Bug report received and forwarded. Copy sent to X2Go Developers <x2go-dev@lists.x2go.org>. (Sat, 08 Jul 2017 15:10:02 GMT) (full text, mbox, link).

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

Package: x2goclient
Version: 4.1.0.0

Hi,

I found that the bug reported in bug #425 [1] is occurring again with
the win32 build of v4.1.0.0.

As described in #425, the CPU usage of  "Windows Audio Device Graph
Isolation" becomes around 14% after x2goclient is started. The issue
could be solved by killing the pulseaudio.exe process.

There was no such problem in previous v4.0.5.2.

I am running Windows 10 64bit (1703).

[1]: https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=425

Eric

Send a report that this bug log contains spam.

X2Go Developers <owner@bugs.x2go.org>. Last modified: Sat Apr 20 09:57:40 2024; Machine Name: ymir.das-netzwerkteam.de

X2Go Bug tracking system

Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

X2Go Bug report logs - #1189 High CPU usage for "Windows Audio Device Graph Isolation" (again)

X2Go Bug report logs - #1189
High CPU usage for "Windows Audio Device Graph Isolation" (again)