312914 - error message on first startup: chrome registration failed

Status: RESOLVED WORKSFORME

(Calendar :: Internal Components, defect)

Description

[Mark Harrison]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.9a1) Gecko/20051018 Mozilla Sunbird/0.2+

The first time the program is executed after download, this message
is displayed:

Chrome Registration Failed

Sunbird could not install thi sitem because of a failure in
Chrome Registration.  Please contact the author about
this problem.

Operation seems normal, but screen looks funny... e.g. no lines
drawn for the calendar grid, etc.

Reproducible: Always

Comment 1

[Adam Guthrie]

It looks like you tried to install an incompatable extension...

Comment 2

[Mark Harrison]

Hmm, so far as I know I haven't done anything but open the
mac DMG that I downloaded.

Are firefox extensions shared to Sunbird?  I've got these
extensions installed:

blogthis
bugmenot
smoothwheel
greasemonkey
web developer
linky

All latest versions except for bugmenot, which is 0.6.2.

I was able to reproduce this problem on two different Macs,
a powerbook and a G5, both running 10.4.2 Tiger.

Comment 3

[Reuven M. Lerner]

I experienced the same problem with version: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.9a1) Gecko/20051030 Mozilla Sunbird/0.2+

I'm running under Mac OS X 10.4.2.  I replaced the previous Sunbird.app with the new Sunbird.app that I got from <http://ftp.mozilla.org/pub/mozilla.org/calendar/sunbird/nightly/latest-trunk/sunbird-0.2+.en-US.mac.dmg> late on Sunday, October 30th.

I had an existing local calendar (from version 0.2), and was subscribed to two or three remote calendars.  When I started Sunbird 0.2+, I got the chrome registration error message.  I have installed lots of Firefox and Thunderbird extensions, but none for Sunbird that I know of.)  The application then quit on me.

When I restarted, I got similar display problems to what the original reporter mentioned, *plus* my original calendar information and remote subscriptions were  missing.

Comment 4

[David Bower]

I had the same issue.  I'm using Windows XP (Home).  Previously had 0.2 installed.  Uninstalled from the control panel but did NOT remove the directory at the end of the uninstall process as files were still within it (I assumed that they may have been preferences and calendar files).

Installed 0.3a1 which went through fine.  On load, I also got the "Chrome" error message, but I also got another screen which displayed some incompatibilty message with a module and displayed "Sunbird 0.2" as the module with problems (strange as I thought I'd uninstalled it!).  Highlighted the module and clicked on "Updates" (or something which suggested to look for updates).  None were found.  Clicked "OK" (or something similar!) to continue into the program and it crashed giving a "this program has crashed..." Windows XP message.

Tried to restart Sunbird from the Start menu and all appears fine (well, so far!) except that my old calendar has gone :-( ! (nothing important there, so no worries).

I do not believe I have ever installed any extensions (only ever the standard Sunbird installation packages).

Comment 5

[Nils Durner]

I experienced the same problem.
After it crashed, I uninstalled Sunbird from the Control Panel, removed the Sunbird directory and installed 0.3a1 again. This time the installation went fine.

Environment:
Microsoft Windows XP [Version 5.1.2600]
Professional Edition

Firefox 1.0.7
Thunderbird 1.5

Comment 6

[Matthew (lilmatt) Willis]

Reporter:
Can you replicate this behaviour using the latest nightly version of Sunbird?

Comment 7

[cmtalbert]

Reporter, I believe these start up issues have been addressed by the recent migrator patch. I have tried these upgrade paths using the latest nightly and cannot recreate this issue. Please give it another shot with the latest nightly and post a comment if you still encounter the bug.

In the meantime, I will mark this bug as Works For Me, due to its age and the fact that it seems to be resolved by the new migration wizard patch. 

Removing qawanted and assignee.