Hide Forgot
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
Created attachment 1219527 [details] File: backtrace
Created attachment 1219528 [details] File: cgroup
Created attachment 1219529 [details] File: core_backtrace
Created attachment 1219530 [details] File: dso_list
Created attachment 1219531 [details] File: environ
Created attachment 1219532 [details] File: limits
Created attachment 1219533 [details] File: maps
Created attachment 1219534 [details] File: mountinfo
Created attachment 1219535 [details] File: namespaces
Created attachment 1219536 [details] File: open_fds
Created attachment 1219537 [details] File: proc_pid_status
Created attachment 1219538 [details] File: var_log_messages
Does this crash happen upon every recovery? Does it seem to depend on any specific sequence/programs?
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?
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
*** Bug 1373500 has been marked as a duplicate of this bug. ***
*** Bug 1392319 has been marked as a duplicate of this bug. ***
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.
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.