Bug 551371 - Assertion failure in PyGILState_Release inside g_closure_invoke running /usr/bin/pybackpack
Summary: Assertion failure in PyGILState_Release inside g_closure_invoke running /usr/...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: python
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Dave Malcolm
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:65b16b746af896f6f1cf324b979...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-30 10:16 UTC by Luya Tshimbalanga
Modified: 2010-12-04 01:04 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-12-04 01:04:47 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (18.65 KB, text/plain)
2009-12-30 10:16 UTC, Luya Tshimbalanga
no flags Details

Description Luya Tshimbalanga 2009-12-30 10:16:01 UTC
abrt 1.0.0 detected a crash.

Comment: Hard to reproduce this back trace
Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/pybackpack
component: python
executable: /usr/bin/python
kernel: 2.6.31.6-166.fc12.x86_64
package: python-2.6.2-2.fc12
rating: 3
reason: Process was terminated by signal 6

Comment 1 Luya Tshimbalanga 2009-12-30 10:16:03 UTC
Created attachment 380920 [details]
File: backtrace

Comment 2 Dave Malcolm 2010-01-04 18:50:27 UTC
Thank you for reporting this bug.

Do you have any ideas on how to reproduce this problem?  If you run the program from a terminal, is an error message printed?

What is the output of: rpm -q pybackpack pygtk2 gtk2

Looking at the backtrace, it looks like an assertion failed inside frame 2 of thread #1 inside PyGILState_Release.

If I'm reading it correctly, thread #1 is releasing its last claim upon the GIL, but when that claim was grabbed, it was already locked.

Reassigning component from "python" to "pybackpack" in case the pybackpack maintainer has seen this before.  This might be a bug in python, pybackpack or pygtk.

Comment 3 Luya Tshimbalanga 2010-01-06 00:03:44 UTC
You can view #552732 as I have set up a custom backup but pybackpack is still working. I am not sure if it is a duplicate.

Resulting output:
$ rpm -q pybackpack pygtk2 gtk2
pybackpack-0.5.7-3.fc12.noarch
pygtk2-2.16.0-1.fc12.i686
gtk2-2.18.5-4.fc12.i686

Comment 4 Bug Zapper 2010-11-04 02:15:02 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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 5 Bug Zapper 2010-12-04 01:04:47 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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