Bug 581226

Summary: [abrt] crash in pino-0.2.4-5.fc12: Process /usr/bin/pino was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Dichi Al Faridi <dee_chie21>
Component: pinoAssignee: Filipe Rosset <rosset.filipe>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: ehud.kaldor, metherid, rosset.filipe, supercyper1
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:761cea2ab0fca394eea3cf02003d6ad4b67f3c35
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-07-11 14:37:59 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 Dichi Al Faridi 2010-04-11 08:28:38 UTC
abrt 1.0.8 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: pino
comment: just online.. suddenly crash..
component: pino
executable: /usr/bin/pino
kernel: 2.6.32.10-90.fc12.i686
package: pino-0.2.4-5.fc12
rating: 4
reason: Process /usr/bin/pino was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
How to reproduce: pino suddenly crash. I don't know why...

Comment 1 Dichi Al Faridi 2010-04-11 08:28:51 UTC
Created attachment 405791 [details]
File: backtrace

Comment 2 Filipe Rosset 2010-04-12 14:34:04 UTC
pino-0.2.5-1.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 pino'.  You can provide
feedback for this update here:
http://admin.fedoraproject.org/updates/pino-0.2.5-1.fc12

Comment 3 Chen Lei 2010-06-04 16:52:37 UTC
*** Bug 585582 has been marked as a duplicate of this bug. ***

Comment 4 Chen Lei 2010-07-11 14:37:59 UTC

*** This bug has been marked as a duplicate of bug 603854 ***