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.
Mike.
--
Mike Beattie <[EMAIL PROTECTED]> ZL4DM, IRLP Node 6184
Contentsofsignaturemaysettleduringshipping.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
