Bug 921123

Summary: [abrt] xfce4-power-manager-1.2.0-5.fc18: vasprintf: Process /usr/bin/xfce4-power-manager was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Joe Wrigley <joe>
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: 18CC: admiller, christoph.wickert, mgolindsay, muczyjoe, nesnera
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:e13f38af500c092f4e611fed5df870553b04b33b
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 19:56:10 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: 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

Description Joe Wrigley 2013-03-13 14:05:22 UTC 
Description of problem:
plugged in power adaptor

Version-Release number of selected component:
xfce4-power-manager-1.2.0-5.fc18

Additional info:
backtrace_rating: 4
cmdline:        xfce4-power-manager --restart --sm-client-id 22aa81b7d-9b80-4405-8486-52f510433942
crash_function: vasprintf
executable:     /usr/bin/xfce4-power-manager
kernel:         3.8.2-206.fc18.x86_64
uid:            1000

Truncated backtrace:
Thread no. 1 (9 frames)
 #2 vasprintf at /usr/include/bits/stdio2.h:210
 #3 g_vasprintf at gprintf.c:314
 #4 g_strdup_vprintf at gstrfuncs.c:517
 #5 g_strdup_printf at gstrfuncs.c:543
 #6 xfpm_battery_get_message_from_battery_state at xfpm-battery.c:244
 #7 xfpm_battery_notify at xfpm-battery.c:345
 #8 xfpm_battery_notify_idle at xfpm-battery.c:367
 #13 gtk_main at gtkmain.c:1257
 #14 xfpm_start at xfpm-main.c:318

Potential duplicate: bug 760445
Comment 1 Joe Wrigley 2013-03-13 14:05:26 UTC 
Created attachment 709591 [details]
File: backtrace
Comment 2 Joe Wrigley 2013-03-13 14:05:31 UTC 
Created attachment 709592 [details]
File: cgroup
Comment 3 Joe Wrigley 2013-03-13 14:05:33 UTC 
Created attachment 709593 [details]
File: core_backtrace
Comment 4 Joe Wrigley 2013-03-13 14:05:35 UTC 
Created attachment 709594 [details]
File: dso_list
Comment 5 Joe Wrigley 2013-03-13 14:05:37 UTC 
Created attachment 709595 [details]
File: environ
Comment 6 Joe Wrigley 2013-03-13 14:05:43 UTC 
Created attachment 709596 [details]
File: limits
Comment 7 Joe Wrigley 2013-03-13 14:05:46 UTC 
Created attachment 709597 [details]
File: maps
Comment 8 Joe Wrigley 2013-03-13 14:05:50 UTC 
Created attachment 709598 [details]
File: open_fds
Comment 9 Joe Wrigley 2013-03-13 14:05:52 UTC 
Created attachment 709599 [details]
File: proc_pid_status
Comment 10 Joe Wrigley 2013-03-13 14:05:54 UTC 
Created attachment 709600 [details]
File: var_log_messages
Comment 11 Joe Wrigley 2013-03-19 13:41:13 UTC 
This appears to be a duplicate of 754585

I applied the same patch (again) and the problem no longer occurs.
Comment 12 Christoph Wickert 2013-03-21 13:28:07 UTC 
*** Bug 921966 has been marked as a duplicate of this bug. ***
Comment 13 Fedora End Of Life 2013-12-21 12:07:25 UTC 
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.

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 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 18'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 2014-02-05 19:56:10 UTC 
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.