Hello Karsten,

On Sat, Mar 25, 2017 at 08:06:07PM +0100, Karsten wrote:
 
> I upgraded from Debian Jessie to Stretch.
> One of the things that are not running in KDE is Icedove.
> It is hanging after the start.

Can you test if you have changed the setting of the option
javascript.options.baselinejit to 'true'? If so please set this to
false. You can change this in the settings menu.

We switched this option to 'false' some time ago as it's has shown a
slow working Icedove/Thunderbird in the past.

$ grep baseline /etc/thunderbird/pref/thunderbird.js 
pref ("javascript.options.baselinejit", false);

https://anonscm.debian.org/cgit/pkg-mozilla/icedove.git/commit/?id=d68e1695abbaa0081073089b1557e6b56604e4a5

> When i start icedove in a shell i can see the following messages:
> 
> $ icedove
> [calBackendLoader] Using libical backend at
> /usr/lib/icedove/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/components/libical-manifest
  ^^^^

This comes from calendar-google-provider.

> messenger.groupdav.overlay.js: failed to include 
> 'chrome://sogo-connector/content/general/vcards.utils.js'
> TypeError: redeclaration of let kPhotoImageCache
> File: chrome://sogo-connector/content/general/vcards.utils.js
> Line: 22
> 
>  Stack:
> 
> @chrome://sogo-connector/content/general/vcards.utils.js:22:5
> jsInclude@chrome://sogo-connector/content/addressbook/messenger.groupdav.overlay.js:26:13
> @chrome://sogo-connector/content/addressbook/messenger.groupdav.overlay.js:37:1

There is some redeclaration error for the function 'kPhotoImageCache'. I
haven't this issue but I also don't use KDE.
I see instead also a redeclaration error for '_insertCardMethods' but I
don't a have clue were this come from nor how to solve this as I don't
have a deeper knowledge on JS or XUL.

> startup from sogo-connector
> *** new sync: 1
>   1/sync with https://PC7/sabredav/groupwareserver.php/addressbooks/privat/...
> *** new sync: 2
>   2/sync with 
> https://PC7/sabredav/groupwareserver.php/addressbooks/name/privat/...
> *** new sync: 3
>   3/sync with 
> https://PC7/sabredav/groupwareserver.php/addressbooks/myname/share/...
> exception getting pref 
> 'extensions.ca.inverse.addressbook.groupdav.ldap_2.servers.name.url':
> [Exception... "Component returned failure code: 0x8000ffff 
> (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getCharPref]"  nsresult: "0x8000ffff 
> (NS_ERROR_UNEXPECTED)"  location: "JS frame :: 
> chrome://sogo-connector/content/general/preference.service.addressbook.groupdav.js
>  :: GdPSvc__getPref :: line 126" data: no] (126)
> exception getting pref 
> 'extensions.ca.inverse.addressbook.groupdav.ldap_2.servers.pab.url':
> [Exception... "Component returned failure code: 0x8000ffff 
> (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getCharPref]"  nsresult: "0x8000ffff 
> (NS_ERROR_UNEXPECTED)"  location: "JS frame :: 
> chrome://sogo-connector/content/general/preference.service.addressbook.groupdav.js
>  :: GdPSvc__getPref :: line 126" data: no] (126)
> exception getting pref 
> 'extensions.ca.inverse.addressbook.groupdav.ldap_2.servers.history.url':
> [Exception... "Component returned failure code: 0x8000ffff 
> (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getCharPref]"  nsresult: "0x8000ffff 
> (NS_ERROR_UNEXPECTED)"  location: "JS frame :: 
> chrome://sogo-connector/content/general/preference.service.addressbook.groupdav.js
>  :: GdPSvc__getPref :: line 126" data: no] (126)

These exception comes from some internal checking and the mentioned
pref isn't found. I've got nearly the same messages. This comes from
some some assembling that the code is doing, but with wrong content.
That's nothing dramatical though needs some fixup by Inverse.

In your case the URIs

 extensions.ca.inverse.addressbook.groupdav.ldap_2.servers.name.url
 extensions.ca.inverse.addressbook.groupdav.ldap_2.servers.pab.url
 extensions.ca.inverse.addressbook.groupdav.ldap_2.servers.history.url

couldn't found.

> This seems to be the problem.

I don't think so.
What happen if you disable the sogo-connector extension? If you are
right than there shouldn't be a slow working Icdedove/Thunderbird. You
probably the first problem that is report such issues and in the between
times nobody seems to have similar problems.

Sorry, I can't give a better solution for this issue. All visible
issues from above a upstream problems so you should report them to
Inverse.
They don't do issue tracking on GitHub and unfortunately no person
is allowed to open up new report there. So maybe you get in contact by
there website?

https://github.com/inverse-inc/sogo-connector.tb31
https://inverse.ca/

Regards
Carsten

Reply via email to