chenyu_vmware's Posts

Hi  konhuynh, From the collected command outputs, looks to me, your desktop environment at this vm is abnormal. You are using the gnome desktop, right? Could you please share how did you install/modify your desktop environment packages? And what's Redhat7.9 distribution you are using? I prefer you to install Redhat7.9 Enterprise workstation, which has default gnome-classic desktop environment to have a try.  The following are my Redhat7.9 desktop environment output at Terminal. [vmuser@redhat79 ~]$ env |grep DESKTOP IMSETTINGS_INTEGRATE_DESKTOP=yes DESKTOP_SESSION=gnome-classic GNOME_DESKTOP_SESSION_ID=this-is-deprecated XDG_SESSION_DESKTOP=gnome-classic XDG_CURRENT_DESKTOP=GNOME-Classic:GNOME

Hello, Where are you to execute command "pax11publish -d", and with which user? Please login with Horizon Client first, then open one Terminal, at there run this command. Also, please run commands "env", "pactl info", "ps -aux" and collect the output, thanks.

Hello, Where are you run command "pax11publish -d", and with which user to run? It shall be run at Terminal window with login user after you login with Horizon client. If possible, besides "pax11publish -d", please run commands "pactl info", "env", "ps -aux", and print the output here. thanks.  

Could you please have a try to use Linux agent 2209 build, to see whether sso can auto login. As we re-design the sso logic at build 2209. Thanks. If sso still can't auto login with Linux agent 2209 build, please open one PR and attach the dct logs for Engineer to analysis, thanks.

Please request VMWare Support Engineer to open PR to dev team, for next follow up. Note that please attach both connection server and agent log files at PR. As it need broker team's help to analysis the root cause. Thanks.

Thanks for your additional information. Now I understood your faced problem. The jms connection is broken between broker and Linux agent after broker reboot, then you can't login RDS desktop or App. But whether it's one problem, I will try to reproduce it in my env and ask broker team to confirm whether it is expected, will Cc you. Even if this problem can't be fixed finally, maybe I have one alterative way for you to make your RDS desktop or app work, but it's one totally another solution.

Use the fqdn is also fine. Can I understand your RDS desktop or App never works normally after your unmanaged-mode installation? What's status of your vm at "Registered Machines" of broker Admin UI? Or could you please send your viewagent-debug.log and /etc/vmware/viewagent-machine.cfg file to chenyu@vmware.com, I would like to take a look at log file first. thanks.

Hi, Can I understand your problem is "with your unmanaged mode installation, some days later, your agent is no longer reachable"? That's mean, your RDS desktop and app can be used in normal at first, but some days later, it can't work. If that's case, please first check farm/pool vm status at broker UI, to make sure it's in available status. If that's true, then need Linux agent dct log for further checking. BTW, the unmanaged mode installation parameter is similar like "./install_viewagent.sh -A yes -M no -b <broker_ipaddress> -u <username> -p <password> -d <domain_postfix> -n <hostname_fqdn> --multiple-session" After your re-register vm (or reinstall Linux agent), you need re-select vm at farm or create one new farm for your pool. thanks.    

Hi Perttu, First, thanks a lot for your effort and finding. To solve this problem, two possible ways: 1. If customer can accept to use vmware customized libgnome-shell.so, just replace that library back will make SSO works. 2. If customer would like to use gnome-shell of version 3.28.4-0ubuntu18.04.7, they need  reinstall horizon agent with "-G yes", to let horizon agent use the default gnome-shell library provided by ubuntu. Otherwise, it needs to use vmware customized version to take SSO function effective. Any problem, please let me help you, thanks. Thanks, Yu    

Please execute "dpkg-reconfigure gdm3" again, then re-install Linux viewagent, then update /usr/share/applications/org.gnome.Shell.desktop as KB required, then reboot, and have a try. If it still does not work, could you please paste the content here for org.gnome.Shell.desktop? Thanks.

Hi, The thing looks normal now, as the "native" file is created. Perform one logout, and connect to desktop, neither audio out or audio in works, right? Do you install viewagent with option "-a yes"? If logout does not work, please try to reboot vm, and do one connection, to see the result. If still not working, Please run ls -la for each subfolder for server path: # pax11publish -d: to get the server path # ls -la /run/user/ # ls -la /run/user/1001/ #ls -la /run/user/1001/.vmwblastaudio:100/

Please try to edit /usr/lib/vmware/viewagent/bin/MonitorAudio.sh with root. Search line: if version_ge "${DISTRO_RELEASE}" "8.3"; then Then update "8.3" to "8.2", logout and connect to desktop again. If it's lucky, audio shall be able to work now. If it does not work, please continue to run follwing commands and collect output: # ls -la <server_string_path> # sudo /usr/lib/vmware/viewagent/bin/MonitorAudio.sh

Don't need run command start-pulseaudio-x11 any more. Please run the following command in the terminal after you connect to desktop and supply the output, thanks.   # sudo /usr/lib/vmware/viewagent/bin/MonitorAudio.sh

Hi, Could you install Linux agent again after yum install pulseaudio-module-x11 package, and to see whether it's ok. If it still does not work, please help to re-run pax11publish command, and run "ls -la <each_server_path>", I saw  you only run "ls -a" command, thanks a lot.

Hi, Thanks for the feedback. Could you please try below things? thanks. 1. Disable the selinux by the command "# setenforce 0", and try again. 2. If step 1 does not work, try to run follow command, and collect output # /usr/bin/start-pulseaudio-x11 # pax11publish -d 3. Collect Linux agent log file by command "# /usr/lib/vmware/viewagent/bin/dct-debug.sh"

Could you please run below commands and collect command output at connected desktop terminal: # pax11publish -d # pactl info # ls -l <Each_subpath_at_Server_string> (Server string can be seen at output of pax11publish -d command, like ls -l /run/user/1002, ls -l /run/user/1002/.vmwblastaudio:101, ls -l /run/user/1002/.vmwblastaudio:101/native)