Bug 585582 - [abrt] crash in pino-0.2.4-5.fc12: Process /usr/bin/pino was killed by signal 11 (SIGSEGV)
[abrt] crash in pino-0.2.4-5.fc12: Process /usr/bin/pino was killed by signal...
Status: CLOSED DUPLICATE of bug 581226
Product: Fedora
Classification: Fedora
Component: pino (Show other bugs)
12
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Filipe Rosset
Fedora Extras Quality Assurance
abrt_hash:61f333c55b454cac82ada76560b...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-04-24 17:38 EDT by Ehud Kaldor
Modified: 2010-06-04 12:52 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-06-04 12:52:37 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (30.57 KB, text/plain)
2010-04-24 17:38 EDT, Ehud Kaldor
no flags Details

  None (edit)
Description Ehud Kaldor 2010-04-24 17:38:10 EDT
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: pino
component: pino
executable: /usr/bin/pino
global_uuid: 61f333c55b454cac82ada76560ba62c1a88e852a
kernel: 2.6.32.11-99.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)
Comment 1 Ehud Kaldor 2010-04-24 17:38:11 EDT
Created attachment 408892 [details]
File: backtrace
Comment 2 Siddhesh Poyarekar 2010-05-17 07:08:32 EDT
This is probably a glib bug and the same as bug 547807.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers
Comment 3 Siddhesh Poyarekar 2010-05-17 07:12:10 EDT
Oops, sorry, wrong bug number. Please disregard comment 2.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers
Comment 4 Chen Lei 2010-06-04 12:52:37 EDT

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

Note You need to log in before you can comment on or make changes to this bug.