Bug 881532

Summary: [abrt] xfce4-power-manager-1.0.10-3.fc17: _IceTransWrite: Process /usr/bin/xfce4-power-manager was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: chromaticpan
Component: xfce4-power-managerAssignee: Christoph Wickert <christoph.wickert>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: admiller, christoph.wickert
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:919a3630e5195193e8481026837c2175a7aac71a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-31 22:45:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: core_backtrace
none
File: environ
none
File: backtrace
none
File: limits
none
File: cgroup
none
File: smolt_data
none
File: executable
none
File: maps
none
File: dso_list
none
File: proc_pid_status
none
File: var_log_messages
none
File: open_fds none

Description chromaticpan 2012-11-29 03:18:35 UTC
Version-Release number of selected component:
xfce4-power-manager-1.0.10-3.fc17

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.18
backtrace_rating: 4
cmdline:        xfce4-power-manager --restart --sm-client-id 203d17819-6063-4452-8367-4ee5fe9e415d
crash_function: _IceTransWrite
kernel:         3.6.6-1.fc17.x86_64

truncated backtrace:
:Thread no. 1 (8 frames)
: #0 _IceTransWrite at /usr/include/X11/Xtrans/Xtrans.c:896
: #1 _IceWrite at misc.c:350
: #2 IceFlush at misc.c:78
: #3 SmcCloseConnection at sm_client.c:300
: #4 IA__xfce_sm_client_disconnect at xfce-sm-client.c:1719
: #5 xfce_sm_client_finalize at xfce-sm-client.c:590
: #7 xfpm_manager_finalize at xfpm-manager.c:133
: #9 xfpm_start at xfpm-main.c:240

Comment 1 chromaticpan 2012-11-29 03:18:37 UTC
Created attachment 653965 [details]
File: core_backtrace

Comment 2 chromaticpan 2012-11-29 03:18:39 UTC
Created attachment 653966 [details]
File: environ

Comment 3 chromaticpan 2012-11-29 03:18:40 UTC
Created attachment 653967 [details]
File: backtrace

Comment 4 chromaticpan 2012-11-29 03:18:42 UTC
Created attachment 653968 [details]
File: limits

Comment 5 chromaticpan 2012-11-29 03:18:43 UTC
Created attachment 653969 [details]
File: cgroup

Comment 6 chromaticpan 2012-11-29 03:18:45 UTC
Created attachment 653970 [details]
File: smolt_data

Comment 7 chromaticpan 2012-11-29 03:18:47 UTC
Created attachment 653971 [details]
File: executable

Comment 8 chromaticpan 2012-11-29 03:18:49 UTC
Created attachment 653972 [details]
File: maps

Comment 9 chromaticpan 2012-11-29 03:18:51 UTC
Created attachment 653973 [details]
File: dso_list

Comment 10 chromaticpan 2012-11-29 03:18:53 UTC
Created attachment 653974 [details]
File: proc_pid_status

Comment 11 chromaticpan 2012-11-29 03:18:56 UTC
Created attachment 653975 [details]
File: var_log_messages

Comment 12 chromaticpan 2012-11-29 03:18:58 UTC
Created attachment 653976 [details]
File: open_fds

Comment 13 Fedora End Of Life 2013-07-03 21:33:53 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 
'version' of '17'.

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 prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life.

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 14 Fedora End Of Life 2013-07-31 22:45:39 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.

Thank you for reporting this bug and we are sorry it could not be fixed.