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
(Add. info:) I do not know what other files were messed up in the config
folder.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/975545
Title:
playlist.xspf:1: parser error : Start tag expected, ''
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/975545
Title:
playlist.xspf:1: parser error : Start tag expected, '' not found
To manage notifications about this bug go to:
After deleting /home/user/.config/audacious/playlist.xspf:
** (audacious:5201): CRITICAL **: playlist_entry_get_filename: assertion `entry
!= NULL' failed
Speicherzugriffsfehler (← segv)
(dmesg)
[ 1802.791538] audacious[4632]: segfault at 44 ip 7fdadea4746a sp
7fff77e192f0 error 4 in
** Description changed:
- Started audacious out ofn the console:
+ Started audacious out of the console:
$ audacious
file:///home/user/.config/audacious/playlist.xspf:1: parser error : Start tag
expected, '' not found
