Bug 1107427 - [abrt] luckybackup: exit(): luckybackup killed by SIGABRT
Summary: [abrt] luckybackup: exit(): luckybackup killed by SIGABRT
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: luckybackup
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Michael J Gruber
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:302075f52ea32ab68144c1db05a...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-10 02:45 UTC by gigalamer
Modified: 2015-06-29 21:02 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 21:02:18 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (62.65 KB, text/plain)
2014-06-10 02:45 UTC, gigalamer
no flags Details
File: cgroup (172 bytes, text/plain)
2014-06-10 02:45 UTC, gigalamer
no flags Details
File: core_backtrace (19.46 KB, text/plain)
2014-06-10 02:45 UTC, gigalamer
no flags Details
File: dso_list (12.29 KB, text/plain)
2014-06-10 02:45 UTC, gigalamer
no flags Details
File: environ (1.93 KB, text/plain)
2014-06-10 02:45 UTC, gigalamer
no flags Details
File: limits (1.29 KB, text/plain)
2014-06-10 02:45 UTC, gigalamer
no flags Details
File: maps (62.41 KB, text/plain)
2014-06-10 02:46 UTC, gigalamer
no flags Details
File: open_fds (230 bytes, text/plain)
2014-06-10 02:46 UTC, gigalamer
no flags Details
File: proc_pid_status (952 bytes, text/plain)
2014-06-10 02:46 UTC, gigalamer
no flags Details
File: var_log_messages (208 bytes, text/plain)
2014-06-10 02:46 UTC, gigalamer
no flags Details

Description gigalamer 2014-06-10 02:45:47 UTC
Version-Release number of selected component:
luckybackup-0.4.8-1.fc20

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/bin/luckybackup
crash_function: exit
executable:     /usr/bin/luckybackup
kernel:         3.14.4-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #23 exit at exit.c:104
 #24 luckyBackupWindow::exitApp at src/luckybackupwindow.cpp:224
 #25 luckyBackupWindow::closeEvent at src/luckybackupwindow.cpp:230
 #26 QWidget::event at kernel/qwidget.cpp:8558
 #27 QMainWindow::event at widgets/qmainwindow.cpp:1478
 #28 QApplicationPrivate::notify_helper at kernel/qapplication.cpp:4565
 #29 QApplication::notify at kernel/qapplication.cpp:4351
 #30 QCoreApplication::notifyInternal at kernel/qcoreapplication.cpp:953
 #31 sendEvent at ../../src/corelib/kernel/qcoreapplication.h:231
 #32 QWidgetPrivate::close_helper at kernel/qwidget.cpp:7955

Potential duplicate: bug 872915

Comment 1 gigalamer 2014-06-10 02:45:52 UTC
Created attachment 906877 [details]
File: backtrace

Comment 2 gigalamer 2014-06-10 02:45:53 UTC
Created attachment 906878 [details]
File: cgroup

Comment 3 gigalamer 2014-06-10 02:45:55 UTC
Created attachment 906879 [details]
File: core_backtrace

Comment 4 gigalamer 2014-06-10 02:45:56 UTC
Created attachment 906880 [details]
File: dso_list

Comment 5 gigalamer 2014-06-10 02:45:58 UTC
Created attachment 906881 [details]
File: environ

Comment 6 gigalamer 2014-06-10 02:45:59 UTC
Created attachment 906882 [details]
File: limits

Comment 7 gigalamer 2014-06-10 02:46:02 UTC
Created attachment 906883 [details]
File: maps

Comment 8 gigalamer 2014-06-10 02:46:03 UTC
Created attachment 906884 [details]
File: open_fds

Comment 9 gigalamer 2014-06-10 02:46:04 UTC
Created attachment 906885 [details]
File: proc_pid_status

Comment 10 gigalamer 2014-06-10 02:46:05 UTC
Created attachment 906886 [details]
File: var_log_messages

Comment 11 Ivan Vlk 2014-08-22 09:32:07 UTC
Another user experienced a similar problem:

I have closed user's GUI and started Root's GUI

reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        /usr/bin/luckybackup
crash_function: exit
executable:     /usr/bin/luckybackup
kernel:         3.15.10-200.fc20.x86_64
package:        luckybackup-0.4.8-1.fc20
reason:         luckybackup killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            0

Comment 12 Fedora End Of Life 2015-05-29 12:04:13 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-29 21:02:18 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.


Note You need to log in before you can comment on or make changes to this bug.