Closed
Bug 943457
Opened 12 years ago
Closed 12 years ago
SOGo calendars are not connected automatically due to 'Disk Space Watcher Service' trouble?
Categories
(Calendar :: General, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: wimmer, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 (Beta/Release)
Build ID: 20131112160018
Steps to reproduce:
Hi,
many people of SOGo groupware server use Thunderbird/Lightning as a native client. SOGo developers maintain SOGo Connector and SOGo Integrator extension for easy integration of SOGo calendars into Thunderbird/Lightning environment
[ http://www.sogo.nu/about/overview.html ] .
Developers released new version of these extensions few days ago and big trouble appeared - SOGo calendars are not connected automatically into Lightning environment when users start into fresh new Thunderbird profile.
We see following messages in Thunderbird error console:
--
Could not read chrome manifest 'file:///usr/local/thunderbird-24/extensions/%7B972ce4c6-7e08-4474-a285-3208198ce6fd%7D/chrome.manifest'.
--
While creating services from category 'profile-after-change', could not create service for entry 'Disk Space Watcher Service', contract ID '@mozilla.org/toolkit/disk-space-watcher;1'
--
SOGo developers consider 'Disk Space Watcher Service' trouble for a reason of troubles of unconnected SOGo calendars and they suggest to report it into Lighting bugzilla.
[ http://www.sogo.nu/bugs/view.php?id=2510 ]
[ https://lists.inverse.ca/sogo/arc/users/2013-11/msg00150.html ]
What do you think about it?
Thanks,
Milos
Keywords: calendar-integration
Comment 1•12 years ago
|
||
The message about 'Disk Space Watcher Service' is a known warning in Firefox, Thunderbird, SeaMonkey, ... See e.g. Bug 895964, Bug 883621. According to this bugs it can be ignored. I don't think it is the cause of your problem.
Did I understand you correct: It worked with the same Thunderbird version and the same Lightning version but with the previous version of the SOGo extensions? If yes: Sounds like a problem with those extensions.
Comment 2•12 years ago
|
||
I installed Lightning 2.6.3, SOGo Connector 24.0.2 and SOGo Integrator 24.0.2 in a fresh profile. During Thunderbird startup I get many error messages in console that are related to SOGo:
> folders-update.js: failed to include 'chrome://sogo-integrator/content/messenger/mails-labels.js'
> Error opening input stream (invalid filename?)
> File: undefined
> Line: undefined
>
> Stack: undefined
>
> Custom startup code not available.
> e: Error opening input stream (invalid filename?)
> extensions/folder update starts after: 0 cals
> no calendar available: checking extensions update right now.
> number of handled extensions: 2
> skipping startup, sogo-integrator present
> url: http://sogo-demo.inverse.ca/plugins/updates.php?plugin=sogo-integrator@inverse.ca&version=0.00&platform=WINNT_x86-msvc
> getExtensionData: [Exception... "Component returned failure code: 0x80004002 (NS_NOINTERFACE) [nsIRDFService.GetDataSourceBlocking]" nsresult: "0x80004002 (NS_NOINTERFACE)" location: "JS frame :: chrome://sogo-integrator/content/messenger/startup-overlay.js :: getExtensionData :: line 169" data: no]
> no data returned for 'sogo-integrator@inverse.ca'
> url: http://sogo-demo.inverse.ca/plugins/updates.php?plugin=sogo-connector@inverse.ca&version=0.00&platform=WINNT_x86-msvc
> getExtensionData: [Exception... "Component returned failure code: 0x80004002 (NS_NOINTERFACE) [nsIRDFService.GetDataSourceBlocking]" nsresult: "0x80004002 (NS_NOINTERFACE)" location: "JS frame :: chrome://sogo-integrator/content/messenger/startup-overlay.js :: getExtensionData :: line 169" data: no]
> no data returned for 'sogo-connector@inverse.ca'
> no available update for handled extensions
> no interface in sogoWebDAV named {d0029474-0cc4-42fd-bb21-d9ff22f5293c}
> no interface in sogoWebDAV named {d0029474-0cc4-42fd-bb21-d9ff22f5293c}
> no interface in sogoWebDAV named {d0029474-0cc4-42fd-bb21-d9ff22f5293c}
> no interface in sogoWebDAV named {d0029474-0cc4-42fd-bb21-d9ff22f5293c}
> no interface in sogoWebDAV named {d0029474-0cc4-42fd-bb21-d9ff22f5293c}
> no interface in sogoWebDAV named {d0029474-0cc4-42fd-bb21-d9ff22f5293c}
> no interface in sogoWebDAV named {d0029474-0cc4-42fd-bb21-d9ff22f5293c}
Comment 3•12 years ago
|
||
Some more messages that were reported to Error Console instead of console:
[JavaScript Warning: "ReferenceError: reference to undefined property e.fileName" {file: "chrome://sogo-integrator/content/messenger/folders-update.js" line: 10}]
[JavaScript Warning: "WARN addons.manager: Exception calling callback: ReferenceError: SIMailsLabels is not defined" {file: "chrome://sogo-integrator/content/messenger/folders-update.js" line: 261}]
> Did I understand you correct: It worked with the same Thunderbird version and the same Lightning version but with the > previous version of the SOGo extensions?
Yes - the same versions of TB-24.1.1 and Lightning-2.6.3 with older versions of SOGo extensions (prior to 24.0.2) are not affected by this trouble.
> If yes: Sounds like a problem with those extensions.
It looks so. But I didn't investigate all changes in SOGo extensions 24.0.2 yet and I respected opinion of SOGo developers...
Comment 5•12 years ago
|
||
Please forward the error and warning messages listed above to the SOGo developers. Based on all those messages I assume their extension is broken because they missed to include file mails-labels.js in the xpi package.
This was most likely caused by a packaging issue on the SOGo side.
Please see http://www.sogo.nu/bugs/view.php?id=2510 to test the new extension.
Comment 7•12 years ago
|
||
BTW: the SOGo extension doesn't report all errors to Error Console window. In some cases it just dumps them to standard console output. You need to switch advanced preference "browser.dom.window.dump.enabled" to "true" to see them in console.
It looks SOGo developers found bug in SOGo extensions (makefile issue which caused a packaging bug).
They released testing version of SOGo-Integrator just now and it works fine for me.
So it looks this issue will have happy end ;-)
I pass on all your findings to developers.
I'm sorry for false alarm, sometimes it's not easy for users to find where the problem is...
I appreciate your helpfulness and fast reaction.
Thanks for all your help,
Milos
Comment 9•12 years ago
|
||
Resolving as invalid per previous comments.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
Updated•12 years ago
|
Keywords: calendar-integration
You need to log in
before you can comment on or make changes to this bug.
Description
•