Bug 569520 - [abrt] crash in fpm2-0.77-1.fc12: Process /usr/bin/fpm2 was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in fpm2-0.77-1.fc12: Process /usr/bin/fpm2 was killed by signal ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: fpm2
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Aleš Koval
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:e30cd2acfa9fafac41e072f8004...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-01 16:26 UTC by Jeff
Modified: 2010-03-06 03:44 UTC (History)
1 user (show)

Fixed In Version: fpm2-0.78-1.fc12
Clone Of:
Environment:
Last Closed: 2010-03-06 03:44:17 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (17.14 KB, text/plain)
2010-03-01 16:26 UTC, Jeff 		no flags Details
View All

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.
Note You need to log in before you can comment on or make changes to this bug.