Bug 602471 - [abrt] crash in homebank-4.2.1-1.fc13: type_check_is_value_type_U: Process /usr/bin/homebank was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in homebank-4.2.1-1.fc13: type_check_is_value_type_U: Process /u...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: homebank
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Filipe Rosset
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:ce09c58310c2fba2dddaa8d90c4...
: 618772 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-09 22:18 UTC by Claudio Rodrigo Pereyra DIaz
Modified: 2010-12-31 10:52 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-31 10:52:10 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (27.54 KB, text/plain)
2010-06-09 22:18 UTC, Claudio Rodrigo Pereyra DIaz
no flags Details

Description Claudio Rodrigo Pereyra DIaz 2010-06-09 22:18:25 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: homebank
component: homebank
crash_function: type_check_is_value_type_U
executable: /usr/bin/homebank
global_uuid: ce09c58310c2fba2dddaa8d90c4b454fccc683a3
kernel: 2.6.33.3-85.fc13.x86_64
package: homebank-4.2.1-1.fc13
rating: 4
reason: Process /usr/bin/homebank was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

Comment 1 Claudio Rodrigo Pereyra DIaz 2010-06-09 22:18:28 UTC
Created attachment 422718 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-09 13:13:50 UTC
*** Bug 618772 has been marked as a duplicate of this bug. ***

Comment 3 Pierre-YvesChibon 2010-12-30 16:38:03 UTC
Can you reproduce this bug ?

Comment 4 Fedora Admin XMLRPC Client 2010-12-30 18:37:55 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 5 Filipe Rosset 2010-12-31 10:52:10 UTC
I'll close this bug as WONTFIX because it's a old version and now we have a new version in our repositories.


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