On Sat, Sep 28, 2013 at 07:27:49PM -0400, Philipp Weis wrote: > On 2013-09-28 00:46, [email protected] <[email protected]> wrote: >> I tried reproducing this error in an environment matching your report, >> but with no success. Does quodlibet suffer the same when you temporarily >> move your ~/.quodlibet directory out of the way? >> >> Also note that quodlibet-plugins 3.x has not yet landed in unstable, >> which might be the next probable cause. If moving ~/.quodlibet helps to >> let quodlibet start OK, what about disabling all plugins/custom >> pipelines if you have set up any? > > I believe this was caused by another missing dependency. It has been > working fine on my system since another package upgrade on Wednesday. > This included gir1.2-atk-1.0 from 2.8 to 2.10, and python-gi and > python-gobject from 3.8.3 to 3.10.0. Downgrading them manually breaks > quodlibet again, but now with a different error message, so I'm not > 100% sure. > > You might want to declare versioned dependencies for these.
It's good news that quodlibet is now working for you because I have not been able to reproduce this issue neither locally nor in testing/unstable chroots[1]. So there must be something else at play here. [1] I have tried some, but not all, of the archive upgrade steps to find out which package might have been broken. Also, the chroot tests were done using gstreamer-alsa not pulseaudio. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
