Amarok XUL remote

bug fixed in release 1.0.

re-opening, as someone else has this problem too.

The script is not supposed to be launched 2 times.
there may be a problem between amarok and the kde session manager both
launching the script.
I cannot reproduce this, that may be fixed in recent KDE or Amarok.

Ok, I found the bug in the log. Here is the log:


Exception in thread Thread-1:
Traceback (most recent call last):
File "threading.py", line 442, in __bootstrap
self.run()
File
"/home/cavalier/.kde/share/apps/amarok/scripts/xulremote/XulRemote.py",
line 281, in run
self.app = XULRemote( sys.argv )
File
"/home/cavalier/.kde/share/apps/amarok/scripts/xulremote/XulRemote.py",
line 224, in __init__
self.startHttpd()
File
"/home/cavalier/.kde/share/apps/amarok/scripts/xulremote/XulRemote.py",
line 233, in startHttpd
self.httpd=AmarokHttpdThread()
File
"/home/cavalier/.kde/share/apps/amarok/scripts/xulremote/XulRemote.py",
line 161, in __init__
self.httpd =
AmarokHTTPServer((self.interface,self.port))
File
"/home/cavalier/.kde/share/apps/amarok/scripts/xulremote/AmarokHTTPServer.py",
line 25, in __init__
HTTPServer.__init__(self,
server_address, AmarokHTTPRequestHandler)
File "SocketServer.py", line 330, in
__init__
self.server_bind()
File "BaseHTTPServer.py", line
101, in server_bind

SocketServer.TCPServer.server_bind(self)
File "SocketServer.py",
line 341, in server_bind

self.socket.bind(self.server_address)
File "<string>",
line 1, in bind
error: (98,
'Adresse d\xe9j\xe0 utilis\xe9e')


What I tried to say is the following:

- I boot my computer. Then, I start amarok manually, then launch the
script. All is going fine.

- when I shut down my computer with amarok running and the script
xul-remote running, then when booting kde again, kde launch automatically
amarok and the script xul-remote. And in this case, the bug appears: the
script goes wrong (log above) and saturate the cpu at 100%. Then I have to
kill python and relaunch the xul-remote script.

Maybe you will find what is happening with the log...

Hi,

there's something I cant't understand, when you say "starting my computer
with xulremote activated" do you mean Amarok?

you can see some traces within Amarok: right-click on the script name in
the script manager and click on "show output log"