Bug 770160 - [abrt] dreampie-1.1-5.fc14: iter_set_from_byte_offset: Process /usr/bin/python was killed by signal 6 (SIGABRT)
Summary: [abrt] dreampie-1.1-5.fc14: iter_set_from_byte_offset: Process /usr/bin/pytho...
Keywords:
Status: CLOSED DUPLICATE of bug 744857
Alias: None
Product: Fedora
Classification: Fedora
Component: dreampie
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ionuț Arțăriși
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:ca3c912504d22b5ee18de9f3421...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-23 18:23 UTC by David R. Fischer
Modified: 2012-03-30 15:06 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-30 15:06:55 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (32.87 KB, text/plain)
2011-12-23 18:23 UTC, David R. Fischer
no flags Details

Description David R. Fischer 2011-12-23 18:23:42 UTC
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 33656 bytes
cmdline: /usr/bin/python /usr/bin/dreampie
component: dreampie
Attached file: coredump, 98205696 bytes
crash_function: iter_set_from_byte_offset
executable: /usr/bin/python
kernel: 2.6.35.14-106.fc14.x86_64
package: dreampie-1.1-5.fc14
rating: 4
reason: Process /usr/bin/python was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1324662698
uid: 1501

How to reproduce
-----
testing python code mock up

Comment 1 David R. Fischer 2011-12-23 18:23:45 UTC
Created attachment 549378 [details]
File: backtrace

Comment 2 abrt-bot 2012-03-30 15:06:55 UTC
Backtrace analysis found this bug to be similar to bug #744857, closing as duplicate. This bug seems to belong to component pygtk2 or gtk2.

Bugs which were found to be similar to this bug: 
  dreampie: bug #804160
  gourmet: bug #744857, bug #773524
  gtk2: bug #689310

This comment is automatically generated.

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


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