mglae You've been faster, just as I was writing basically the same answer 
skullmonkey You are welcome. Just don't forget to make backup of the file (or whole installation, for that matter), you never know. For example cp ./profiles.xml ./profiles.xml_bak from within the directory containing the profiles.xml file will give you a chance of recovery in case something goes awfully wrong...
Kodi was running, while you tried to change/delete the file? In that case I suppose it would save the file from memory to disk on shutdown...
In case you don't want to stop the Kodi process and then change the file, have you tried shutting the Rpi down, removing the memory card/flashdisk and modifying the file via different computer?
Don't forget to make backup of the file, just in case...
So I've updated and the snapserver (version 11.0.0.2) seems to work for me even though the changes I made were removed. At least those that I could find after such a long time after making them. It seems all is good right now.
Absolutely not sure if I remember correctly, but I think it might have been related with the snapserver server not recognizing the commandline parameter of 'stream', resulting in using the default snapfifo file.
I ran into similar problems when installing 10.0.0.4 on RPi4. I got it to work, finally. It's been a while, but I think I did the following:
1. I wanted to run snapserver and stream output of Kodi to different snapclients (I have a different computer with decent soundcard running snapclient, among other things, connected to audio amplifier)
2. If I remember correctly (and looking at the changes I made), the problem was that Kodi sound stream was passed to '/tmp/snapkodi' file which should be picked up by snapserver and streamed to clients. No matter what I've tried, snapserver would not play from that file.
3. So in the end I ended up modifying 'snapserver.start' file and changed 'file' variable to point to the default '/tmp/snapfifo' file. That did most of the trick.
4. The pulse and audio output settings have to be set correctly.
Another thing to consider is that the version of plugin and hence the snapserver is quite old and newer versions might be fixed (either on plugin configuration part or snapserver part) - don't know yet.
Guess I'll find out when I upgrade.
