Bug 589284 - [abrt] crash in pino-0.2.6-1.fc12: g_hash_table_lookup_node: Process /usr/bin/pino was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in pino-0.2.6-1.fc12: g_hash_table_lookup_node: Process /usr/bin...
Keywords:
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:a6efedcafaa460fc8ea3d749dea...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-05 18:28 UTC by Dennis Appelon Nielsen
Modified: 2010-05-25 10:17 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-25 10:17:18 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (24.30 KB, text/plain)
2010-05-05 18:28 UTC, Dennis Appelon Nielsen 		no flags Details
View All

Description Dennis Appelon Nielsen 2010-05-05 18:28:50 UTC 
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: pino
comment: It comes when Pino have runed for some time, and then "boom" it is crashed
component: pino
crash_function: g_hash_table_lookup_node
executable: /usr/bin/pino
global_uuid: a6efedcafaa460fc8ea3d749dea8e42a392ad6dd
kernel: 2.6.32.11-99.fc12.x86_64
package: pino-0.2.6-1.fc12
rating: 4
reason: Process /usr/bin/pino was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1.start Pino
2.Wait for some random time
3.
Comment 1 Dennis Appelon Nielsen 2010-05-05 18:28:58 UTC 
Created attachment 411706 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 10:17:18 UTC 

*** This bug has been marked as a duplicate of bug 587355 ***
Comment 3 Karel Klíč 2010-05-25 10:17:18 UTC 
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #587355.

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