I experienced this bug too with a python plugin written myself. In my plugin I created a rather complex object in the plugin's __init__ method. This object had a start and stop method I called in the plugin's activate and deactivate methods. The problem was that the object never got dereferenced (set to 'None') in this design. I assumed it gets dereferenced when the plugin object itself gets dereferenced somewhere in the Rhythmbox code - obviously this was wrong. I prevented this bug by creating _all_ objects within the activate method and dereferencing _all_ objects in the deactivate method (indeed the Rhythmbox plugin writing guide recommends to handle references this way).
Based on this experience I would guess the bug is not related to Rhythmbox but to a Rhythmbox plugin. -- rhythmbox crashed with SIGSEGV in PyErr_Fetch() https://bugs.launchpad.net/bugs/274183 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
