Bug 32941 - ValueError: Wrong host or port number : (, 80) upon login with emesene
Summary: ValueError: Wrong host or port number : (, 80) upon login with emesene
Status: RESOLVED FIXED
Alias: None
Product: papyon
Classification: Unclassified
Component: general (show other bugs)
Version: git master
Hardware: x86-64 (AMD64) All
: medium normal
Assignee: papyon-bugs
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-09 08:05 UTC by Sven
Modified: 2011-08-14 06:21 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Sven 2011-01-09 08:05:11 UTC
This is the output I get

[16:46:48 WARNING papyon.p2p] Unknown MSN object, another end point might have it
[16:46:48 ERROR papyon.msnp2p.session_manager] No handler could handle euf-guid {A4268EEC-FEC5-49E5-95C3-F126696BDBF6}
[16:46:48 WARNING papyon.p2p] Unknown MSN object, another end point might have it
[16:46:48 ERROR papyon.msnp2p.session_manager] No handler could handle euf-guid {A4268EEC-FEC5-49E5-95C3-F126696BDBF6}
[16:46:48 WARNING papyon.p2p] Unknown MSN object, another end point might have it
[16:46:48 ERROR papyon.msnp2p.session_manager] No handler could handle euf-guid {A4268EEC-FEC5-49E5-95C3-F126696BDBF6}
[16:46:48 WARNING papyon.p2p] Unknown MSN object, another end point might have it
[16:46:48 ERROR papyon.msnp2p.session_manager] No handler could handle euf-guid {A4268EEC-FEC5-49E5-95C3-F126696BDBF6}
[16:46:50 ERROR papyon.gnet.HTTP] Received error code 404 (Not Found) from byfiles.storage.msn.com:80
Traceback (most recent call last):
  File "/home/sven/emesene/emesene/e3/papylib/papyon/papyon/service/ContentRoaming/storage.py", line 171, in failed_cb
    run(errback, error)
  File "/home/sven/emesene/emesene/e3/papylib/papyon/papyon/util/async.py", line 40, in run
    callback[0](*args)
  File "/home/sven/emesene/emesene/e3/papylib/papyon/papyon/service/ContentRoaming/storage.py", line 148, in request_static_tile
    self.get_resource(scheme, host, resource, callback, errback)
  File "/home/sven/emesene/emesene/e3/papylib/papyon/papyon/service/ContentRoaming/storage.py", line 180, in get_resource
    transport.request(resource, http_headers, method='GET')
  File "/home/sven/emesene/emesene/e3/papylib/papyon/papyon/gnet/protocol/HTTP.py", line 186, in request
    self._process_queue()
  File "/home/sven/emesene/emesene/e3/papylib/papyon/papyon/gnet/protocol/HTTP.py", line 163, in _process_queue
    self._setup_transport()
  File "/home/sven/emesene/emesene/e3/papylib/papyon/papyon/gnet/protocol/HTTP.py", line 99, in _setup_transport
    self._transport.open()
  File "/home/sven/emesene/emesene/e3/papylib/papyon/papyon/gnet/io/iochannel.py", line 150, in open
    if not self._configure():
  File "/home/sven/emesene/emesene/e3/papylib/papyon/papyon/gnet/io/abstract.py", line 102, in _configure
    (self._host, self._port) )
ValueError: Wrong host or port number : (, 80)

Apparently, it causes my nickname to be unset (i.e. it becomes my email), so it's quite annoying.

For reference: https://github.com/emesene/emesene/issues/#issue/265
Comment 1 Louis-Francis Ratté-Boulianne 2011-04-12 20:51:15 UTC
Are you still experimenting the problem with papyon 0.5.4 ?
Comment 2 Riccardo (c10ud) 2011-04-13 01:55:16 UTC
i think this could be gone with latest errback commits (?)

2011/4/13  <bugzilla-daemon@freedesktop.org>:
> https://bugs.freedesktop.org/show_bug.cgi?id=32941
>
> --- Comment #1 from Louis-Francis Ratté-Boulianne <louis-francis.ratte-boulianne@collabora.co.uk> 2011-04-12 20:51:15 PDT ---
> Are you still experimenting the problem with papyon 0.5.4 ?
>
> --
> Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are the assignee for the bug.
> _______________________________________________
> papyon-bugs mailing list
> papyon-bugs@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/papyon-bugs
>
Comment 3 Sven 2011-04-13 02:03:15 UTC
It's still happening with the latest papyon updates pulled (the ones from 5 hours ago). Way to reproduce it is:

Log in with emesene 1. Do some stuff in emesene 1 -> This will break your profile.
Log in with emesene 2 -> Error.

Most users using emesene 2 come from emesene 1, so they'll all experience this.
Comment 4 Louis-Francis Ratté-Boulianne 2011-08-14 06:21:59 UTC
Fixed in master.

You will still get an error (we can't go around it if the ContentRoaming profile is broken), but the error is cleaner and should be handled properly by some clients (e.g. Emesene 2)


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.