Bug 1329345

Summary: [abrt] open-vm-tools: VMToolsLogPanic(): vmtoolsd killed by SIGABRT
Product: [Fedora] Fedora Reporter: Patrick J. Scott <patrick.james.scott>
Component: open-vm-toolsAssignee: Ravindra Kumar <ravindrakumar>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: negativo17, ravindrakumar, rjones
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/142b3e2dad53c942140edffc5f5b5d0dc6604b37
Whiteboard: abrt_hash:05b8c3557162cbd8bdf51fb1d01a319ed1963542;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-08 14:17:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Patrick J. Scott 2016-04-21 16:39:19 UTC
Version-Release number of selected component:
open-vm-tools-10.0.0-7.fc23

Additional info:
reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        /usr/bin/vmtoolsd -n vmusr
crash_function: VMToolsLogPanic
executable:     /usr/bin/vmtoolsd
global_pid:     1723
kernel:         4.2.3-300.fc23.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 VMToolsLogPanic at vmtoolsLog.c:207
 #3 VMToolsLog at vmtoolsLog.c:451
 #12 RandR12SetSizeVerify at resolutionRandR12.c:571
 #13 RandR12_SetTopology at resolutionRandR12.c:1014
 #14 SelectResolution at resolutionX11.c:546
 #15 ResolutionSetResolution at resolutionX11.c:179
 #16 ResolutionResolutionSetCB at resolutionSet.c:155
 #17 RpcChannel_Dispatch at rpcChannel.c:405
 #18 RpcInExecRpc at rpcin.c:1317
 #19 RpcInLoop at rpcin.c:1573

Comment 1 Patrick J. Scott 2016-04-21 16:39:24 UTC
Created attachment 1149514 [details]
File: backtrace

Comment 2 Patrick J. Scott 2016-04-21 16:39:25 UTC
Created attachment 1149515 [details]
File: cgroup

Comment 3 Patrick J. Scott 2016-04-21 16:39:28 UTC
Created attachment 1149516 [details]
File: core_backtrace

Comment 4 Patrick J. Scott 2016-04-21 16:39:32 UTC
Created attachment 1149517 [details]
File: dso_list

Comment 5 Patrick J. Scott 2016-04-21 16:39:33 UTC
Created attachment 1149518 [details]
File: environ

Comment 6 Patrick J. Scott 2016-04-21 16:39:34 UTC
Created attachment 1149519 [details]
File: limits

Comment 7 Patrick J. Scott 2016-04-21 16:39:36 UTC
Created attachment 1149520 [details]
File: maps

Comment 8 Patrick J. Scott 2016-04-21 16:39:37 UTC
Created attachment 1149521 [details]
File: mountinfo

Comment 9 Patrick J. Scott 2016-04-21 16:39:42 UTC
Created attachment 1149522 [details]
File: open_fds

Comment 10 Patrick J. Scott 2016-04-21 16:39:43 UTC
Created attachment 1149523 [details]
File: proc_pid_status

Comment 11 Patrick J. Scott 2016-04-21 16:39:44 UTC
Created attachment 1149524 [details]
File: var_log_messages

Comment 12 Fedora End Of Life 2016-11-25 07:25:46 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 '23'.

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 23 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.

Comment 13 Ravindra Kumar 2016-11-30 01:40:59 UTC
This may apply to F24 as well.

Comment 14 Fedora End Of Life 2017-07-25 20:35:39 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 '24'.

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 24 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.

Comment 15 Fedora End Of Life 2017-08-08 14:17:45 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.