Bug 587930

Summary: [abrt] crash in pino-0.2.6-1.fc13: Process /usr/bin/pino was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Bernd Stramm <bernd.stramm>
Component: pinoAssignee: Filipe Rosset <rosset.filipe>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: bernd.stramm, k.weiz, metherid, rosset.filipe, supercyper1
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:2637a2c88aacaa32347ae8d9b966821845b571ea
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-06-04 16:49:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Description Flags
File: backtrace none

Description Bernd Stramm 2010-05-01 16:00:49 UTC
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/pino
component: pino
executable: /usr/bin/pino
global_uuid: 2637a2c88aacaa32347ae8d9b966821845b571ea
package: pino-0.2.6-1.fc13
rating: 4
reason: Process /usr/bin/pino was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

- did not post any twits, just waiting in background
- apparently no new messages at the time of crash

How to reproduce
1. Start pino
2. Wait in background 1-2 hours

Comment 1 Bernd Stramm 2010-05-01 16:00:52 UTC
Created attachment 410697 [details]
File: backtrace

Comment 2 Filipe Rosset 2010-05-02 01:02:57 UTC
pino-0.2.7-1.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 pino'.  You can provide
feedback for this update here:

Comment 3 Karel Klíč 2010-05-25 09:10:06 UTC
*** Bug 587540 has been marked as a duplicate of this bug. ***

Comment 4 Chen Lei 2010-06-04 16:49:14 UTC

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