XBL Status

wont connect

Bug #340444 reported by Cosworth1
4
Affects Status Importance Assigned to Milestone
XBL Status
Fix Released
Medium
Chris Hollenbeck

Bug Description

Was working fine. Last few days it sits there connecting with this error in the terminal:

Exception in thread Thread-1:
Traceback (most recent call last):
  File "/usr/lib/python2.5/threading.py", line 486, in __bootstrap_inner
    self.run()
  File "/usr/lib/python2.5/threading.py", line 446, in run
    self.__target(*self.__args, **self.__kwargs)
  File "./xblstatus.py", line 285, in menuFileConnect_clicked
    self.xbLive.connect()
  File "/home/voorhees/xblstatus/LiveConnect.py", line 189, in connect
    self.cookiejar.save(self.cookieFile)
  File "/usr/lib/python2.5/_LWPCookieJar.py", line 89, in save
    f.write(self.as_lwp_str(ignore_discard, ignore_expires))
  File "/usr/lib/python2.5/_LWPCookieJar.py", line 75, in as_lwp_str
    r.append("Set-Cookie3: %s" % lwp_cookie_str(cookie))
  File "/usr/lib/python2.5/_LWPCookieJar.py", line 35, in lwp_cookie_str
    time2isoz(float(cookie.expires))))
  File "/usr/lib/python2.5/cookielib.py", line 98, in time2isoz
    year, mon, mday, hour, min, sec = time.gmtime(t)[:6]
ValueError: timestamp out of range for platform time_t

See original description
Cosworth1 (jimmorrison1979)
description: updated
Revision history for this message
Chris Hollenbeck (chris-hollenbeck) wrote :

Confirmed on two different computers running Ubuntu Hardy (8.04) 32 bit. This error does not occur on Ubuntu Intrepid (8.10) 64 bit.

Changed in xblstatus:
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
Ksornberger (thebigsorbo) wrote :

I have also had the same error running the python code on my MacBook OS X 10.5

I've tried using this in the last week or so and usually get this error.

I did connect and save a cookie successfully once, I'm not sure what the difference was, but the next time I tried, it was back to this.
Any ideas?

Revision history for this message
Ksornberger (thebigsorbo) wrote :

If it is working on a 64 bit machine, and has to do with the dates, so you think it is something to do with the 2038 bug?
Maybe the expiry time on the cookie was recently pushed back?

Revision history for this message
Chris Hollenbeck (chris-hollenbeck) wrote :

Yes, that's exactly what I was thinking. I haven't had a chance to play around with it but the error needs to be handled or some sort of cookie date adjustment needs to take place before it can be saved.

Revision history for this message
Chris Hollenbeck (chris-hollenbeck) wrote :

It looks like there is some difference in the way LWPCookieJar and MozillaCookieJar handle saving the cookie. I was able to get it to start up with MozillaCookieJar. I'll play around with this a little more and will hopefully have a fix for you shortly.

Changed in xblstatus:
assignee: nobody → chris-hollenbeck
Revision history for this message
Chris Hollenbeck (chris-hollenbeck) wrote :

I just pushed up a possible fix to trunk (revision 39). Please test this on your end by branching a local copy and executing it. It works on my 32-bit Ubuntu 8.04 (Hardy) system.

Revision history for this message
Ksornberger (thebigsorbo) wrote :

Looks like that worked on my system without an error... good thinking
Thanks!

Chris Hollenbeck (chris-hollenbeck)
Changed in xblstatus:
status: Confirmed → Fix Committed
Revision history for this message
Chris Hollenbeck (chris-hollenbeck) wrote :

This bug is now fixed in version 0.4.1

Changed in xblstatus:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.