Bug 606686

Summary: [abrt] crash in pino-0.2.10-1.fc12: raise: Process /usr/bin/pino was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Gabriel PREDA <gabriel>
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: bhowmick, dek-09q, giallu, jl.deloos, mackuzzz, metherid, rosset.filipe, supercyper1
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:b4b8098d2166198822af8087d0dbe9c60649ea3e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-07-11 14:41:45 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 Gabriel PREDA 2010-06-22 08:55:32 UTC 
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: pino
component: pino
crash_function: raise
executable: /usr/bin/pino
global_uuid: b4b8098d2166198822af8087d0dbe9c60649ea3e
kernel: 2.6.32.14-127.fc12.x86_64
package: pino-0.2.10-1.fc12
rating: 4
reason: Process /usr/bin/pino was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)
How to reproduce: Just open Pino...

comment
-----
After this behaviour was usual I removed pino (with yum) then looked for every file generated by pino (updatedb, locate... rm -Rf )... to simulate a fresh install...

Even with this effort pino crashed... on my work computer.

On my home computer with F13 it works ok.
Comment 1 Gabriel PREDA 2010-06-22 08:55:34 UTC 
Created attachment 425861 [details]
File: backtrace
Comment 2 Chen Lei 2010-06-22 11:22:21 UTC 
*** Bug 606657 has been marked as a duplicate of this bug. ***
Comment 3 Chen Lei 2010-06-22 11:22:49 UTC 
*** Bug 606221 has been marked as a duplicate of this bug. ***
Comment 4 Chen Lei 2010-06-22 11:24:16 UTC 
*** Bug 605503 has been marked as a duplicate of this bug. ***
Comment 5 Chen Lei 2010-06-22 11:26:54 UTC 
*** Bug 604208 has been marked as a duplicate of this bug. ***
Comment 6 Chen Lei 2010-06-22 11:27:03 UTC 
*** Bug 605589 has been marked as a duplicate of this bug. ***
Comment 7 Chen Lei 2010-06-22 11:27:44 UTC 
*** Bug 603272 has been marked as a duplicate of this bug. ***
Comment 8 Chen Lei 2010-06-22 11:29:07 UTC 
*** Bug 604009 has been marked as a duplicate of this bug. ***
Comment 9 Chen Lei 2010-06-22 11:30:25 UTC 
*** Bug 604510 has been marked as a duplicate of this bug. ***
Comment 10 Chen Lei 2010-06-22 11:33:14 UTC 
*** Bug 604511 has been marked as a duplicate of this bug. ***
Comment 11 Chen Lei 2010-06-22 11:34:32 UTC 
*** Bug 587355 has been marked as a duplicate of this bug. ***
Comment 12 Chen Lei 2010-06-23 06:20:49 UTC 
*** Bug 607070 has been marked as a duplicate of this bug. ***
Comment 13 Gianluca Sforna 2010-06-29 14:57:12 UTC 
Looks like bug 603854 is also a duplicate of this one.

Please have a look at the patch in upstream tracker:
http://code.google.com/p/pino-twitter/issues/attachmentText?id=259&aid=-8820533392689778435&name=0.2.10-gthread.patch
Comment 14 dekellum 2010-07-01 18:10:48 UTC 
I have the same problem. Temp workaround to get pino working again for me was to uninstall from yum and replace pino with this build:

http://code.google.com/p/pino-twitter/downloads/detail?name=pino-0.2.8-1.fc12.al.i686.rpm
Comment 15 Gabriel PREDA 2010-07-07 07:22:10 UTC 
I also confirm no crash so far on Fedora 12 with pino 0.2.9 from sources from http://code.google.com/p/pino-twitter/downloads/detail?name=pino-0.2.9.tar.bz2&can=2&q=label%3DSource&sort=-filename
Comment 16 Chen Lei 2010-07-11 14:41:45 UTC 

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