VMware Horizon Community
xzpluszone
Contributor
Contributor

linux horizon client Segmentation Fault

 
picture_599.png

 

hello.
I installed the recently patched VMware-Horizon-Client-2203-8.5.0-19586897.x64.bundle.
Normal CLI execution is fine, but if you execute a command through an external application, a segmentation fault occurs.

The previously installed VMware-Horizon-Client-2012-8.1.0-17349998.x64.bundle works fine with the CLI as well.

I've tried comparing the differences between the two in binary, but it doesn't make any difference.
I have a problem with VMware-Horizon-Client-2203-8.5.0
I had libgthread-2.0.so.0 => /lib/x86_64-linux-gnu/libgthread-2.0.so.0 additionally.

My guess is... a library error? or permission error?


thank you.

 

Error Version: VMware-Horizon-Client-2203-8.5.0-19586897.x64.bundle

Test Environment: Debian GNU/Linux 11 \n \l and Linux Mint 19 Tara \n \l

Kernel: 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

0 Kudos
2 Replies
xzpluszone
Contributor
Contributor

as additional information

Check it with dmesg.

The information appears as follows.

May 23 15:02:33 gooroom kernel: [4580804.344405] vmware-view[439645]: segfault at 0 ip 00007f548785a695 sp 00007ffe4b2801f0 error 4 in libnss_compat-2.31.so[7f5487858000+6000]
May 23 15:02:33 gooroom kernel: [4580804.344433] Code: 04 24 48 89 ef 64 48 8b 04 25 28 00 00 00 48 89 84 24 e8 00 00 00 31 c0 f3 48 ab 48 b8 00 00 01 00 01 00 00 00 48 89 44 24 20 <41> 0f b6 04 24 83 e8 2b a8 fd 74 68 48 83 3d 37 59 00 00 00 49 89

 

0 Kudos
xzpluszone
Contributor
Contributor

self answer.

Debugging just before the segfault, /proc/self/loginuid was defined as -1.

openat(AT_FDCWD, "/proc/self/loginuid", O_RDONLY) = 21
read(21, "4294967295", 12) = 10

Normal operation should be the corresponding execution uid.

When I forcibly change the loginuid, it works normally.

0 Kudos