Bug 1631782

Summary: [abrt] xfce4-session: SmsSaveYourself(): xfce4-session killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Фукидид <fukidid>
Component: xfce4-sessionAssignee: Kevin Fenzi <kevin>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 28CC: kevin, nonamedotc
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/20e35fe063b43316ca88c033d8764d0f3894ca69
Whiteboard: abrt_hash:7591054365cf59d483581cc2fa22f3dad2fa96b3;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-28 22:32: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: cpuinfo
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status
none
File: exploitable none

Description Фукидид 2018-09-21 14:42:35 UTC
Version-Release number of selected component:
xfce4-session-4.12.1-13.fc28

Additional info:
reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        xfce4-session
crash_function: SmsSaveYourself
executable:     /usr/bin/xfce4-session
journald_cursor: s=d7b8957c8cb94d40adb6987cbdb79311;i=36c6a;b=c31e1383083c43e29dffefeabf9ff5b6;m=5ec7abe94;t=5719d15ef8b5e;x=68d74c00997a83bb
kernel:         4.17.6-200.fc28.x86_64
rootdir:        /
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
 #8 gtk_main at gtkmain.c:1270

Potential duplicate: bug 1394213

Comment 1 Фукидид 2018-09-21 14:42:41 UTC
Created attachment 1485601 [details]
File: backtrace

Comment 2 Фукидид 2018-09-21 14:42:42 UTC
Created attachment 1485602 [details]
File: cgroup

Comment 3 Фукидид 2018-09-21 14:42:43 UTC
Created attachment 1485603 [details]
File: core_backtrace

Comment 4 Фукидид 2018-09-21 14:42:45 UTC
Created attachment 1485604 [details]
File: cpuinfo

Comment 5 Фукидид 2018-09-21 14:42:46 UTC
Created attachment 1485605 [details]
File: dso_list

Comment 6 Фукидид 2018-09-21 14:42:47 UTC
Created attachment 1485606 [details]
File: environ

Comment 7 Фукидид 2018-09-21 14:42:49 UTC
Created attachment 1485607 [details]
File: limits

Comment 8 Фукидид 2018-09-21 14:42:52 UTC
Created attachment 1485608 [details]
File: maps

Comment 9 Фукидид 2018-09-21 14:42:54 UTC
Created attachment 1485609 [details]
File: mountinfo

Comment 10 Фукидид 2018-09-21 14:42:55 UTC
Created attachment 1485610 [details]
File: open_fds

Comment 11 Фукидид 2018-09-21 14:42:57 UTC
Created attachment 1485611 [details]
File: proc_pid_status

Comment 12 Фукидид 2018-09-21 14:42:58 UTC
Created attachment 1485612 [details]
File: exploitable

Comment 13 Ben Cotton 2019-05-02 20:52:00 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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 14 Ben Cotton 2019-05-28 22:32:10 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.