Reply
Thread Tools
Posts: 726 | Thanked: 345 times | Joined on Apr 2010 @ Sweden
#131
Version 0.0.8-3 has been uploaded to the repository and the Garage page. This is a bugfix release to take care of some of the bugs that have been found.

Fixes:
Clearing of variables after deallocation.
Thread issue when starting the first song from search or playlist. This might solve some problems with slow connections and long timeouts.
 

The Following User Says Thank You to Joorin For This Useful Post:
Dave999's Avatar
Posts: 7,075 | Thanked: 9,073 times | Joined on Oct 2009 @ Moon! It's not the East or the West side... it's the Dark Side
#132
Much faster now and no crash anymore
Thx
 
Posts: 726 | Thanked: 345 times | Joined on Apr 2010 @ Sweden
#133
Originally Posted by Dave999 View Post
Much faster now and no crash anymore
Thx
Great!

The thread issue was introduced when I did the work to separate starting of new songs and reading of music data. Without this separation, it was real easy to make the client crash but I also introduced this problem with a long timeout when starting the first song.

Bleh, fix one bug only to introduce another.
 
Posts: 9 | Thanked: 0 times | Joined on Jun 2010
#134
Hi Joorin, first of all many thanks for making this! Unfortunately I find it to be in an unusuable state. No matter what I do I get a segmentation fault. I can start the client and I can get a key authentication failure but doing anything else than that (even pressing the play button or searching while not logged in) results in an instant segmentation fault. Also a successful login will cause a segmentation fault for me. I have installed the latest version from the extras-devel and I don't have libdespotify or any other spotify client installed. Any idea or anything else I can help with? Would love to get it up and running!

Also I have PTR 1.2 if that's of any help.
 
Posts: 726 | Thanked: 345 times | Joined on Apr 2010 @ Sweden
#135
Originally Posted by wcborstel View Post
Hi Joorin, first of all many thanks for making this! Unfortunately I find it to be in an unusuable state. No matter what I do I get a segmentation fault.
That sounds really bad!

I can start the client and I can get a key authentication failure
If you get a key authentication error, you're not using the right libdespotify.

How did you install footify? Using the application manager or a .deb file? How do you start it?

but doing anything else than that (even pressing the play button or searching while not logged in) results in an instant segmentation fault.
Trying to search or play while not logged in might result in anything. These buttons will, in some future UI clean-up version, be inactivated until you are logged in.

Also a successful login will cause a segmentation fault for me. I have installed the latest version from the extras-devel and I don't have libdespotify or any other spotify client installed. Any idea or anything else I can help with? Would love to get it up and running!

Also I have PTR 1.2 if that's of any help.
Getting a successful login shouldn't be possible if you get key authentication error. This suggests that you start the application in some special way.

As far as I know, footify should work on both PR1.1.1 and PR1.2 but since I haven't upgraded yet, this is just me guessing since no-one with PR1.2 has reported any specific error that might suggest that it shouldn't work.

Could you please supply the output of the following, using the XTerminal:
Code:
ldd /home/opt/footify/usr/bin/footify
 
Posts: 9 | Thanked: 0 times | Joined on Jun 2010
#136
Originally Posted by Joorin View Post
That sounds really bad!


If you get a key authentication error, you're not using the right libdespotify.
Ah sorry, I should have been more clear. I am getting those errors when deliberately entering incorrect information. I am getting a segmention fault as soon as I enter my own account's credentials.

How did you install footify? Using the application manager or a .deb file? How do you start it?
From the app manager. Or more specifically with ap-get install footify, but that does the same thing anyway.

Getting a successful login shouldn't be possible if you get key authentication error. This suggests that you start the application in some special way.
All I do as a normal user is type in "footify" from the xterm.

Could you please supply the output of the following, using the XTerminal:
Code:
ldd /home/opt/footify/usr/bin/footify

This results in the following:
Code:
	libc.so.6 => /lib/libc.so.6 (0x4002e000)
	libhildon-1.so.0 => /usr/lib/libhildon-1.so.0 (0x40153000)
	libdespotify.so.0 => not found
	libvorbisfile.so.3 => /usr/lib/libvorbisfile.so.3 (0x401c6000)
	libresolv.so.2 => /lib/libresolv.so.2 (0x401d5000)
	libpulse-simple.so.0 => /usr/lib/libpulse-simple.so.0 (0x401ee000)
	libcrypto.so.0.9.8 => /usr/lib/libcrypto.so.0.9.8 (0x42050000)
	libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 (0x401f8000)
	libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0x40573000)
	libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0x40601000)
	libgconf-2.so.4 => /usr/lib/libgconf-2.so.4 (0x40620000)
	libpthread.so.0 => /lib/libpthread.so.0 (0x40644000)
	libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0x40664000)
	libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x406a5000)
	libpulse.so.0 => /usr/lib/libpulse.so.0 (0x40781000)
	libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x407a9000)
	/lib/ld-linux.so.3 (0x40000000)
	libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0x41f30000)
	libgio-2.0.so.0 => /usr/lib/libgio-2.0.so.0 (0x407bb000)
	libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0x40825000)
	libpangocairo-1.0.so.0 => /usr/lib/libpangocairo-1.0.so.0 (0x40853000)
	libcairo.so.2 => /usr/lib/libcairo.so.2 (0x40864000)
	libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0x408cd000)
	libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x41750000)
	libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x417c8000)
	libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0x40914000)
	libdbus-glib-1.so.2 => /usr/lib/libdbus-glib-1.so.2 (0x4091f000)
	libdbus-1.so.3 => /usr/lib/libdbus-1.so.3 (0x40942000)
	libcanberra.so.0 => /usr/lib/libcanberra.so.0 (0x4097f000)
	libvorbis.so.0 => /usr/lib/libvorbis.so.0 (0x40995000)
	libogg.so.0 => /usr/lib/libogg.so.0 (0x409c5000)
	libpulsecommon-0.9.15.so => /usr/lib/libpulsecommon-0.9.15.so (0x409d1000)
	libgdbm.so.3 => /usr/lib/libgdbm.so.3 (0x42710000)
	librt.so.1 => /lib/librt.so.1 (0x40a01000)
	libdl.so.2 => /lib/libdl.so.2 (0x40a10000)
	libm.so.6 => /lib/libm.so.6 (0x40a1b000)
	libz.so.1 => /usr/lib/libz.so.1 (0x413d0000)
	libX11.so.6 => /usr/lib/libX11.so.6 (0x40a91000)
	libXtst.so.6 => /usr/lib/libXtst.so.6 (0x41ad8000)
	libXcomposite.so.1 => /usr/lib/libXcomposite.so.1 (0x41b90000)
	libXdamage.so.1 => /usr/lib/libXdamage.so.1 (0x41ba0000)
	libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0x41ac8000)
	libXext.so.6 => /usr/lib/libXext.so.6 (0x41968000)
	libXrender.so.1 => /usr/lib/libXrender.so.1 (0x41988000)
	libXi.so.6 => /usr/lib/libXi.so.6 (0x41a10000)
	libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0x41b78000)
	libXcursor.so.1 => /usr/lib/libXcursor.so.1 (0x41a98000)
	libpixman-1.so.0 => /usr/lib/libpixman-1.so.0 (0x40b82000)
	libpng12.so.0 => /usr/lib/libpng12.so.0 (0x41938000)
	libexpat.so.1 => /usr/lib/libexpat.so.1 (0x414b8000)
	libltdl.so.7 => /usr/lib/libltdl.so.7 (0x41f88000)
	libXau.so.6 => /usr/lib/libXau.so.6 (0x414e0000)
	libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x414f0000)
Seems that I'm missing libdespotify but I thought I didn't need it? Since you're compiling your code against a newer version of libdespotify?

Last edited by wcborstel; 2010-06-14 at 18:46.
 
Posts: 48 | Thanked: 21 times | Joined on May 2010
#137
This might be a stupid question, but do you have Spotify Premium?
 
Posts: 9 | Thanked: 0 times | Joined on Jun 2010
#138
Yep I do have a Spotify Premium account
 
Posts: 726 | Thanked: 345 times | Joined on Apr 2010 @ Sweden
#139
Originally Posted by wcborstel View Post
Ah sorry, I should have been more clear. I am getting those errors when deliberately entering incorrect information. I am getting a segmention fault as soon as I enter my own account's credentials.
As far as I know, entering wrong username or password will result in an error message stating this and not something about key authentication.

From the app manager. Or more specifically with ap-get install footify, but that does the same thing anyway.
The app manager removes the downloaded .deb package after installation which apt-get doesn't but apart from that they do the same thing, yes. Which version was installed?

All I do as a normal user is type in "footify" from the xterm.
Ah, good, could you then please supply any output that is written to the terminal?

This results in the following:
Code:
	libc.so.6 => /lib/libc.so.6 (0x4002e000)
	libhildon-1.so.0 => /usr/lib/libhildon-1.so.0 (0x40153000)
	libdespotify.so.0 => not found
	libvorbisfile.so.3 => /usr/lib/libvorbisfile.so.3 (0x401c6000)
...
Seems that I'm missing libdespotify but I thought I didn't need it? Since you're compiling your code against a newer version of libdespotify?
The libdespotify that is used is located in /home/opt/footify/usr/lib and is used via the LD_LIBRARY_PATH environment variable which is set in the /home/opt/footify/usr/bin/footify.sh script that should be the file that is linked to from /usr/bin/footify .

So, no need for you to install libdespotify.
 
Posts: 9 | Thanked: 0 times | Joined on Jun 2010
#140
Originally Posted by Joorin View Post
As far as I know, entering wrong username or password will result in an error message stating this and not something about key authentication.
I have double checked and it really says "key exchange failed". I am connected with wifi and have a working internet connection as well.


The app manager removes the downloaded .deb package after installation which apt-get doesn't but apart from that they do the same thing, yes. Which version was installed?
0.0.8-3

Ah, good, could you then please supply any output that is written to the terminal?
With normal attempting to login (and thus resulting in a segmentation fault):
Code:
footify-0.0.8-3
  init client, high_bitrate=0, use_cache=0
segmentation fault
The libdespotify that is used is located in /home/opt/footify/usr/lib and is used via the LD_LIBRARY_PATH environment variable which is set in the /home/opt/footify/usr/bin/footify.sh script that should be the file that is linked to from /usr/bin/footify .

So, no need for you to install libdespotify.
Ah yes makes sense, thanks for that. Didn't know the LD_LIBRARY_PATH was used somewhere.
 
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 05:49.