On Sun, 02 Mar 2008 09:56:02 -0600 William Pitcock wrote: > Your constant crashing issue is also an issue with libmcs (infact, the > same bug which causes the 2.3GiB config file -- bug #468923). As such, > it will be fixed in the next couple of days.
I upgraded to libmcs1 version 0.7.0-1 from unstable, and I can confirm
that audacious doesn't crash so often any longer and that I haven't seen
any more neon errors.
On the other hand, in a couple of days of usage, I got *one* segfault.
The relevant info in /var/log/kern.log was:
audacious[3357]: segfault at 0 rip 2aaabaa92824 rsp 7fff2ea1f2e0 error 4
I don't know if this means that the bug should be reopened: maybe this
segfault is related to the reported crashes, maybe it's not.
Steps to reproduce: it's hard to tell.
As I said, I only experienced this segfault once.
What I did to get the segfault was:
0. start audacious
1. press play and listen to an Internet radio stream for quite some
time (about half afternoon or so)
2. press stop and leave audacious silent for quite some time (the
rest of the afternoon, dinner time and more)
3. press play: boom! segfault!
--
http://frx.netsons.org/progs/scripts/refresh-pubring.html
New! Version 0.6 available! What? See for yourself!
..................................................... Francesco Poli .
GnuPG key fpr == C979 F34B 27CE 5CD8 DC12 31B5 78F4 279B DD6D FCF4
pgpx3H6lqKog6.pgp
Description: PGP signature
