I recently updated my debian Airtime Installation from 2.0.1 to 2.1.2.
I had 3 problems,
1 - a lot of playlists (but not all of them) got their creator reassigned.
2 - On chrome, any page which allows a full screen scroll (calendar, preferences), is broken. As you scroll the content goes to the bottom and more empty space is created.
3- My audio output stopped working, play light is fine, audio doesn't go to my soundcard.
Regarding #1, Airtime 2.1 introduced the notion of playlist's creator, so I'm not sure how the creator could have changed from 2.0? Could you elaborate on this?
For #2 Please try clearing your browser cache. Most of us use Chrome and have not had these problems. Out of curiousity what is your OS? We've had one other user with a Mac OS that also reported some chrome issues.
For #3) this may be because another process has grabbed your soundcard (and locked it for exclusive use), while Airtime was updating. 2.1 comes with a utility "airtime-test-soundcard" to let you know if your soundcard is working properly. Let us know how that utility runs.
1 - I was definitely using 2.0.0 previously, just checked my install files. I bring this up becuase a number of people got locked out of playlists they had created becuase they are now controlled by one of the admin accounts. Its possible that creator wasn't there before, but in some instances the creator still makes sense, so I feel like it must have been.
2 - Having looked into this, it only occurs with Chrome on Mac OS . I cannot replicate this error on chrome on windows. Clearing the cache doesn't work. However it works just fine in safari.
3 - This is a great new feature.
I ran it and the output is attached. I think the relevant lines are:
2012/07/02 16:52:45 [alsa_out(default):3] Using ALSA 1.0.23.
2012/07/02 16:52:45 [threads:1] Thread "alsa_out(default)" aborts with exception Alsa error: No such file or directory!
2012/07/02 16:52:45 [threads:3] Raised by primitive operation at file "", line 0, characters 0-0
Thread 4 killed on uncaught exception Alsa.Unknown_error(2)