Description of problem: VMWare Tools crash when trying to reinstall or remove it. Version-Release number of selected component: open-vm-tools-9.10.2-1.fc22 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/bin/vmtoolsd -n vmusr crash_function: g_static_mutex_get_mutex_impl executable: /usr/bin/vmtoolsd global_pid: 1805 kernel: 4.1.3-201.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (9 frames) #0 g_static_mutex_get_mutex_impl at deprecated/gthread-deprecated.c:515 #1 RpcChannel_Send at rpcChannel.c:836 #2 CopyPasteDnDWrapper::OnCapReg at copyPasteDnDWrapper.cpp:558 #3 DnDCPCapabilities at dndcp.cpp:107 #4 g_cclosure_user_marshal_POINTER__POINTER_BOOLEAN at svcSignals.c:85 #8 g_signal_emit_by_name at gsignal.c:3401 #9 ToolsCore_UnloadPlugins at pluginMgr.c:880 #10 ToolsCoreCleanup at mainLoop.c:62 #11 ToolsCoreRunLoop at mainLoop.c:243
Created attachment 1061196 [details] File: backtrace
Created attachment 1061197 [details] File: cgroup
Created attachment 1061198 [details] File: core_backtrace
Created attachment 1061199 [details] File: dso_list
Created attachment 1061200 [details] File: environ
Created attachment 1061201 [details] File: limits
Created attachment 1061202 [details] File: maps
Created attachment 1061203 [details] File: mountinfo
Created attachment 1061204 [details] File: namespaces
Created attachment 1061205 [details] File: open_fds
Created attachment 1061206 [details] File: proc_pid_status
Created attachment 1061207 [details] File: var_log_messages
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.