Bug 1607255

Summary: [abrt] deja-dup: __libc_sigaction(): deja-dup-monitor killed by SIGABRT
Product: [Fedora] Fedora Reporter: Luya Tshimbalanga <luya>
Component: deja-dupAssignee: Gwyn Ciesla <gwync>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 28CC: fedora, gwync, jitesh.1337, walter.pete
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/15df353539c2dc1ed11b58c66cdb7331bc51de34
Whiteboard: abrt_hash:a91f11ce84133b3e5a8f73a55269705d3baa2800;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-28 23:08:15 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

Description Luya Tshimbalanga 2018-07-23 05:53:18 UTC 
Description of problem:
Crashed during log in session and after resetting the settings to default

Version-Release number of selected component:
deja-dup-38.0-2.fc28

Additional info:
reporter:       libreport-2.9.5
backtrace_rating: 3
cmdline:        /usr/libexec/deja-dup/deja-dup-monitor
crash_function: __libc_sigaction
executable:     /usr/libexec/deja-dup/deja-dup-monitor
journald_cursor: s=510d72399253427f91fdb0af0fcd3af6;i=26c43;b=64864f087de5442db580efdb36c169aa;m=2747e5721;t=571a3fee932c7;x=ffa9aab4dd42e1de
kernel:         4.17.7-200.fc28.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 1 Luya Tshimbalanga 2018-07-23 05:53:24 UTC 
Created attachment 1469866 [details]
File: backtrace
Comment 2 Luya Tshimbalanga 2018-07-23 05:53:26 UTC 
Created attachment 1469867 [details]
File: cgroup
Comment 3 Luya Tshimbalanga 2018-07-23 05:53:27 UTC 
Created attachment 1469868 [details]
File: core_backtrace
Comment 4 Luya Tshimbalanga 2018-07-23 05:53:28 UTC 
Created attachment 1469869 [details]
File: cpuinfo
Comment 5 Luya Tshimbalanga 2018-07-23 05:53:30 UTC 
Created attachment 1469870 [details]
File: dso_list
Comment 6 Luya Tshimbalanga 2018-07-23 05:53:31 UTC 
Created attachment 1469871 [details]
File: environ
Comment 7 Luya Tshimbalanga 2018-07-23 05:53:32 UTC 
Created attachment 1469872 [details]
File: limits
Comment 8 Luya Tshimbalanga 2018-07-23 05:53:34 UTC 
Created attachment 1469873 [details]
File: maps
Comment 9 Luya Tshimbalanga 2018-07-23 05:53:35 UTC 
Created attachment 1469874 [details]
File: mountinfo
Comment 10 Luya Tshimbalanga 2018-07-23 05:53:36 UTC 
Created attachment 1469875 [details]
File: open_fds
Comment 11 Luya Tshimbalanga 2018-07-23 05:53:38 UTC 
Created attachment 1469876 [details]
File: proc_pid_status
Comment 12 Ben Cotton 2019-05-02 20:26:27 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 13 Ben Cotton 2019-05-28 23:08:15 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.