Bug 548730 - PyGILState_Release assertion failure in bonobo call when running hamster-applet
Summary: PyGILState_Release assertion failure in bonobo call when running hamster-applet
Keywords:
Status: CLOSED DUPLICATE of bug 544344
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:71b9fddcd2b58f31c50b540654b...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-18 12:18 UTC by Marcus Alves Grando
Modified: 2009-12-23 18:00 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-12-23 18:00:23 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (35.04 KB, text/plain)
2009-12-18 12:18 UTC, Marcus Alves Grando
no flags Details

Description Marcus Alves Grando 2009-12-18 12:18:45 UTC
abrt 1.0.2 detected a crash.

How to reproduce
-----
1.Update to latest update-testing
2.Add hamster-applet to gnome-panel
3.Crash


Attached file: backtrace
cmdline: python /usr/lib64/hamster-applet/hamster-applet --oaf-activate-iid=OAFIID:Hamster_Applet_Factory --oaf-ior-fd=25
component: python
executable: /usr/bin/python
kernel: 2.6.31.8-171.fc12.x86_64
package: python-2.6.2-2.fc12
rating: 4
reason: Process was terminated by signal 6 (Aborted)

Comment 1 Marcus Alves Grando 2009-12-18 12:18:48 UTC
Created attachment 379200 [details]
File: backtrace

Comment 2 Dave Malcolm 2009-12-23 17:59:10 UTC
Thank you for reporting this bug.

How reproducible is this problem?  If you run the program from a terminal, is an error message printed?

What is the output from running the following command?
  rpm -q hamster-applet glib2 libbonobo gnome-panel pygtk2

Thanks!

Looking at the backtrace, it looks like the "oldstate == PyGILState_UNLOCKED" assertion failed inside frame 2 of thread #1 inside PyGILState_Release.

This was whilst responding to a _ORBIT_skel_small_Bonobo_Control_setFrame request (see frame #14) that led to a call to impl_Bonobo_Control_setFrame (frame #12).


Thread #3 is also running a Gtk main loop; thread #3 is waiting on a mutex, somewhere inside libglib.

Comment 3 Dave Malcolm 2009-12-23 18:00:23 UTC

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


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