Version-Release number of selected component: open-vm-tools-10.2.0-1.fc28 Additional info: reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=f85b5e556c3a47ae87b88ebd774bde31;i=6979;b=e781bf2c36c2434f9577129b8b285677;m=1f5a34c;t=56099cf45ffbb;x=80d67612d0116652 kernel: 4.15.0-0.rc3.git4.1.fc28.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (9 frames) #0 gdk_window_has_impl at gdkwindow.c:677 #1 _gdk_window_has_impl at gdkwindow.c:678 #2 gdk_x11_window_get_xid at gdkwindow-x11.c:5560 #3 InitGroupLeader at x11Lock.c:85 #4 AcquireDisplayLock at x11Lock.c:225 #5 X11Lock_Init at x11Lock.c:370 #6 ToolsOnLoad at desktopEvents.c:118 #7 ToolsCore_LoadPlugins at pluginMgr.c:730 #8 ToolsCoreRunLoop at mainLoop.c:291
Created attachment 1369326 [details] File: backtrace
Created attachment 1369327 [details] File: cgroup
Created attachment 1369328 [details] File: core_backtrace
Created attachment 1369329 [details] File: cpuinfo
Created attachment 1369330 [details] File: dso_list
Created attachment 1369331 [details] File: environ
Created attachment 1369332 [details] File: exploitable
Created attachment 1369333 [details] File: limits
Created attachment 1369334 [details] File: maps
Created attachment 1369335 [details] File: mountinfo
Created attachment 1369336 [details] File: open_fds
Created attachment 1369337 [details] File: proc_pid_status
Kevin, could you please look into it? Thanks!
*** Bug 1528064 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Crash is reported right after boot of a current Rawhide Workstation live image. reporter: libreport-2.9.3 backtrace_rating: 3 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=36f728a09a9b4372931b6b6b52da3120;i=7df;b=e70313c7318b469bb87112f9b2f1ad02;m=5954087;t=560cc59ad1ca3;x=3111d996988e5ad3 kernel: 4.15.0-0.rc4.git1.1.fc28.x86_64 package: open-vm-tools-10.2.0-2.fc28 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: 3 5 type: CCpp uid: 1000
Proposing as an F28 Final blocker, per criterion "There must be no SELinux denial notifications or crash notifications on boot of or during installation from a release-blocking live image, or at first login after a default install of a release-blocking desktop" - https://fedoraproject.org/wiki/Fedora_28_Final_Release_Criteria#SELinux_and_crash_notifications . This crash appears to happen on boot of current Workstation live images.
Similar problem has been detected: This happened on the startup of the newly updated Fedora Rawhide in Oracle VirtualBox. The machine seems to be running fine, though. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=37d938dc73fd4b6ea8b5a83526598995;i=9049d;b=e67da6710d454c3d974a14e174ca1779;m=1c9e47cd;t=560cf15e8584e;x=65cce214e304ec54 kernel: 4.15.0-0.rc4.git0.1.fc28.x86_64 package: open-vm-tools-10.2.0-2.fc28 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
@Adam, are you running Rawhide Workstation live image in a VM or physical? If VM, what hypervisor are you using? @Rafal, could you please move /usr/lib64/open-vm-tools/plugins/vmusr/libdesktopEvent.so out to say /tmp and then see if the issue gets resolved?
Ravindra: KVM (via qemu).
Similar problem has been detected: see this immediately after boot into the Installation screen reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=f1b555ed1b184f98b8655bbdb8da74c9;i=7a6;b=6fc20036be47400aaac53c927c30c9b0;m=35006a9;t=560d282779a5a;x=bce39e5f183b1e46 kernel: 4.15.0-0.rc4.git1.1.fc28.x86_64 package: open-vm-tools-10.2.0-2.fc28 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
(In reply to Ravindra Kumar from comment #18) > @Rafal, could you please move > /usr/lib64/open-vm-tools/plugins/vmusr/libdesktopEvent.so out to say /tmp > and then see if the issue gets resolved? It seems to be resolved. I don't know what vmtoolsd does but if this library is removed then it does not crash. But also I can't see it running when I run ps aux. When the library is restored it says it dumped a core. From the stack trace it looks like it is trying to obtain a XID of a window which is NULL. Maybe it's a bug in GTK? It should not crash.
*** Bug 1528307 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Happens every startup when vmtoolsd.service is started. The root-owned vmtoolsd starts, but the user-owned vmtoolsd segfaults. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=6d78e1c58dd74f63954466a9f7e84417;i=1ff49d;b=65dc3846312649059c01ec3d4268a714;m=22026c1;t=560da5c4e477c;x=ddc8c8b1a5007f0a kernel: 4.15.0-0.rc4.git1.1.fc28.x86_64 package: open-vm-tools-10.2.0-2.fc28 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1024
*** Bug 1528389 has been marked as a duplicate of this bug. ***
(In reply to Adam Williamson from comment #19) > Ravindra: KVM (via qemu). Could you please share the backtrace? I'd like to see if the crash is exactly same? (In reply to Rafal Luzynski from comment #21) > It seems to be resolved. I don't know what vmtoolsd does but if this library > is removed then it does not crash. That's because crash is happening while loading this plugin. If the plugin is not there, then it is not loaded and there is no crash. > But also I can't see it running when I run ps aux. That's because after loading plugins it checks if it is running on VMware platform or not. It exits gracefully when VMware platform is not detected. > From the stack trace it looks like it is trying to obtain a XID of a window > which is NULL. Maybe it's a bug in GTK? It should not crash. Yes, either that or some interaction with Wayland. (In reply to Ron Lovell from comment #23) > Similar problem has been detected: > > Happens every startup when vmtoolsd.service is started. The root-owned > vmtoolsd starts, but the user-owned vmtoolsd segfaults. Ron, are you running Fedora in a VM on VMware platform? root-owned vmtoolsd should not be running on non-VMware platforms as well as physical machines.
(In reply to Ravindra Kumar from comment #25) > (In reply to Adam Williamson from comment #19) > > Ravindra: KVM (via qemu). > > Could you please share the backtrace? I'd like to see if the crash is > exactly same? > > (In reply to Rafal Luzynski from comment #21) > > It seems to be resolved. I don't know what vmtoolsd does but if this library > > is removed then it does not crash. > > That's because crash is happening while loading this plugin. If the plugin > is not there, then it is not loaded and there is no crash. > > > But also I can't see it running when I run ps aux. > > That's because after loading plugins it checks if it is running on VMware > platform or not. It exits gracefully when VMware platform is not detected. > > > From the stack trace it looks like it is trying to obtain a XID of a window > > which is NULL. Maybe it's a bug in GTK? It should not crash. > > Yes, either that or some interaction with Wayland. > > (In reply to Ron Lovell from comment #23) > > Similar problem has been detected: > > > > Happens every startup when vmtoolsd.service is started. The root-owned > > vmtoolsd starts, but the user-owned vmtoolsd segfaults. > > Ron, are you running Fedora in a VM on VMware platform? root-owned vmtoolsd > should not be running on non-VMware platforms as well as physical machines. I am running Fedora Rawhide under VMware Workstation Player 14 hosted on Windows 7. Before problem came up, I saw vmtoolsd running as root and a second vmtoolsd (with args -n vmusr) running as myself. FYI, openSUSE Tumbleweed also has this problem, currently running open-vm-tools 10.1.15, and Debian Sid does NOT have the problem, currently running open-vm-tools 10.2. For Tumbleweed see my Bug 1073760 in SUSE Bugzilla, which just got a reply I need to check out.
(In reply to Ravindra Kumar from comment #25) > > From the stack trace it looks like it is trying to obtain a XID of a window > > which is NULL. Maybe it's a bug in GTK? It should not crash. > > Yes, either that or some interaction with Wayland. > That's significant. When I login to GNOME with X11 session, the per-user vmtoolsd (started via /ec/xdb/autostart/vmware-user.desktop) starts successfully. lovellf@ron5raw:~$ ps -ef | grep vmtoolsd root 713 1 0 Dec21 ? 00:02:19 /usr/bin/vmtoolsd lovellf 20406 1 0 08:19 tty2 00:00:00 /usr/bin/vmtoolsd -n vmusr
(In reply to Ron Lovell from comment #27) > That's significant. When I login to GNOME with X11 session, the per-user > vmtoolsd (started via /ec/xdb/autostart/vmware-user.desktop) starts > successfully. Make that /etc/xdg/autostart/vmware-user.desktop. Confusingly, that file isn't always referenced on login (per ls -lu). Trying to correlate, looking at Rawhide, Tumbleweed, and Sid.
*** Bug 1528748 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Unsure what happened. Rebooted laptop after installing updates and got the crash alert when I logged in. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=06e10de8821f441098dbe047d52f10f2;i=c4f9;b=5597168f24aa43c4b782e676774b3829;m=42fdba69;t=5611acd9687e3;x=3cba67fed010a682 kernel: 4.14.8-300.fc27.x86_64 package: open-vm-tools-10.2.0-2.fc27 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1529137 has been marked as a duplicate of this bug. ***
*** Bug 1529155 has been marked as a duplicate of this bug. ***
Similar problem has been detected: booting F27 after a dnf update reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=c38ab068f37a4a1bb0eca6705a2eb7f2;i=7ab;b=4375836425794cb6a3c37afbf3e3ccbf;m=8efc2a2;t=56161c0c4e1a0;x=815dcad4966e4c98 kernel: 4.14.8-300.fc27.x86_64 package: open-vm-tools-10.2.0-2.fc27 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1104
Similar problem has been detected: It happened immediately upon login. The crash notification was the only indication that open-vm-tools tried to launch. Prior to the login, I updated Fedora using dnf distro-sync, rebooted and logged in. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=4b9e0ae996e045b081db8590917f345f;i=1e25f;b=eb480d6bd872488fb6d894bd1e5109b6;m=79b7d6e;t=56166d4ab9bb0;x=41bfdb28336dc0aa kernel: 4.14.8-300.fc27.x86_64 package: open-vm-tools-10.2.0-2.fc27 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Starting a session reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=e3b7d969c27042c8bb40da64310f1c1b;i=6eaa;b=9314757cbe99418b804c62dc4dc77afe;m=1d0635ce4;t=56167f3eea87e;x=a3267f38456e51f kernel: 4.14.8-300.fc27.x86_64 package: open-vm-tools-10.2.0-2.fc27 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Just try to enter my password in the lock screen. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=67ae6e4c8b9245789b9e999637d056dc;i=858;b=ccfa2ca562564c1c8ece39f019ed1690;m=233e6a4;t=561682c3ba22c;x=64cffdfec25965c5 kernel: 4.14.8-300.fc27.x86_64 package: open-vm-tools-10.2.0-2.fc27 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Started desktop (Gnome Shell) after updates which included open-vm-tools.x86_64 10.2.0-2.fc27 and open-vm-tools-desktop.x86_64 10.2.0-2.fc27. Nothing VM related explicitly configured to start at boot or desktop start. Boxes not installed and Oracle VirtualBox installed but not used. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=d16ab61be14e4080b3d2213f7e2b66cd;i=1a67b;b=5d235b6f6d2e46eea4ae4786a94d3e64;m=621b15d9;t=56168202c455d;x=5f6cb7001281fcd1 kernel: 4.14.8-300.fc27.x86_64 package: open-vm-tools-10.2.0-2.fc27 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: failed during reboot after most recent update reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=2a5dd4caa9434c689f8f5e8adcf59966;i=1b853;b=ed065e45db394dfdbe4c951a30ac88a0;m=b79580a;t=56168c6a3008b;x=6aa294e95dadbeba kernel: 4.14.8-300.fc27.x86_64 package: open-vm-tools-10.2.0-2.fc27 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I had just logged in after a fresh boot. I did not directly use open-vm-tools. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=cbf63cbb28184f17b872900d2171dd7e;i=1378;b=2d3bd747dc6041e4835166f927479f60;m=79e17c7;t=561699004ae6e;x=ec1604df49ad5ff2 kernel: 4.14.8-300.fc27.x86_64 package: open-vm-tools-10.2.0-2.fc27 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
As per comment 27 and comment 28, I had been using X sessions, and never saw this crash. The crash in comment 39 happened the first time I used a Wayland session.
Similar problem has been detected: restarted my computer reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=e6f023bc45c84bc790b51bb60dee9f3c;i=4514d6;b=99bf56902a1d401f9699e004d2ee18e4;m=210323b;t=5616c3fc01206;x=d0d43d45711800e5 kernel: 4.14.8-300.fc27.x86_64 package: open-vm-tools-10.2.0-2.fc27 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: unknown type: CCpp uid: 1000
Similar problem has been detected: At start up. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=1ecb89dada864f4b82dd13fe6cafb77c;i=1e625;b=da2a0ad316c747c7aeb234406262eaf4;m=16a6af73;t=5616c5520d12e;x=8d58c702f8c6c2e8 kernel: 4.14.8-300.fc27.x86_64 package: open-vm-tools-10.2.0-2.fc27 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Failed after start up on a physcial machine (not quite sure why open-vm-tools is installed). reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=ec8c35286d844ceb8e5a1feebd61db93;i=2194eb;b=376b1e65585b46bea8f72f256b1d3d29;m=1f3eff23;t=5616ce4181443;x=d6fa08f6d7f348af kernel: 4.14.8-300.fc27.x86_64 package: open-vm-tools-10.2.0-2.fc27 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 501
*** Bug 1529324 has been marked as a duplicate of this bug. ***
*** Bug 1529362 has been marked as a duplicate of this bug. ***
*** Bug 1529378 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I just clicked on a link in Firefox and was thrown out of my GNOME session. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=e4dc33b48ca7472ea79a009a0eacb524;i=2c8bc;b=47573981a8514e6f9e16db7b68c67e8f;m=3f16734d3;t=5616e70b51042;x=af7e41daa28e4fc8 kernel: 4.14.8-300.fc27.x86_64 package: open-vm-tools-10.2.0-2.fc27 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: System startup reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=d7a7b9005ef74c89a3930607c202c566;i=7fc3d;b=7526de207fb14419be0684c4283cb63a;m=253c51b;t=561717f6b0bbe;x=4bd93970be9e48cc kernel: 4.14.8-300.fc27.x86_64 package: open-vm-tools-10.2.0-2.fc27 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I got This error each time i'm restarting my machine reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=80c3944c53bb4fa094b2c3b8af396675;i=8ac58;b=66daaee124df4a0b8be4cf26440f5219;m=8424c71;t=561759d3aafd8;x=bcde83ef377a6936 kernel: 4.14.8-300.fc27.x86_64 package: open-vm-tools-10.2.0-2.fc27 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: After start reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=6d7ddadd022443ed9709cd2e36a4ff33;i=7b3cfb;b=4389ce5c39434fba9a68f520b7f9e37d;m=768164f;t=56175d6e21ce1;x=6b1a6e09676cc023 kernel: 4.14.8-300.fc27.x86_64 package: open-vm-tools-10.2.0-2.fc27 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: using firefox 57 on Fedora27, and greating a terminal session after <menu><pgdown> reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=4ebf36b8788542a0847cdca0e71d43c3;i=4294f;b=6818bed950244100ba1e74d4e0f9f8fa;m=187c37e33;t=5617675a1655d;x=2eaa49badb9b3532 kernel: 4.14.8-300.fc27.x86_64 package: open-vm-tools-10.2.0-2.fc27 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I installed the latest update successfully and was reviewing what had been updated in the Software app, I clicked on the OS updates and this error message apeared in my notifications. I had no other apps running; the System continued to work normally. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=612ea45715774396a4e7037f00356cc1;i=417ac;b=7ec2607a91464e3183467c4be2139789;m=6cc46d2;t=5617706a86c35;x=19d4832858238db4 kernel: 4.14.8-300.fc27.x86_64 package: open-vm-tools-10.2.0-2.fc27 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Initial computer login (into Gnome) reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=33ed7df679db49ff806ca782b3330df0;i=57870;b=db0e2ef5b394493da8b8bae6f137fe69;m=28db6a3;t=56179b3cd2bff;x=11b7f6dda0cde57 kernel: 4.14.8-300.fc27.x86_64 package: open-vm-tools-10.2.0-2.fc27 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Immediate fault during cold boot a day after updates applied. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=f902860ed9834095898e9d6122e7da74;i=1654fa;b=279c259755244b23b3fc6a164df725b8;m=1138260;t=5617accf14ba2;x=2b3e49b587a8e148 kernel: 4.14.8-300.fc27.x86_64 package: open-vm-tools-10.2.0-2.fc27 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Crashed on login reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=06ab058dc0134fb8a007ebf4674eb3b4;i=74a9;b=4d307d06d1334fb0a3597d2d9c942911;m=f8549c;t=5617b8a7fd640;x=9ff6bd580e91a920 kernel: 4.14.8-300.fc27.x86_64 package: open-vm-tools-10.2.0-2.fc27 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: unknown type: CCpp uid: 1000
Similar problem has been detected: This was only reported for me on the "Problem Reporting" after I was applied the latest updates by rebooting the Fedora. When I sign-in "Problem Reporting" was waiting me on the screen. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=cc22ef4490964ff09b6ba093d9991aaa;i=d24fd;b=1e99104539ce4518b26408e2950c4c39;m=16244fe;t=5617bb29c8fba;x=d6e2723eaf4aea97 kernel: 4.14.8-300.fc27.x86_64 package: open-vm-tools-10.2.0-2.fc27 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: gnome session crashed after waking up from suspend reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=8924cd8b99804dc8b3f3a7278a73f82b;i=2f84b;b=f9ac7ccdc9264f439e83341b6645af9a;m=a01bbbbd;t=5617d1d864bdf;x=e777515405cfa2f0 kernel: 4.14.8-300.fc27.x86_64 package: open-vm-tools-10.2.0-2.fc27 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I had just logged in to a GNOME session. I'm not using a VM and had no idea it was even running until it crashed. I had Evolution and Empathy set to open on login. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=5450a613acfe4ba69016a76228d8521a;i=108c41;b=7059eda82add45d7bf871bdf4947c9bc;m=5dd2d95;t=5617d5a0f1092;x=637fbba01730d85e kernel: 4.14.8-300.fc27.x86_64 package: open-vm-tools-10.2.0-2.fc27 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1529669 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I just logged in - and got a message telling me of a crash reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=161060363342445bb276c78d612db016;i=1c0444c;b=6d538fb5a30948adbd9da3ac69c5a04c;m=4e6327c18;t=56181dc36336e;x=84922ad5103d4e4e kernel: 4.14.8-300.fc27.x86_64 package: open-vm-tools-10.2.0-2.fc27 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1002
Similar problem has been detected: Error was reported when I signed on to Gnome after restarting. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=e5e91592c3194cbc891a3f9eb58aa3a4;i=81e;b=7fd998fcf49642b8a0139366ddd54ef1;m=41e5a9c;t=56181fabe79f7;x=701eba4ef8b9ff6f kernel: 4.14.8-300.fc27.x86_64 package: open-vm-tools-10.2.0-2.fc27 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Logged out of Fedora 27 using Plasma. Select Gnome Classis and log in. Error occurred in start up. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=8f43951af8a74cc78078a8dc1d6f05af;i=1670a;b=f22b01bcee2546c18a215252a2365524;m=f9e0c38;t=56182672cfe34;x=84aa16aff10558d9 kernel: 4.14.8-300.fc27.x86_64 package: open-vm-tools-10.2.0-2.fc27 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
open-vm-tools-10.2.0-3.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-b26f7becf5
open-vm-tools-10.2.0-3.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-2228f21eb5
Similar problem has been detected: I've installed fedora 27 just yesterday. I've tried to upgrade my system using "# dnf upgrade -y" but in the middle of cleaning process i've lost power my battery was too low and fedora automaticly powered off. After next boot i've lost my system setting menu. Problem just happend when i tried to open it. Almost everything else is working good. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=e90b8e8c56a644799a1b690e1b990520;i=73fb;b=2112e1ab24b244c8b3312cb8c4695ea0;m=558ae96;t=5618b41f2b643;x=9858a03a98b032e1 kernel: 4.13.9-300.fc27.x86_64 package: open-vm-tools-10.2.0-2.fc27 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: This happen when I start my PC. Just after start my pc i have message on screen "open-vm-tools quit unexpectedly" reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=b1e5fa18598e4c7b9e1c9106edb2dd00;i=e3ee;b=f527740d0f52446896a74c4224fdc1af;m=a00ac5a;t=5618c9a2b2559;x=5455fd64e2b3bdad kernel: 4.14.8-300.fc27.x86_64 package: open-vm-tools-10.2.0-2.fc27 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: On power up reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=91c44421506d44588710e342f1d0a9a2;i=1fef77;b=23c0434c305a4a4886a977d2032b2071;m=7628eb9;t=56192cb9c96f5;x=2e49cf4c49479da8 kernel: 4.14.8-200.fc26.x86_64 package: open-vm-tools-10.2.0-2.fc26 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 500
open-vm-tools-10.2.0-3.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-b26f7becf5
open-vm-tools-10.2.0-3.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-2228f21eb5
Similar problem has been detected: This was a fresh install but with encrypted partitions. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=033eb77b1be54215932d52cb43951e58;i=1d91;b=8b0067c0401f42e3b8ac35dba409cd88;m=367cc04;t=56195391515f7;x=4cc6a92c7eb57df5 kernel: 4.14.8-300.fc27.x86_64 package: open-vm-tools-10.2.0-2.fc27 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Logged in and it crashed reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=75a46794aa5643b2ae456f909284b622;i=26207;b=ab724a8aa9674ef5a9a8cd1c46da4862;m=467a82dff;t=561971eecd20c;x=ef79f6f81179fd3e kernel: 4.14.8-200.fc26.x86_64 package: open-vm-tools-10.2.0-2.fc26 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1001
open-vm-tools-10.2.0-3.fc28 fixes the issue in Rawhide on my system, running as VM under VMware Workstation 14. Good work, guys.
Similar problem has been detected: No idea how this happened. This bug report opened up when I booted up my computer, so maybe something happened when I closed it. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=1ad6737588764571a65eca6abbbde7b5;i=18c33;b=72e02e04b1fb407383b3861d150f1fd1;m=15e6477;t=561acf6741558;x=e125ef4c912022b7 kernel: 4.14.8-200.fc26.x86_64 package: open-vm-tools-10.2.0-2.fc26 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Problem occurred at boot time reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=0ce936b61e164c898356bb75678ae2e0;i=44ccb1;b=bd7efc171b9a4e37bc0643cf53b1ce92;m=104a638;t=561b3b73d845e;x=2584df3f684d0870 kernel: 4.14.8-300.fc27.x86_64 package: open-vm-tools-10.2.0-2.fc27 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: unknown type: CCpp uid: 1000
Similar problem has been detected: I watched a movie on 'mpv' then I touched the touchscreen reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=1bd4fc05ce5c4f23a106d128e7aca000;i=b637;b=2cf5d3c26d3149309ab6a95c2ae16745;m=13ef2f20f3;t=561bdc99cbcd4;x=1a2dc49b80f88b20 kernel: 4.14.8-200.fc26.x86_64 package: open-vm-tools-10.2.0-2.fc26 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I just did an upgrade from fedora 26 to fedora 27, using the manual method. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=ecb36497fcc14c41bb0649b125acb986;i=3392e4;b=9008e2f9f6784b2d82a1429c3ff456b0;m=b07cc8e;t=561bed71e30f6;x=f1a001c81645f99c kernel: 4.14.8-300.fc27.x86_64 package: open-vm-tools-10.2.0-2.fc27 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: When starting the computer, the error occurs. No specific actions taken that trigger the error. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=e4c49eb35044418da2e51426dc348a8b;i=90324;b=1272964320e04bdc8cf3bf5df8ae2029;m=7874f77;t=561c7204743e7;x=45b5092ebc14f198 kernel: 4.14.8-300.fc27.x86_64 package: open-vm-tools-10.2.0-2.fc27 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
open-vm-tools-10.2.0-3.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.
open-vm-tools-10.2.0-3.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.
Similar problem has been detected: I walked away from my laptop for a few hours and only remember going through my emails and reading/deleting the older ones. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=50a1dfb18a3747be95440916f3c3e5c2;i=12818;b=d4fc3096add04e89ac109f93b8860337;m=5305644af;t=561d2f0dac45d;x=bb139639ecf869fa kernel: 4.14.8-300.fc27.x86_64 package: open-vm-tools-10.2.0-2.fc27 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Virtual machine was in suspended running under vmware player 12.5.8, under Windows 10 as a host. After resume, network was not coming back up so a reboot was performed. As soon as the machine was up, a notification about the crash appeared. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=67560ff94a0643438920b611b49a861e;i=7fa0;b=0d31c4a873d447d2bd3ef4d457f9a130;m=87bdc9a;t=561f925e2a5a3;x=11df11276472b9ae kernel: 4.14.8-300.fc27.x86_64 package: open-vm-tools-10.2.0-2.fc27 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
@96cavalier and @Igor, open-vm-tools-10.2.0-2.fc27 doesn't have the fix. Fix is available in open-vm-tools-10.2.0-3.fc27. Please update the open-vm-tools packages on your system to get the fix, try 'dnf update open-vm-tools-desktop'.
You will also need to logout and log back in to have 'vmtoolsd -n vmusr' restarted.
Similar problem has been detected: logged into my laptop with clean upgrade to fedora 27, locked screen, provided credentials to unlock, froze for several seconds and then showed login screen as though I had just booted reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=eec5ac4309544f029756b2a84ae523a7;i=6907;b=632c458a2d894447ae8de397b5f89c5b;m=43e63dca;t=56182af1f3b95;x=1974a6032476a628 kernel: 4.14.8-300.fc27.x86_64 package: open-vm-tools-10.2.0-2.fc27 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Found this in ABRT. vmtoolsd should not even be running. I've never used VMWare, and this is not a VM. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=508c5b714a5f43f09ff2dfd5a43bbac9;i=517c3;b=11965f3bd9dc4725a310c2712b2f54fa;m=1f5d430;t=561838c3b3dfe;x=d54c5f7f686b0e88 kernel: 4.14.8-300.fc27.x86_64 package: open-vm-tools-10.2.0-2.fc27 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: /var/spool/abrt/ccpp-2018-01-07-10:46:31.766295-1529/comment 12/29(Fri)Shutdown後、01/07(Sun)Boot直後に発生 背後で、dnf update実行中+Firefox(Reload中)実行中+Thunderbird起動中(CPU Idle = 0.0%で、大変重たい状況) reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=e7ca4dde7a9c4a56bdce46dc37c2360d;i=20d9;b=5c25e3ec80c149ea94176f7035d14627;m=9e96cb1;t=56225d9cf56a4;x=f79408a94d248354 kernel: 4.14.8-300.fc27.x86_64 package: open-vm-tools-10.2.0-2.fc27 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Just started my computer reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=90b291d54a874be0b0c7838cd8eb736b;i=74a87e;b=85455560ccff4f5da9fae2d2dc04e654;m=1054f06a;t=5616ada4d2e9b;x=9bb657680163cac7 kernel: 4.14.8-300.fc27.x86_64 package: open-vm-tools-10.2.0-2.fc27 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Unlocked screen reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: gdk_window_has_impl executable: /usr/bin/vmtoolsd journald_cursor: s=75a46794aa5643b2ae456f909284b622;i=7a1f3;b=ab724a8aa9674ef5a9a8cd1c46da4862;m=2a969ff8b79;t=5643c217f1fae;x=501817a7aeb24776 kernel: 4.14.8-200.fc26.x86_64 package: open-vm-tools-10.2.0-2.fc26 reason: vmtoolsd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1001