This message was deleted.
# citrix-vad
s
This message was deleted.
r
@Marco Hofmann Which client do you have? There is a known issue that was fixed in CU2 with certain Ubuntu clients: • The ctxgfx process can cause high CPU usage on Windows VDA version 2112 when using Ubuntu 18 clients with dual monitors. [CVADHELP-19937]
m
Dell Wyse ThinOS & Windows 10
r
ThinOS might be Ubuntu based.. Can you share some more details what the users are doing? Also, which graphics policy do you have enabled?
m
No, ThinOS is not Linux afaik. No, not yet. I only get info once it's too late. The users complain about bad performance and the customer reboots the VDA. I can check the graphics policies.
r
Thanks. I would recommend opening a support case and upload a CDF trace of the session. This helps us figuring out what is going on here
m
These are all the settings, I tend to stick strictly to the Citrix defaults regarding anything graphics.
r
Do you see anything in the Event Viewer?
(P.S: You do not have to disable HW Encoding if you don't have a GPU. The policy does nothing when you do not have a GPU in your VDA)
m
I asked the customer, the causative user were always ThinOS users, I'm trying to get more info.
r
I just looked at the Dell website, but ThinOS is definitely Linux based
Which version are they running?
m
Before grabbing CDF traces a upgrade to 2203.2000 would make sense.
Yeah I would recommend testing with 2203 CU2 as well. Do they have Dual Monitor?
If so, you could test by running it on just 1 monitor
m
Your link proves the opposite, that it's not linux.
r
In that list you can see stuff like XOrg, which is Linux
m
No, it's freeBSD 12.0, that's not Linux.
Like NetScaler is not Linux, but BSD.
But we're missing the point.
r
Yeah let's see if CU2 fixes it, also like I said if they have Multi Monitor try running with one.
m
I get the info.
👍 1
t
You can try to kill ctxgfx.exe and see if the performance recovers. Though that's not a solution but maybe a workaround until fixed. I had an environment were we had to kill the process twice a day in order to keep performance, but that was long ago and single session OS.
m
Last time I observed the issue the EXE was un-killable.
Only a Force Reboot fixed the issue. Completly forgot to mention this.
p
@Rody Kossen - is there a publicly accessible link to these "known issues" outside waiting for a new release to casually mention them in the release notes?
p
Those are release notes. “Known issues” are updated infrequently and usually don’t actually contain all the known issues until some time later. No I’m asking about direct access to the [CVADHELP] files. Oftentimes someone with internal access will say “yeah that issue you’ve been scrambling to fix is CVADHELP blah” but until Citrix link that to a release note or to some KB it’s unfindable.
r
@Paul Brown The CVADHELP articles are internal and cannot be shared unfortunately. We try to keep the Known issues up to date, but I'll bring the feedback back to the team. Do you have an example where you ran into something that was known but not in the known-issue section?
p
Plenty. Maybe my memory is playing tricks on me but back in the day I recall there was a central repository where you could look up issues. Now it’s all scattered about into “known issues” notes in the documentation for each specific piece of software, vda, profile mgmt, wem, pvs, etc etc. There also used to be a semi decent compatibility doc that talked about MS patches, highlighting issues.
r
@Paul Brown we have one central page for Interop compatibility and known issues for that: https://support.citrix.com/article/CTX276640/citrix-interoperability-validation
m
@Rody Kossen Happend again today, customer gathered info. I was surprised. The session where the EXE had 25% and ruining the UX was from a Windows 10 PC with 1 Monitor.