Bug 928551

Summary: [abrt] bibletime-2.9.1-3.fc18: (anonymous namespace)::myMessageOutput(enum QtMsgType, const char *): Process /usr/bin/bibletime was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: David Le Sage <dlesage>
Component: bibletimeAssignee: Deji Akingunola <dakingun>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: dakingun
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:23bd24f4046f5cc2a40a872ea428c86d284ac1eb
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 20:20:31 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: smolt_data
none
File: var_log_messages none

Description David Le Sage 2013-03-27 22:03:54 UTC 
Description of problem:
Crashed on launch.

Version-Release number of selected component:
bibletime-2.9.1-3.fc18

Additional info:
backtrace_rating: 4
cmdline:        /usr/bin/bibletime
crash_function: (anonymous namespace)::myMessageOutput(enum QtMsgType, const char *)
executable:     /usr/bin/bibletime
kernel:         3.8.4-202.fc18.x86_64
uid:            1000
ureports_counter: 1
xsession_errors: 

Truncated backtrace:
Thread no. 1 (4 frames)
 #2 (anonymous namespace)::myMessageOutput(enum QtMsgType, const char *) at /usr/src/debug/bibletime-2.9.1/src/main.cpp:174
 #3 qt_message_output at global/qglobal.cpp:2269
 #4 qt_message(enum QtMsgType, const char *, typedef __va_list_tag __va_list_tag *) at global/qglobal.cpp:2369
 #5 qFatal at global/qglobal.cpp:2552
Comment 1 David Le Sage 2013-03-27 22:03:58 UTC 
Created attachment 717320 [details]
File: backtrace
Comment 2 David Le Sage 2013-03-27 22:04:01 UTC 
Created attachment 717321 [details]
File: cgroup
Comment 3 David Le Sage 2013-03-27 22:04:04 UTC 
Created attachment 717322 [details]
File: core_backtrace
Comment 4 David Le Sage 2013-03-27 22:04:07 UTC 
Created attachment 717323 [details]
File: dso_list
Comment 5 David Le Sage 2013-03-27 22:04:11 UTC 
Created attachment 717324 [details]
File: environ
Comment 6 David Le Sage 2013-03-27 22:04:13 UTC 
Created attachment 717325 [details]
File: limits
Comment 7 David Le Sage 2013-03-27 22:04:17 UTC 
Created attachment 717326 [details]
File: maps
Comment 8 David Le Sage 2013-03-27 22:04:22 UTC 
Created attachment 717327 [details]
File: open_fds
Comment 9 David Le Sage 2013-03-27 22:04:25 UTC 
Created attachment 717328 [details]
File: proc_pid_status
Comment 10 David Le Sage 2013-03-27 22:04:30 UTC 
Created attachment 717329 [details]
File: smolt_data
Comment 11 David Le Sage 2013-03-27 22:04:33 UTC 
Created attachment 717330 [details]
File: var_log_messages
Comment 12 Fedora End Of Life 2013-12-21 12:31:37 UTC 
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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 2014-02-05 20:20:31 UTC 
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.