[Bug 1073760] New: vmtoolsd process running as user aborts with segfault
http://bugzilla.opensuse.org/show_bug.cgi?id=1073760 Bug ID: 1073760 Summary: vmtoolsd process running as user aborts with segfault Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs@suse.de Reporter: ron163264@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- At startup, the vmtoolsd process running as the user (option -n vmusr) aborts with a segfault. From journal: kernel: vmtoolsd[2650]: segfault at f0 ip 00007fb61c7a1232 sp 00007fff4e0b7bb8 error 4 in libgdk-3.so.0.2200.26[7fb61c758000+e The vmtoolsd process running as root does start. I don't know how long this problem has been present. I happened to see it in Fedora Rawhide on 19 December and checked my other Linux VMs at that time. I'm running my Linux VMs under VMware Workstation Player 14 hosted on Windows 7. I'm running current Tumbleweed versions, including open-vm-tools 10.1.15-1.2. I noticed that TW will update to 10.2.0 soon. It might still be a problem there as well. Fedora has a bug 1526942 against open-vm-tools 10.2.0 for what appears to be the identical problem. Just for reference, I do NOT see the problem in Debian Sid (Unstable) running open-vm-tools 10.2. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1073760
http://bugzilla.opensuse.org/show_bug.cgi?id=1073760#c2
--- Comment #2 from Ron Lovell
However, I'd like some details on how you are running `vmtoolsd -n vmusr`.
I'm not doing anything special, so /etc/xdg/autostart/vmware-user-autostart.desktop is presumably starting the per-user vmtoolsd. I see its last access time is exactly when I logged into GNOME yesterday. New results: I just logged into GNOME with X11 session, and the per-user vmtoolsd process starts successfully. Output of ps: lovells@ron5tum:~$ ps -ef | grep vmtools root 1067 1 0 Dec21 ? 00:01:31 /usr/bin/vmtoolsd lovells 24535 1 0 08:11 tty2 00:00:00 /usr/bin/vmtoolsd -n vmusr --blockFd 3 Considering the backtraces shown in Red Hat Bug 1526952, this is beginning to have the feel of a graphics situation that occurs in Wayland sessions that vmtoolsd does not handle gracefully. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1073760
http://bugzilla.opensuse.org/show_bug.cgi?id=1073760#c3
Mike Latimer
Considering the backtraces shown in Red Hat Bug 1526952, this is beginning to have the feel of a graphics situation that occurs in Wayland sessions that vmtoolsd does not handle gracefully.
Yes, I just duplicated the problem after switching to Wayland on my test box. I also upgraded to 10.2.0 and still saw the problem: #sudo coredumpctl dump PID: 2149 (vmtoolsd) UID: 1000 (mlatimer) GID: 100 (users) Signal: 11 (SEGV) Timestamp: Fri 2017-12-22 11:06:59 MST (2min 54s ago) Command Line: /usr/bin/vmtoolsd -n vmusr --blockFd 3 Executable: /usr/bin/vmtoolsd Control Group: /user.slice/user-1000.slice/session-1.scope Unit: session-1.scope Slice: user-1000.slice Session: 1 Owner UID: 1000 (mlatimer) Boot ID: f031430e7d6544148a8b662ad2dedc83 Machine ID: e63fac42f89c4a3e968d9649b158679e Hostname: localhost Storage: /var/lib/systemd/coredump/core.vmtoolsd.1000.f031430e7d6544148a8b662ad2dedc83.2149.1513966019000000.lz4 Message: Process 2149 (vmtoolsd) of user 1000 dumped core. # gdb /usr/bin/vmtoolsd core.out Core was generated by `/usr/bin/vmtoolsd -n vmusr --blockFd 3'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007f3c09a14232 in gdk_window_has_impl (window=<optimized out>) at gdkwindow.c:677 677 gdkwindow.c: No such file or directory. [Current thread is 1 (Thread 0x7f3c0ecde780 (LWP 2149))] (gdb) bt #0 0x00007f3c09a14232 in gdk_window_has_impl (window=<optimized out>) at gdkwindow.c:677 #1 _gdk_window_has_impl (window=window@entry=0x0) at gdkwindow.c:678 #2 0x00007f3c09a4b63e in gdk_x11_window_get_xid (window=0x0) at gdkwindow-x11.c:5560 #3 0x00007f3c0a92275d in X11Lock_Init () from /usr/lib64/open-vm-tools/plugins/vmusr/libdesktopEvents.so #4 0x00007f3c0a9224ab in ToolsOnLoad () from /usr/lib64/open-vm-tools/plugins/vmusr/libdesktopEvents.so #5 0x000055f469c17318 in ToolsCore_LoadPlugins () #6 0x000055f469c15fa3 in ToolsCoreRunLoop () #7 0x000055f469c15398 in main () As Ravindra is already working on this in the Fedora bug, I'll set needinfo to him. If anything is needed from my environment, I'd be happy to provide it. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1073760
http://bugzilla.opensuse.org/show_bug.cgi?id=1073760#c4
--- Comment #4 from Ravindra Kumar
http://bugzilla.opensuse.org/show_bug.cgi?id=1073760
http://bugzilla.opensuse.org/show_bug.cgi?id=1073760#c5
--- Comment #5 from Ron Lovell
http://bugzilla.opensuse.org/show_bug.cgi?id=1073760
http://bugzilla.opensuse.org/show_bug.cgi?id=1073760#c6
Ravindra Kumar
http://bugzilla.opensuse.org/show_bug.cgi?id=1073760
http://bugzilla.opensuse.org/show_bug.cgi?id=1073760#c9
--- Comment #9 from Ron Lovell
participants (1)
-
bugzilla_noreply＠novell.com