Package: calendar-google-provider
Version: 38.3.0-1
Followup-For: Bug #733047
Hi,

tonight I had the following three behaviours of google calendars in
icedove+iceowl:

1. First I could not add an event to the calendar. I added it with iceweasel,
but it didn't occur in the icedove calendar tab even after manual
synchronisation.

I installed several other add-ons and disabled and reenabled the google
calendar provider (I don't remember in which order) and

2. Iceweasel semi-crashed after billions of CPU cycles. When I entered the
master password the first time the cpu usage went up to 100% (only on single
core) and the GUI was unresponsive. I had to wait some time until the
calculation has finished. Then I could close the other 8 annoying password
prompts before the main window disappeared. But some icewasel process still
consumed 3% of my cpu.

After deleting all calendars and readding them I got a similar behaviour to 2.
But I found out that I have to disable both the birthdays calender as well as
the week numbers.

3. It works: Iceweasel starts with the usual couple of master password
requests. Then it works more or less normal. I had different experiences about
adding events, but I could not track it down to a pattern so far.



-- System Information:
Debian Release: stretch/sid
  APT prefers testing-proposed-updates
  APT policy: (500, 'testing-proposed-updates'), (500, 'oldoldstable-updates'), 
(500, 'oldoldstable'), (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, mingw64-windows, mingw64-x86v64, mingw64-amd64, 
mingw64-i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

-- no debconf information

Reply via email to