Bug 588068 - [abrt] crash in pino-0.2.5-1.fc12: Process /usr/bin/pino was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in pino-0.2.5-1.fc12: Process /usr/bin/pino was killed by signal...
Status: CLOSED DUPLICATE of bug 587355
Alias: None
Product: Fedora
Classification: Fedora
Component: pino
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Filipe Rosset
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:7376289352ed0a933f5ba44d1e7...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-02 13:54 UTC by Frédéric Logier
Modified: 2010-06-04 16:50 UTC (History)
3 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2010-06-04 16:50:56 UTC

Attachments (Terms of Use)
File: backtrace (60.79 KB, text/plain)
2010-05-02 13:54 UTC, Frédéric Logier 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Frédéric Logier 2010-05-02 13:54:18 UTC 
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: pino
component: pino
executable: /usr/bin/pino
global_uuid: 7376289352ed0a933f5ba44d1e7a009768c91f85
kernel: 2.6.32.11-99.fc12.x86_64
package: pino-0.2.5-1.fc12
rating: 4
reason: Process /usr/bin/pino was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
Comment 1 Frédéric Logier 2010-05-02 13:54:23 UTC 
Created attachment 410800 [details]
File: backtrace
Comment 2 Filipe Rosset 2010-05-02 15:27:45 UTC 
pino-0.2.7-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.7-1.fc12
Comment 3 Frédéric Logier 2010-05-03 10:14:35 UTC 
indeed this version works better, thanks
Comment 4 Chen Lei 2010-06-04 16:50:56 UTC 

*** This bug has been marked as a duplicate of bug 587355 ***
Note You need to log in before you can comment on or make changes to this bug.