I tried starting audacious from console w/o any parameters and with a playlist argument. Both failed.
The apparently random data in playlist.xspf did exist. It was a bug in ecryptfs.
Nevertheless a messed up config file should be discarded and not render a segv.
Deleting the entire audacious config folder helped. But a casual user you would not come up wIth deleting the config folder, esp. since no dialog whatsoever appeared when I tried to start audacious out of the start menu.
I tried starting audacious from console w/o any parameters and with a playlist argument. Both failed.
The apparently random data in playlist.xspf did exist. It was a bug in ecryptfs.
Nevertheless a messed up config file should be discarded and not render a segv.
Deleting the entire audacious config folder helped. But a casual user you would not come up wIth deleting the config folder, esp. since no dialog whatsoever appeared when I tried to start audacious out of the start menu.