/usr/bin/xfce4-session:11:SmsSaveYourself:xfsm_manager_save_yourself_global:xfsm_manager_dbus_shutdown_idled:g_main_dispatch:g_main_context_dispatch

[errors.ubuntu.com bug bridge]

The Ubuntu Error Tracker has been receiving reports about a problem regarding xfce4-session. This problem was most recently seen with package version 4.12.1-3ubuntu3, the problem page at https://errors.ubuntu.com/problem/61b4712608953316cca31251304dd5dff7b16f16 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/.

[Oleg (oleg-redhat-bugs)]

Version-Release number of selected component:
xfce4-session-4.12.1-9.fc24

Additional info:
reporter: libreport-2.7.2
backtrace_rating: 4
cmdline: xfce4-session
crash_function: SmsSaveYourself
executable: /usr/bin/xfce4-session
global_pid: 1140
kernel: 4.8.6-201.fc24.x86_64
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor: Fedora Project
runlevel: N 5
type: CCpp
uid: 1000

Truncated backtrace:
Thread no. 1 (4 frames)
 #0 SmsSaveYourself at sm_manager.c:217
 #1 xfsm_manager_save_yourself_global at xfsm-manager.c:1212
 #2 xfsm_manager_dbus_shutdown_idled at xfsm-manager.c:2032
 #7 gtk_main at gtkmain.c:1268

Potential duplicate: bug 982188

[Oleg (oleg-redhat-bugs)]

Created attachment 1219754
File: backtrace

[Oleg (oleg-redhat-bugs)]

Created attachment 1219755
File: cgroup

[Oleg (oleg-redhat-bugs)]

Created attachment 1219756
File: core_backtrace

[Oleg (oleg-redhat-bugs)]

Created attachment 1219757
File: dso_list

[Oleg (oleg-redhat-bugs)]

Created attachment 1219758
File: environ

[Oleg (oleg-redhat-bugs)]

Created attachment 1219759
File: limits

[Oleg (oleg-redhat-bugs)]

Created attachment 1219760
File: maps

[Oleg (oleg-redhat-bugs)]

Created attachment 1219761
File: mountinfo

[Oleg (oleg-redhat-bugs)]

Created attachment 1219762
File: namespaces

[Oleg (oleg-redhat-bugs)]

Created attachment 1219763
File: open_fds

[Oleg (oleg-redhat-bugs)]

Created attachment 1219764
File: proc_pid_status

[Oleg (oleg-redhat-bugs)]

Created attachment 1219765
File: var_log_messages

[Oleg (oleg-redhat-bugs)]

Created attachment 1219766
File: exploitable

[Mukundan (mukundan-redhat-bugs)]

What were you doing when this crash happened?

Can you please post steps to reproduce the crash if it's not one-off?

[Fedora (fedora-redhat-bugs)]

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 (fedora-redhat-bugs)]

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.

[Sean Davis (bluesabre)]

This issue hasn't been reported since 19.04. Marking as resolved.