657244 - Google ical calendars stop loading after laptop awakes from sleeping

Status: RESOLVED WORKSFORME

(Calendar :: Provider: GData, defect)

Description

[Ben Lerner]

User-Agent:       Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0.1) Gecko/20100101 Firefox/4.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b3pre Thunderbird/3.1.10

Using TB 3.1.10 and Lightning/GData nightlies 3/28/11

I use TB on my laptop all the time.  I close the lid on my laptop and it goes to sleep.  I wake it up frequently.  So far, so good.  Unfortunately, sometimes when I wake the laptop up, Lightning doesn't wake up all the way.  In particular, my Gdata calendars, all of the form http://www.google.com/calendar/ical/<some-identifier>%40group.calendar.google.com/public/basic.ics, all claim they are "momentarily not available".  They claim this permanently, until I restart TB.

On this latest failure, I saw the following messages in the Error Console, for each [calendar name]:
Warning: There has been an error reading data for calendar: [calendar name]. Error code: 0x804b0046. Description: 
Warning: There has been an error reading data for calendar: [calendar name]. Error code: READ_FAILED. Description: 

A quick search for that error code revealed nothing of interest.  I'm *pretty* sure the sleep/wake has to do with it, though I haven't noticed explicitly whether it occurs while I'm just actively using my machine.  Is it possible that if the machine sleeps while Lightning has a network connection is outstanding, when it next wakes up that network connection hasn't been cleared, but clearly has timed out?

Reproducible: Sometimes



Expected Results:  
Even if the network connection has timed out or otherwise fails, I'd expect that asking explicitly to Reload Remote Calendars would do so, but that errors out as well.

Comment 1

[Ben Lerner]

Update: problem still occurs with Tb5 and Lightning 1.0b4 and Gdata 0.8.

Comment 2

[Mike Conley (:mconley) (:⚙️)]

I can confirm this occurring for me too on OSX.

Comment 3

[石庭豐 (Seak, Teng-Fong)]

Lightning has native support to Google calendar through CalDAV (not ical).  Could you try it?

Comment 4

[Wayne Mery (:wsmwk)]

Ben?

(In reply to 石庭豐 (Seak, Teng-Fong) from comment #3)
> Lightning has native support to Google calendar through CalDAV (not ical). 
> Could you try it?

Comment 5

[Ben Lerner]

As in, remove my calendars and resubscribe to them using the CalDAV option rather than the Google Calendar option?  I can try, but I haven't seen this particular symptom in a while.  (Since I reported the bug, TB13.0.1 and Lightning 1.5.2 now seem to connect ok, but thrash the sqlite journal for many minutes every now and then (reported in bug 753297), so I'm reluctant to give it a reason to reload a calendar from scratch...)

If the CalDAV option is now the preferred way to subscribe to Google calendars, is the GData provider and/or the "Google Calendar" subscription option deprecated?  I'm happy to use the correct method; I just don't know which it is :)

Comment 6

[Lewis Rosenthal]

I thnk most of us, Ben, are using GData Provider for read/write access and CalDAV for read-only calendar subscriptions (though a number have switched to using CalDAV for both). I don't know of anyone using iCal with Google at present (but admittedly, I don't know everyone!).

To follow up on Comment 3, yes, the implication is to either remove (or simple disable) your current iCal calendar(s) in Lightning, and create (a) new CalDAV calendar(s). I would suggest *not* getting fancy with caching or anything, and just go plain vanilla for testing (I've had a round of fun with caching calendars the past 48 hours). Keep it simple. If you don't like the behavior/performance vs what you are presently using, then just delete the new one(s) and re-enable what you've been using. At least, that formula works for me. ;-)

Comment 7

[Ben Lerner]

Thanks, Lewis.  I have my setup similar to yours, with GData for the read/write calendars and CalDAV for the others.  I wasn't aware the Google/CalDAV interaction had progressed to read/write support, so I didn't know CalDAV *could* be used for those calendars...  

I'll try to find a machine to test these on sometime next week (my main laptop is very crashy at the moment and I'm trying to avoid giving it another excuse to bluescreen).

Comment 8

[Lewis Rosenthal]

Surely, Ben; no problem.

The GData Provider wiki page has some info concerning CalDAV: https://wiki.mozilla.org/Calendar:GDATA_Provider#Why_should_I_use_the_Provider.2C_and_not_access_via_CalDAV.3F . IIRC, there are still some issues with alerts (I may be wrong), and in my own experience, I had longer delays uploading changes than via GData. However, most everyone has different habits, so your experience may be different than mine.

As for bluescreens, as an IT consultant, I can tell you that the best way to avoid them is to change to a different operating system. :-)

Have a good one!

Comment 9

[石庭豐 (Seak, Teng-Fong)]

I'm using Google with CalDAV since day one and have never had big problem.  I have seen two glitches:
1. the first time a calendar is loaded, events are seen as double.  When this happens, I'd close TB and restart it again and the problem is gone.  I haven't seen any bug reported on this issue so I think it's not a big deal.

2. lightning cannot open two Google calendars at the same time by default, but there's an option to trigger its support -- so that's not a big deal

Comment 10

[石庭豐 (Seak, Teng-Fong)]

Oh, and most importantly, since this bug is about loading problem, but you haven't seen it again, we could consider the bug as closed?

Comment 11

[Philipp Kewisch [:Fallen][☁️📆]]

There has been a major rewrite of the Provider for Google Calendar between version 0.32 and 1.0. A vast number of bugs have been fixed during this rewrite, therefore I am closing lots of old bugs that I think might either be fixed or no longer apply to the latest version.

Please read the updated FAQ [1] for details on known issues. If you can reproduce your issue with the latest version of the Provider for Google Calendar and you can't find an existing bug that handles your case, please reopen this issue.

Thank you for your understanding.

[1] https://wiki.mozilla.org/Calendar:GDATA_Provider