Bug 1394014

Summary: [abrt] xfce4-power-manager: _g_log_abort(): xfce4-power-manager killed by SIGTRAP
Product: [Fedora] Fedora Reporter: Paul DeStefano <paul.destefano-redhat2>
Component: xfce4-power-managerAssignee: Mukundan Ragavan <nonamedotc>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: christoph.wickert, cristian.ciupitu, kevin, nonamedotc, noobusinghacks
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/46bb1ac1e620b1df8a3e39d72b1dbaf9e36befe2
Whiteboard: abrt_hash:e21640d17e5a7bf5347f2aedee1e33042bb0ba3c;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-08 19:13:39 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: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Paul DeStefano 2016-11-10 20:17:00 UTC
Description of problem:
Just recovered from suspend.

Version-Release number of selected component:
xfce4-power-manager-1.6.0-4.fc24

Additional info:
reporter:       libreport-2.7.2
backtrace_rating: 4
cmdline:        xfce4-power-manager --restart --sm-client-id 223337a87-2c4c-4875-91da-caafb16d5a56
crash_function: _g_log_abort
executable:     /usr/bin/xfce4-power-manager
global_pid:     1546
kernel:         4.8.6-201.fc24.x86_64
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor:     Fedora Project
runlevel:       N 5
type:           CCpp
uid:            1002

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 _g_log_abort at gmessages.c:325
 #10 xfpm_dpms_force_level at xfpm-dpms.c:312
 #11 xfpm_manager_lid_changed_cb at xfpm-manager.c:473
 #12 g_cclosure_marshal_VOID__ENUMv at gmarshal.c:1496
 #13 _g_closure_invoke_va at gclosure.c:867
 #16 xfpm_power_check_lid at xfpm-power.c:284
 #17 xfpm_power_get_properties at xfpm-power.c:339
 #23 g_object_notify_by_spec_internal at gobject.c:1155
 #32 up_exported_daemon_proxy_g_properties_changed at up-daemon-generated.c:1348
 #33 ffi_call_unix64 at ../src/x86/unix64.S:76

Comment 1 Paul DeStefano 2016-11-10 20:17:06 UTC
Created attachment 1219527 [details]
File: backtrace

Comment 2 Paul DeStefano 2016-11-10 20:17:07 UTC
Created attachment 1219528 [details]
File: cgroup

Comment 3 Paul DeStefano 2016-11-10 20:17:08 UTC
Created attachment 1219529 [details]
File: core_backtrace

Comment 4 Paul DeStefano 2016-11-10 20:17:09 UTC
Created attachment 1219530 [details]
File: dso_list

Comment 5 Paul DeStefano 2016-11-10 20:17:10 UTC
Created attachment 1219531 [details]
File: environ

Comment 6 Paul DeStefano 2016-11-10 20:17:11 UTC
Created attachment 1219532 [details]
File: limits

Comment 7 Paul DeStefano 2016-11-10 20:17:12 UTC
Created attachment 1219533 [details]
File: maps

Comment 8 Paul DeStefano 2016-11-10 20:17:13 UTC
Created attachment 1219534 [details]
File: mountinfo

Comment 9 Paul DeStefano 2016-11-10 20:17:14 UTC
Created attachment 1219535 [details]
File: namespaces

Comment 10 Paul DeStefano 2016-11-10 20:17:15 UTC
Created attachment 1219536 [details]
File: open_fds

Comment 11 Paul DeStefano 2016-11-10 20:17:16 UTC
Created attachment 1219537 [details]
File: proc_pid_status

Comment 12 Paul DeStefano 2016-11-10 20:17:17 UTC
Created attachment 1219538 [details]
File: var_log_messages

Comment 13 Mukundan Ragavan 2016-11-11 01:20:20 UTC
Does this crash happen upon every recovery?

Does it seem to depend on any specific sequence/programs?

Comment 14 Paul DeStefano 2016-11-15 06:14:12 UTC
No, not every recover, but 50% since I upgraded to kernel 4.8.6 last week or so.  I'm not pointing at the kernel, but just to give you a time frame.  On the other hand, I also see now that, at least after this crash, backlight control is broken and that has been a kernel thing several times in the past.

I basically just run Firefox and Gnome Terminal and xterm on this system and ssh to other boxen.  So, those are always running.  If it correlates with something else, I haven't noticed, yet.  Today, it happened again, but this time there was also a kernel oops.  I reported that, too, so maybe they are related?

Comment 15 Fedora Admin XMLRPC Client 2017-01-28 15:22:15 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 16 Mukundan Ragavan 2017-01-30 00:46:23 UTC
*** Bug 1373500 has been marked as a duplicate of this bug. ***

Comment 17 Mukundan Ragavan 2017-01-30 00:46:50 UTC
*** Bug 1392319 has been marked as a duplicate of this bug. ***

Comment 18 Fedora End Of Life 2017-07-25 23:50:38 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 19 Fedora End Of Life 2017-08-08 19:13:39 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.