Bug 693301 - [abrt] exaile-0.3.2.1-1.fc14: gtk_text_iter_make_real: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
Summary: [abrt] exaile-0.3.2.1-1.fc14: gtk_text_iter_make_real: Process /usr/bin/pytho...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gtk2
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:eea06900e8ba68926d29dcce8bc...
: 710365 829796 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-04 09:29 UTC by mimetaster
Modified: 2013-01-07 15:26 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 14:25:27 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (99.04 KB, text/plain)
2011-04-04 09:29 UTC, mimetaster
no flags Details

Description mimetaster 2011-04-04 09:29:36 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 101417 bytes
cmdline: python /usr/lib/python2.7/site-packages/exaile/exaile.py --datadir=/usr/share/exaile/data --startgui
component: exaile
Attached file: coredump, 112136192 bytes
crash_function: gtk_text_iter_make_real
executable: /usr/bin/python
kernel: 2.6.35.11-83.fc14.x86_64
package: exaile-0.3.2.1-1.fc14
rating: 4
reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1301862727
uid: 500

How to reproduce
-----
1. Open Exaile
2. Play the playlist with tracks shuffling and repeat mode on
3. bug occured when Exaile switched form a song to the next one

Comment 1 mimetaster 2011-04-04 09:29:38 UTC
Created attachment 489724 [details]
File: backtrace

Comment 2 Deji Akingunola 2011-04-04 14:47:53 UTC
Could this be a bug in gtk? re-assigning to gtk2.

Comment 3 abrt-bot 2012-03-20 18:08:05 UTC
Backtrace analysis found this bug to be similar to some already closed bugs from other components. You might want to check those bugs for additional information.

Bugs which were found to be similar to this bug: 
  exaile: bug #650695, bug #675788, bug #694279, bug #706833
  gxine: bug #551187
  pygtk2: bug #542064

This comment is automatically generated.

Comment 4 Robin Lee 2012-06-08 01:34:16 UTC
*** Bug 829796 has been marked as a duplicate of this bug. ***

Comment 5 Robin Lee 2012-06-08 01:35:30 UTC
*** Bug 820602 has been marked as a duplicate of this bug. ***

Comment 6 Robin Lee 2012-06-08 01:41:00 UTC
*** Bug 710365 has been marked as a duplicate of this bug. ***

Comment 7 Fedora End Of Life 2012-08-16 14:25:30 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 8 Brian J. Murrell 2013-01-07 15:26:38 UTC
Can we get this bug opened back up and have it's Version(s) field updated to FC18 since I am seeing this in FC18 now?


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