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.
Created attachment 425861 [details] File: backtrace
*** Bug 606657 has been marked as a duplicate of this bug. ***
*** Bug 606221 has been marked as a duplicate of this bug. ***
*** Bug 605503 has been marked as a duplicate of this bug. ***
*** Bug 604208 has been marked as a duplicate of this bug. ***
*** Bug 605589 has been marked as a duplicate of this bug. ***
*** Bug 603272 has been marked as a duplicate of this bug. ***
*** Bug 604009 has been marked as a duplicate of this bug. ***
*** Bug 604510 has been marked as a duplicate of this bug. ***
*** Bug 604511 has been marked as a duplicate of this bug. ***
*** Bug 587355 has been marked as a duplicate of this bug. ***
*** Bug 607070 has been marked as a duplicate of this bug. ***
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
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
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
*** This bug has been marked as a duplicate of bug 603854 ***