Bug 569520

Summary: [abrt] crash in fpm2-0.77-1.fc12: Process /usr/bin/fpm2 was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Jeff <1nomdeplume>
Component: fpm2Assignee: Aleš Koval <als>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: als
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:e30cd2acfa9fafac41e072f80049a9d5334c0a86
Fixed In Version: fpm2-0.78-1.fc12 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-03-06 03:44:17 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 Jeff 2010-03-01 16:26:34 UTC 
abrt 1.0.7 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: fpm2
comment: For this backtrace I entered a made up password and a random text file for my keyfile for security, but the behavior is exactly the same with the correct password and keyfile.
component: fpm2
executable: /usr/bin/fpm2
kernel: 2.6.31.12-174.2.22.fc12.i686.PAE
package: fpm2-0.77-1.fc12
rating: 4
reason: Process /usr/bin/fpm2 was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. Enter Password and choose keyfile
2. Click OK
3. Program crashes
Comment 1 Jeff 2010-03-01 16:26:36 UTC 
Created attachment 397107 [details]
File: backtrace
Comment 2 Fedora Update System 2010-03-03 13:26:30 UTC 
fpm2-0.78-1.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/fpm2-0.78-1.fc12
Comment 3 Jeff 2010-03-03 14:51:40 UTC 
Downgrading to 0.75 works until the new version is released.
Comment 4 Fedora Update System 2010-03-06 03:44:12 UTC 
fpm2-0.78-1.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.