Bug 1075591

Summary: [abrt] xfce4-session: SmsSaveYourself(): xfce4-session killed by SIGSEGV
Product: [Fedora] Fedora Reporter: John Duchek <johnduchek>
Component: xfce4-sessionAssignee: Kevin Fenzi <kevin>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: kevin, nonamedotc
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/f66086af7eca94d952563cebeab84848ee555817
Whiteboard: abrt_hash:7591054365cf59d483581cc2fa22f3dad2fa96b3
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-30 00:56:51 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 John Duchek 2014-03-12 12:39:32 UTC
Description of problem:
I had updated my system using yum extender yesterday.  When I booted up this morning this occurred.  It happened on boot up.

Version-Release number of selected component:
xfce4-session-4.10.1-3.fc20

Additional info:
reporter:       libreport-2.1.12
backtrace_rating: 4
cmdline:        xfce4-session
crash_function: SmsSaveYourself
executable:     /usr/bin/xfce4-session
kernel:         3.13.5-200.fc20.x86_64
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:1180
 #2 xfsm_manager_dbus_shutdown_idled at xfsm-manager.c:1991
 #7 gtk_main at gtkmain.c:1257

Potential duplicate: bug 879629

Comment 1 John Duchek 2014-03-12 12:39:39 UTC
Created attachment 873513 [details]
File: backtrace

Comment 2 John Duchek 2014-03-12 12:39:41 UTC
Created attachment 873514 [details]
File: cgroup

Comment 3 John Duchek 2014-03-12 12:39:43 UTC
Created attachment 873515 [details]
File: core_backtrace

Comment 4 John Duchek 2014-03-12 12:39:46 UTC
Created attachment 873516 [details]
File: dso_list

Comment 5 John Duchek 2014-03-12 12:39:48 UTC
Created attachment 873517 [details]
File: environ

Comment 6 John Duchek 2014-03-12 12:39:49 UTC
Created attachment 873518 [details]
File: limits

Comment 7 John Duchek 2014-03-12 12:39:51 UTC
Created attachment 873519 [details]
File: maps

Comment 8 John Duchek 2014-03-12 12:39:53 UTC
Created attachment 873520 [details]
File: open_fds

Comment 9 John Duchek 2014-03-12 12:39:55 UTC
Created attachment 873521 [details]
File: proc_pid_status

Comment 10 John Duchek 2014-03-12 12:39:57 UTC
Created attachment 873522 [details]
File: var_log_messages

Comment 11 Kevin Fenzi 2014-03-12 14:31:21 UTC
Looks like something failed to save right on shutdown. 

Did you notice any problems the last time you logged out/shutdown?

Comment 12 Fedora End Of Life 2015-05-29 11:13:56 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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 13 Fedora End Of Life 2015-06-30 00:56:51 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.