After a week of using version 0.0.3, i,ve found one nasty bug (maybe it,s only with my device). whenever I play one song, everything goes fine, even clicking next works (not always, but most of the time). but whenever I go to a playlist / search function, and I try too doubleclick a song, the whole program exits or crashes.. any chance you know why this is? great thanks for you effort to keep a spotify client alive!

Version 0.0.3 has only been out for a little more than three days so I'm guessing you're using 0.0.2.

But, I just tried what you describe and I get another behaviour: start playing a song from a play list and then pick a song from Search and the music stops, the labels are updated with information for the new song and then silence. If I try to start a new song, the application hangs.

So, something fishy is going on, for sure.

EDIT:

And now it works flawlessly without any changes. Perhaps network trouble that confuses the client.

Hmmm, now I also have no problems. I also think it has something to do with network. I now use wifi, and this morning i used 3g. or do you think it,s more an spotify network error?

I'd easily blame my client for many things before blaming Spotify.

And I wouldn't be surprised if high network latency causes problems for the client.

Now I've created a Garage account, applied for project creation and applied for upload rights. If everything works out, I'll get up to speed on Debian packaging and hopefully I'll be able to push something to Extras-devel.

I've also doodled a little and created an icon for the application. Having to reboot to make it show up is a bit of a let down, even though the reboot was caused by me trying to find the right process to kill to make it show up.

Version 0.0.4 is here. This is just a stepping stone, once again, but this time it comes in the shape of a .deb file making easier installation possible.

New features:
+ Application menu with an About button.
+ Prints version information to stderr at startup.

I can't say I'm pleased with how the Hildon note looks but with three versions here in tar.gz form, I really needed to add some version information so this will have to do until I decide on something else.

This is my first Debian package, ever, so expect it to behave weirdly. I've done test installation on my own device and it worked for me but that's not to say it'll work for you.

Installation:

Hello Joorin, the .deb file works flawlessly. No problem with that, great job. I think I know what the "bug" is where I talked about earlier.
What I do to let the program crash:
- Login -> search tab -> look for song -> start song -> click on other song in search results = Crash
- Login -> playlist tab -> look for song -> start song -> click on other song in search results = Crash
- Login -> playlist tab -> look for song -> start song -> click on next / previous (for 2 or 3 times) = Crash

Don't get me wrong, this is my contribution for this great program. If you need anything, just post in this thread. Keep up the great work.

Reporting bugs is good, so no problem. And if you also take the time to test my .deb file, I'm only grateful.

I managed to get it to crash too, but with a longer route, suggesting something a little more complicated than a simple memory error.

I logged in, did a search, started a song, picked another song from search and started that while the other one was still playing. Then I looked in a playlist and started a song from there and, finally, I started a new song from the search result. And this was when it crashed on me. So, I got a bit more fun out of it.

My guess is that this is all related to how my client gets music data from despotify. While changing songs, the data that has just been collected is deallocated resulting in bad things when played. Being able to crash the application with Previous/Next song points in this direction too.

Thank you for the feedback!

And here is version 0.0.5 with one of the major thread bugs fixed. As i suspected, most of the problems with changing songs came from trying to get sound data while the despotify library was doing its thing.

Fixes:
Separation of thread activity in client layer and despotify when changing songs.

Changes:
+ Some small change to how the UI is updated when Previous or Next is clicked.
+ Polling update of the GUI is started as soon as the application starts and not when the first song starts.
+ The client layer should exit more cleanly now and avoid triggering a segmentation fault when the application is terminated.

Things to note:
- I sometimes end up with a song not starting. The application is still responsive but no sound data arrives. No idea why. By picking another song, I get music again.
- Doing another search after having scrolled around in the previous result works but the view is left at the old place and not reset to the top.
- There are similar scrolling issues with the playlist and song view.

after installing 0.0.5 via dpkg (having completely removed 0.0.3) I can't start it via the Menu anymore. After a few hours, the blue icon disappeared, and when I click on Footify, it seems to crash the desktop. It reloads all from hildon.