Bug 927861

Summary: [abrt] xfce4-power-manager-1.0.10-4.fc17: vasprintf: Process /usr/bin/xfce4-power-manager was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Andrey V. Henneberg <andrey.henneberg>
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, awjm, christoph.wickert
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:e13f38af500c092f4e611fed5df870553b04b33b
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-31 22:48:46 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: backtrace
none
File: build_ids
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages
none
File: smolt_data none

Description Andrey V. Henneberg 2013-03-26 12:09:07 UTC 
Description of problem:
I disconnected the DC cabel then connected it back and disconnected again. Power manager has been crashed by this sequence.

Version-Release number of selected component:
xfce4-power-manager-1.0.10-4.fc17

Additional info:
backtrace_rating: 4
cmdline:        xfce4-power-manager
crash_function: vasprintf
executable:     /usr/bin/xfce4-power-manager
kernel:         3.8.3-103.fc17.i686.PAE
uid:            1000

Truncated backtrace:
Thread no. 1 (9 frames)
 #2 vasprintf at /usr/include/bits/stdio2.h:199
 #3 g_vasprintf at gprintf.c:314
 #4 g_strdup_vprintf at gstrfuncs.c:509
 #5 g_strdup_printf at gstrfuncs.c:535
 #6 xfpm_battery_get_message_from_battery_state at xfpm-battery.c:242
 #7 xfpm_battery_notify at xfpm-battery.c:343
 #8 xfpm_battery_notify_idle at xfpm-battery.c:365
 #14 gtk_main at gtkmain.c:1257
 #15 xfpm_start at xfpm-main.c:238

Potential duplicate: bug 760445
Comment 1 Andrey V. Henneberg 2013-03-26 12:09:21 UTC 
Created attachment 716474 [details]
File: backtrace
Comment 2 Andrey V. Henneberg 2013-03-26 12:09:59 UTC 
Created attachment 716476 [details]
File: build_ids
Comment 3 Andrey V. Henneberg 2013-03-26 12:10:03 UTC 
Created attachment 716478 [details]
File: cgroup
Comment 4 Andrey V. Henneberg 2013-03-26 12:10:09 UTC 
Created attachment 716481 [details]
File: core_backtrace
Comment 5 Andrey V. Henneberg 2013-03-26 12:10:14 UTC 
Created attachment 716483 [details]
File: dso_list
Comment 6 Andrey V. Henneberg 2013-03-26 12:10:19 UTC 
Created attachment 716484 [details]
File: environ
Comment 7 Andrey V. Henneberg 2013-03-26 12:10:22 UTC 
Created attachment 716485 [details]
File: limits
Comment 8 Andrey V. Henneberg 2013-03-26 12:10:27 UTC 
Created attachment 716486 [details]
File: maps
Comment 9 Andrey V. Henneberg 2013-03-26 12:10:31 UTC 
Created attachment 716487 [details]
File: open_fds
Comment 10 Andrey V. Henneberg 2013-03-26 12:10:35 UTC 
Created attachment 716488 [details]
File: proc_pid_status
Comment 11 Andrey V. Henneberg 2013-03-26 12:10:38 UTC 
Created attachment 716489 [details]
File: var_log_messages
Comment 12 Andrey V. Henneberg 2013-03-26 12:10:42 UTC 
Created attachment 716490 [details]
File: smolt_data
Comment 13 Fedora End Of Life 2013-07-03 21:35:13 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:48:53 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.