Public bug reported:
Binary package hint: moosic
The moosic client dies with a ProtocolError when connecting to the
moosicd daemon. moosicd doesn't give any helpful output at that point,
but moosic itself shows this traceback:
[EMAIL PROTECTED]:~$ moosic list
Traceback (most recent call last):
File "/usr/bin/moosic", line 6, in <module>
main(sys.argv)
File "/usr/lib/python2.5/site-packages/moosic/client/cli/main.py", line 238,
in main
moosic.no_op()
File "/usr/lib/python2.5/xmlrpclib.py", line 1147, in __call__
return self.__send(self.__name, args)
File "/usr/lib/python2.5/xmlrpclib.py", line 1437, in __request
verbose=self.__verbose
File "/usr/lib/python2.5/xmlrpclib.py", line 1191, in request
headers
xmlrpclib.ProtocolError: <ProtocolError for
%2Fhome%2Fsjoerd%2F.moosic%2Fsocket/: 500 Internal Server Error>
I tried running over TCP/IP (same problem) and faking to be a client (by
using it's message to an earlier faked server) using nc, I got the
following session:
[EMAIL PROTECTED]:~$ nc localhost 9090
POST / HTTP/1.0
Host: localhost:9090
User-Agent: xmlrpclib.py/1.0.1 (by www.pythonware.com)
Content-Type: text/xml
Content-Length: 99
<?xml version='1.0'?>
<methodCall>
<methodName>no_op</methodName>
<params>
</params>
</methodCall>
HTTP/1.0 500 Internal Server Error
Server: BaseHTTP/0.3 Python/2.5
Date: Sat, 24 Mar 2007 16:04:24 GMT
I also ran both client and server in Python 2.4. This worked. So it
seems the problem is with Python 2.5. It's also not a problem for a
client in Python 2.5 to talk to a server in Python 2.4. A Python 2.4
client talking to a Python 2.5 client throws the same error.
** Affects: moosic (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
moosic client throws ProtocolError
https://launchpad.net/bugs/95532
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
