On Mon, Jul 13, 2009 at 14:38, A. Christine Spang <[email protected]> wrote:
> On Mon, Jul 13, 2009 at 06:41:40AM +0200, David Riebenbauer wrote: > > Package: quodlibet > > Version: 2.1-1 > > Severity: important > > > > I am actually quite surprised to be the first to report this bug. > > Quodlibet won't start for me. Here's the output on the commandline. > > I can reproduce, and I've tracked down which files are causing the > failure. It's definitely a packaging issue, and I think it has something > to do with python-support triggers. I'll look at it more tonight or > tomorrow and get back to you. (A hackish temporary fix would be to kill > /usr/lib/pymodules/python2.5/quodlibet/plugins/editing/__init__.py* and > /usr/lib/pymodules/python2.5/quodlibet/plugins/songsmenu/__init__.py*.) > > It seems to not occur sometimes depending on what packages out of > exfalso, quodlibet, quodlibet-plugins, and quodlibet-ext are installed, > which might explain why no one else has reported this yet. For what it's worth, I just came back from a weekend trip, I upgraded all four packages to the latest version, and I'm seeing this now. However, I didn't want to report this when David had already reported it. Thanks for promptly looking into this,
