Bug 601027

Summary: [abrt] crash in gyachi-1.2.4-2.fc13: raise: Process /usr/bin/gyachi was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Dave Gordon <davesama>
Component: gyachiAssignee: Rahul Sundaram <metherid>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: ghosler, metherid
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:92d0f37d266c8fa78269bc6afb0637ef9f96fcb8
Fixed In Version: gyachi-1.2.7-3.fc11 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-06-21 21:31:29 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 Dave Gordon 2010-06-07 03:01:44 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/gyachi
comment: Jus wanted to look at a friend's profile, by right clicking on their name and selecting profile
component: gyachi
crash_function: raise
executable: /usr/bin/gyachi
global_uuid: 92d0f37d266c8fa78269bc6afb0637ef9f96fcb8
kernel: 2.6.33.5-112.fc13.x86_64
package: gyachi-1.2.4-2.fc13
rating: 4
reason: Process /usr/bin/gyachi was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
Comment 1 Dave Gordon 2010-06-07 03:01:46 UTC 
Created attachment 421702 [details]
File: backtrace
Comment 2 Greg Hosler 2010-06-14 14:03:26 UTC 
buffer was too small for printf.

I believe this is fixed in 1.2.7
Comment 3 Fedora Update System 2010-06-14 14:48:59 UTC 
gyachi-1.2.7-3.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/gyachi-1.2.7-3.fc11
Comment 4 Fedora Update System 2010-06-14 15:06:34 UTC 
gyachi-1.2.7-2.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/gyachi-1.2.7-2.fc12
Comment 5 Fedora Update System 2010-06-15 13:13:26 UTC 
gyachi-1.2.8-3.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/gyachi-1.2.8-3.fc13
Comment 6 Fedora Update System 2010-06-15 15:57:57 UTC 
gyachi-1.2.7-3.fc11 has been pushed to the Fedora 11 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 gyachi'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/gyachi-1.2.7-3.fc11
Comment 7 Fedora Update System 2010-06-15 16:00:56 UTC 
gyachi-1.2.7-2.fc12 has been pushed to the Fedora 12 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 gyachi'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/gyachi-1.2.7-2.fc12
Comment 8 Fedora Update System 2010-06-16 17:42:25 UTC 
gyachi-1.2.8-3.fc13 has been pushed to the Fedora 13 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 gyachi'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/gyachi-1.2.8-3.fc13
Comment 9 Fedora Update System 2010-06-21 21:31:21 UTC 
gyachi-1.2.8-3.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 10 Fedora Update System 2010-06-21 21:35:34 UTC 
gyachi-1.2.7-2.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 11 Fedora Update System 2010-06-21 21:44:46 UTC 
gyachi-1.2.7-3.fc11 has been pushed to the Fedora 11 stable repository.  If problems still persist, please make note of it in this bug report.