[Pkg-audacious-maintainers] Bug#512682: audacious: Segfault on startup - skin problem?

Adam Majer adamm at zombino.com
Thu Jun 25 21:57:56 UTC 2009


John Lindgren wrote:
> Okay, 2.0 has been released now (and will run on Lenny if compiled from
> source, in spite of nominally depending on newer libraries). How about
> updating now and testing again? Also, whether or not you update, try
> clearing $HOME/.config/audacious. Sometimes the config gets corrupted
> and causes segfaults.
> 
> John Lindgren

Ok, it seems to start and seems to run. I'll let you know in within a
few days if it crashes.

One thing I have noticed is it seems to use quite a significant amount
of CPU time. The default settings were using 30% CPU. When I reduced it
to slowest update time and Fastest Sync interpolation, CPU varies
between 7-25%.

This is just using `top` AMD Athlon(tm) 64 X2 Dual Core Processor 3800+.
In comparison, GNOME Movie Player (totem) uses only 1-6% CPU time.

And final observation is that Audacious seems to default to ESD sound
(first on list). ALSA may be a better choice for output plugin, if such
a default can be compiled in.

- Adam





More information about the Pkg-audacious-maintainers mailing list