severity 303998 important stop On April 10, 2005 18:07, Mike Beattie wrote: > Yep, I saw this too... finally discovered that it was because I still had > wmxmms running. > > This sort of method *should* reproduce the problem: > > 1) install 1.2.10-2 > 2) install wmxmms > 3) run xmms, and wmxmms. > 4) quit xmms (leave wmxmms running) > 5) upgrade to 1.2.10+cvs20050209-2 > 6) run xmms - should segfault > 7) quit wmxmms > 8) run xmms - should run fine > 9) run wmxmms. > > Any further quits/runs of xmms will be fine. I haven't investigated this > any further than getting it going again, but to me it looks like wmxmms > has the control socket open when xmms starts - something about the > previous version having been running with the current wmxmms causes it to > bomb.
Thanks very much for this information. I'm CCing this to restarting wmxmms resolves the issue. Meanwhile, I'll take the tentative liberty of downgrading the bug to important, since if the problem is a "one-timer" then it really isn't release critical. Cheers, Christopher Martin
pgpyra8LOhz3t.pgp
Description: PGP signature
