Version-Release number of selected component: open-vm-tools-10.1.5-4.fc25 Additional info: reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: VMToolsLogPanic executable: /usr/bin/vmtoolsd global_pid: 1775 kernel: 4.10.12-200.fc25.x86_64+debug pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (9 frames) #2 VMToolsLogPanic at vmtoolsLog.c:209 #3 VMToolsLog at vmtoolsLog.c:453 #10 XGetWindowProperty at GetProp.c:69 #11 XFetchName at FetchName.c:46 #12 AcquireDisplayLock at x11Lock.c:286 #13 X11Lock_Init at x11Lock.c:370 #14 ToolsOnLoad at desktopEvents.c:118 #15 ToolsCore_LoadPlugins at pluginMgr.c:730 #16 ToolsCoreRunLoop at mainLoop.c:206
Created attachment 1277139 [details] File: backtrace
Created attachment 1277140 [details] File: cgroup
Created attachment 1277141 [details] File: core_backtrace
Created attachment 1277142 [details] File: dso_list
Created attachment 1277143 [details] File: environ
Created attachment 1277144 [details] File: limits
Created attachment 1277145 [details] File: maps
Created attachment 1277146 [details] File: mountinfo
Created attachment 1277147 [details] File: namespaces
Created attachment 1277148 [details] File: open_fds
Created attachment 1277149 [details] File: proc_pid_status
Created attachment 1277150 [details] File: var_log_messages
*** Bug 1450431 has been marked as a duplicate of this bug. ***
*** Bug 1447600 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I got the crash error as soon as I logged in to the gnome desktop via gdm. reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: VMToolsLogPanic executable: /usr/bin/vmtoolsd global_pid: 1974 kernel: 4.11.5-200.fc25.x86_64 package: open-vm-tools-10.1.5-4.fc25 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project reason: vmtoolsd killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
*** Bug 1467732 has been marked as a duplicate of this bug. ***
*** Bug 1470144 has been marked as a duplicate of this bug. ***
*** Bug 1470499 has been marked as a duplicate of this bug. ***
*** Bug 1471264 has been marked as a duplicate of this bug. ***
*** Bug 1471412 has been marked as a duplicate of this bug. ***
*** Bug 1471754 has been marked as a duplicate of this bug. ***
*** Bug 1472097 has been marked as a duplicate of this bug. ***
*** Bug 1472795 has been marked as a duplicate of this bug. ***
*** Bug 1475043 has been marked as a duplicate of this bug. ***
*** Bug 1476260 has been marked as a duplicate of this bug. ***
*** Bug 1477407 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Crash after operating system startup reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: VMToolsLogPanic executable: /usr/bin/vmtoolsd journald_cursor: s=8d1d0797206e428997460532e7f6ee00;i=2354c;b=a7e836bb55d5454eafd714510f21e9b4;m=1ae4cba;t=556381c331404;x=da83ea53f34ac169 kernel: 4.12.4-300.fc26.x86_64 package: open-vm-tools-10.1.5-5.fc26 reason: vmtoolsd killed by signal 6 rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I am using Fedora as VirtualBox's VM. The crash occured right after I logged in. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: VMToolsLogPanic executable: /usr/bin/vmtoolsd journald_cursor: s=fafc39b834c04e10890685f207ddaeb5;i=2aa6;b=095e2031e05545fabf6ae0981b471ad2;m=1a8d447;t=55668669aedd8;x=780e1c56eb59974a kernel: 4.11.11-300.fc26.x86_64 package: open-vm-tools-10.1.5-5.fc26 reason: vmtoolsd killed by signal 6 rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1441596 has been marked as a duplicate of this bug. ***
*** Bug 1401214 has been marked as a duplicate of this bug. ***
*** Bug 1398820 has been marked as a duplicate of this bug. ***
(In reply to Norbert Langner from comment #28) > Similar problem has been detected: > > I am using Fedora as VirtualBox's VM. The crash occured right after I logged > in. Norbert, your issue might be different. Could you please file a new report with backtrace so that I can confirm if it is same or different? Thanks!
Similar problem has been detected: Downloaded a .docx file and set it to open automatically once download is completed Switched to Totem player on another desktop and kept watching a video After a while the LibreOffice splash screen appeared Video playback stopped, mouse and keyboard frozen The machine was somehow still doing something and audio of the video file continued I pressed space to pause and after about a minute it actually did pause. Mouse pointer was not actually frozen, but had a delay of one minute until it reacted to input. Same with keyboard. As the machine did not recover from that state I had to press the reset button to reboot. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: VMToolsLogPanic executable: /usr/bin/vmtoolsd journald_cursor: s=f0608a6ec2e24d11aaab88ba0ed9e165;i=8c9;b=3043afc037f34e43868ec264e1542713;m=2b7f517;t=55743c845b7a7;x=bcb037c592baa72a kernel: 4.12.5-300.fc26.x86_64 package: open-vm-tools-10.1.10-1.fc26 reason: vmtoolsd killed by signal 6 rootdir: / runlevel: unknown type: CCpp uid: 1000
*** Bug 1484922 has been marked as a duplicate of this bug. ***
Assigning to Kevin who is looking at it.
The problem is that when we try to get the name of the specified window using XFetchName(), the window returned by XQueryTree() is a bad window. So, _XError() calls gdk_x_error() to log "BadWindow (invalid Window parameter)" with log_domain="Gdk" and log_level=G_LOG_LEVEL_ERROR. Then it goes to the log handler of VMTools. In VMToolsLog(), g_strdup() failed to allocate memory. Then VMToolsLogPanic() aborts the process and generates the stack trace we have. I think it is due to system being low on resources. If we cannot alloc memory, any error can occur. I want to know the memory size of the VM to see if it is too small to run.
Note that I had this exact crash (bz1477407, at least marked as a duplicate) and it crashes on my host node (no idea why it was run there), 48G of RAM.
This crash occurred in my host, rather than my VM, as well. Host had 8GB of RAM, VM was allocated 512MB.
Similar problem has been detected: Notification occurred on startup after reboot. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: VMToolsLogPanic executable: /usr/bin/vmtoolsd journald_cursor: s=13fc334c67aa43b69b7b666a3548dab9;i=70f0;b=3ffeecdbe50a4ff5ab74d9571fb89f0d;m=215b299;t=558ec640c1694;x=37ffb1b676da58e8 kernel: 4.12.9-300.fc26.x86_64 package: open-vm-tools-10.1.10-1.fc26 reason: vmtoolsd killed by signal 6 rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Logged into my computer and received the crash notification. Not sure what caused it. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: VMToolsLogPanic executable: /usr/bin/vmtoolsd journald_cursor: s=a1b24ce9efc242bea73d05e055a4d317;i=a0bfe;b=30a4c305acdd4c448f1c0171853af1db;m=502e8094bb;t=55d121f40dcd2;x=120ec3e0f7a610ec kernel: 4.13.9-200.fc26.x86_64 package: open-vm-tools-10.1.10-3.fc26 reason: vmtoolsd killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: No idea, computer did this on it's own :-| reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: VMToolsLogPanic executable: /usr/bin/vmtoolsd journald_cursor: s=fc1c282dd0a7449d82dba39594db8ded;i=db9600;b=ca9086c34f2240939a4617f2e3728c5e;m=24a9bd5;t=55d7360dfbb7d;x=e5488d1b89915112 kernel: 4.13.10-200.fc26.x86_64 package: open-vm-tools-10.1.10-3.fc26 reason: vmtoolsd killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
*** Bug 1514743 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Booting in a virtual Fedora Linux under a Windows 10 host. Not sure what happened reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: VMToolsLogPanic executable: /usr/bin/vmtoolsd journald_cursor: s=7ee9b9cb7fd8445e9b8d016a1fafeb4b;i=b51;b=fbc96d201577487cb95a71f53a648420;m=919c286;t=55ed120543013;x=787c1c99a290b474 kernel: 4.13.13-300.fc27.x86_64 package: open-vm-tools-10.1.10-3.fc27 reason: vmtoolsd killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I have logged in and Problem Reporting opened reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: VMToolsLogPanic executable: /usr/bin/vmtoolsd journald_cursor: s=1942d8e3e3b64e16afaa72eccbdf9588;i=72da;b=f87474a579154b09a509ce895c69a15d;m=222336e;t=55f0636fae7b1;x=7f4c8f688caedbf1 kernel: 4.13.13-300.fc27.x86_64 package: open-vm-tools-10.1.10-3.fc27 reason: vmtoolsd killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
This was seen on Fedora 26 & 27 as well.
*** Bug 1526723 has been marked as a duplicate of this bug. ***
*** Bug 1528454 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Updated most current software as of 12/22/2017. Rebooted after update. At login screen, I entered my credentials. As soon as Gnome DE started, that's when the notification appeared. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: VMToolsLogPanic executable: /usr/bin/vmtoolsd journald_cursor: s=bfdd3156de764bce8333934b3d9bb87d;i=4cbb0;b=ff9e4179343e47feb119866964858fd4;m=9b50576;t=560f3da5fd59f;x=416b8b7337a1c0cb kernel: 4.14.7-300.fc27.x86_64 package: open-vm-tools-10.1.10-3.fc27 reason: vmtoolsd killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.