On Sun, 10 Apr 2005, Christopher Martin wrote: > 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.
Package: xmms Version: 1.2.10+cvs20050209-2 All right. Today, I can no longer reproduce the segfault. The other day I must have had the wmxmms (from the previous package version) running while I installed and started the new xmms version. I'm now running both wmxmms and xmms comming from the same package and I don't see the segfault. Maybe a warning (about killing a running wmxmms) when installing a new xmms package wouldn't be such a bad idea. Nevertheless, I did notice this: ,---- | Getting status for xmms... | Verifying package integrity... | There may be a problem with your installation of xmms; | the following files appear to be missing or changed: | | Do you still want to file a report [y|N|q|?]? `---- comming out of 'reportbug'. There might be something odd with either reportbug or the files in the xmms package. You may want to downgrade the bug to 'normal'. Cheers, Cristian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
