


Amarok 1.x Scripts by tkaitchuck 32 comments
You can of course get around this if you really want to. If you look at its manpage, streamripper has an option to change the user agent to anything you want. All you have to do is to add this flag to the 'options' string specified at the top of the file.
This is not done by default, because I have no desire to conceal things from the site it is connecting to. - Jun 15 2009

Amarok 1.x Scripts by tkaitchuck 32 comments
Someone decided that the only plugins that should be allowed must be written in Java script, not call any external libraries processes and only call these functions within Amarok: http://amarok.kde.org/wiki/Development/Script_API
I consider this very limiting and have filed a feature request: https://bugs.kde.org/show_bug.cgi?id=179015
I would encourage anyone who wants this plugin to continue to work in future version to vote for that feature.
- Dec 29 2008

Amarok 1.x Scripts by tkaitchuck 32 comments
There are two possibilities that can cause this.
First is if you are using the "Always record" mode, the server may have accepted the connection from your computer, and allowed you to start listening, but rejected when you tried to reconnect, because it was busy. This should not happen in "record on demand" mode. So try that first.
The second possibility is that it simply did not wait long enough to try to connect to the server. This could simply be caused by your computer being slow. If this happens consistently go into the script manager and right click on the script and click edit. Then change the line towards the bottom that says: "sleep 2" to something like say "sleep 5", which will add an extra three seconds pause to get the relay server up and running.
If this continues to happen, even with the increased delay and in "on demand" mode. Then edit the script so that it sends it's log to a file somewhere, start amarok and reproduce the problem. Then send me the log file as well as a step by step list of everyting you did. - May 02 2006

Amarok 1.x Scripts by tkaitchuck 32 comments

Amarok 1.x Scripts by tkaitchuck 32 comments
There are two possibilities that can cause this.
First is if you are using the "Always record" mode, the server may have accepted the connection from your computer, and allowed you to start listening, but rejected when you tried to reconnect, because it was busy. This should not happen in "record on demand" mode. So try that first.
The second possibility is that it simply did not wait long enough to try to connect to the server. This could simply be caused by your computer being slow. If this happens consistently go into the script manager and right click on the script and click edit. Then change the line towards the bottom that says: "sleep 2" to something like say "sleep 5", which will add an extra three seconds pause to get the relay server up and running.
If this continues to happen, even with the increased delay and in "on demand" mode. Then edit the script so that it sends it's log to a file somewhere, start amarok and reproduce the problem. Then send me the log file as well as a step by step list of everyting you did. - May 02 2006

Dolphin Service Menus by tkaitchuck 5 comments
the directory named
.kde/apps/share/apps/konqueror/servicemenus
within your home directory. - Feb 20 2006

Amarok 1.x Scripts by tkaitchuck 32 comments

Amarok 1.x Scripts by tkaitchuck 32 comments

Amarok 1.x Scripts by tkaitchuck 32 comments

Amarok 1.x Scripts by DaBlade 5 comments

Various Stuff by tkaitchuck 20 comments
If you don't have kde3 you may want to wait a few days for a kde 2.2 version. Or you could try inserting those 3 "Preload" lines into your startkde script and see what happens. - Apr 09 2002

Various Stuff by tkaitchuck 20 comments
Because it loads the Desktop/panel/window manager first, then does the usual kde stuff.
So then when the kdeinit discovers that the window manager desktop and panel are already running it just doesn't start another copy.
So after about 20 sec (usual kde load time) it is exactly the same as it would be with the default script.
All the problems I mentioned are either come directly from these thins not being session managed in the usual way. (So I don't think there will be any other problems)
About the fonts though, If you want to use font overriding, just copy that section from your existing startkde3 script. (I just removed it because it took time and it is not something most people need)
If you have any other problems just e-mail me. - Apr 08 2002