Bug 665712

Summary: [abrt] bibletime-2.7.3-2.fc14: set: Process /usr/bin/bibletime was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: mariolinux
Component: bibletimeAssignee: David Anderson <fedora-packaging2>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: dakingun, ehicks, fedora-packaging2, jameshusby, Robert-Martin
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:7e83e01a4a4e4745a6ec4b977c5a702ebf80f451
Fixed In Version: bibletime-2.8.0-1.fc14 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-01-14 20:31: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

Description mariolinux 2010-12-26 10:47:31 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: bibletime
component: bibletime
crash_function: set
executable: /usr/bin/bibletime
kernel: 2.6.35.10-72.fc14.x86_64
package: bibletime-2.7.3-2.fc14
rating: 4
reason: Process /usr/bin/bibletime was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1293360005
uid: 500

How to reproduce
-----
1. Installing or upgrading something in the library (I presume)
2.
3.
Comment 1 mariolinux 2010-12-26 10:47:34 UTC 
Created attachment 470720 [details]
File: backtrace
Comment 2 E. Hicks 2010-12-30 08:26:20 UTC 
Package: bibletime-2.7.3-2.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.Opened the bookshelf
2.Tabbed over to xiphos
3.It crashed


Comment
-----
Only xiphos does this - the others I have in there work just fine
Comment 3 Robert Martin 2010-12-30 16:14:00 UTC 
Package: bibletime-2.7.3-2.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.Opened Bibletime.
2.Proceeded to "Bookshelf Manager".
3.Clicked on Xiphos respository tab.


Comment
-----
Once I clicked on the Xiphos repository tab, in order to download the files, the application crashed.
Comment 4 jameshusby 2011-01-02 16:05:49 UTC 
Package: bibletime-2.7.3-2.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Moved Mag toolbar from top to left side
2. Bibletime crashed 
3. Reopened Bibletime and can no longer move toolbar. It is stuck on top and won't redock left
Comment 5 jameshusby 2011-01-02 16:09:11 UTC 
My bad... It took so long to report the bug that I actually forgot what I was doing at the time.

I also was in the bookshelf under Xiphos when the crash occurred. The Mag toolbar is now stuck on the top of the screen as I reported above however.
Comment 6 Fedora Update System 2011-01-04 18:02:09 UTC 
bibletime-2.8.0-1.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/bibletime-2.8.0-1.fc14
Comment 7 Fedora Update System 2011-01-05 21:19:49 UTC 
bibletime-2.8.0-1.fc14 has been pushed to the Fedora 14 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update bibletime'.  You can provide feedback for this update here: https://admin.fedoraproject.org/updates/bibletime-2.8.0-1.fc14
Comment 8 jameshusby 2011-01-06 15:13:55 UTC 
Package: bibletime-2.7.3-2.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. opened Xiphos in bookshelf
2.
3.
Comment 9 jameshusby 2011-01-07 03:14:59 UTC 
Package: bibletime-2.7.3-2.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. opened Xiphos in bookshelf
2.
3.
Comment 10 Fedora Update System 2011-01-14 20:31:06 UTC 
bibletime-2.8.0-1.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.