I've seen this too, and it was inconsistent. To me, it looked like maybe it was related to the problems Rafafel has been investigating.
Vasanth, try this: 1. Restart Chrome 2. Navigate to any webpage (eg www.google.com) 3. Drag the crx onto the page It's important in step 2 that the current page not be one of Chrome's built-in pages like the new tab page or history page. - a On Thu, Jun 18, 2009 at 9:31 AM, Vasanth Dharmaraj<[email protected]> wrote: > > I tried deleting and installing a few extensions. Looks like now I do > not get the error all the time. But I did manage to get it a 2 out of > 10 times. Here is the error: > > --------------------------- > Extension error > --------------------------- > Could not install extension from 'C:\Documents and Settings\dharmav\My > Documents\Downloads\gmail.crx'. Could not open file. > --------------------------- > OK > --------------------------- > > Vasanth > > On Jun 18, 12:19 pm, Erik Kay <[email protected]> wrote: >> (+chromium-extensions - discussions like this should really start happening >> there) >> It works for me on XP as well. Spaces in the filename aren't a problem. >> Could you please tell me what the error is that you're seeing? >> >> Erik >> >> On Thu, Jun 18, 2009 at 9:03 AM, Vasanth Dharmaraj <[email protected]>wrote: >> >> >> >> >> >> > Yes Daniele, you are right. It seems to be a problem with XP. Just >> > tried it on Windows 7. Installation works fine. >> >> > Regards, >> > Vasanth >> >http://www.vasanth.in >> >> > On Jun 18, 11:53 am, "Daniele S." <[email protected]> wrote: >> > > I had the same problem of Vasanth, my opinion is that the problem >> > > appears on Windows XP but does not on Windows Vista. >> >> > > Maybe the whitespaces on "Documents and Settings" ( where on Vista is >> > > just Users ) are the problem. >> >> > > Daniele >> >> > > On 18 Giu, 17:30, Erik Kay <[email protected]> wrote: >> >> > > > Hi Vasanth, >> > > > I don't have the installation problem you describe (I was able to >> > install >> > > > your page rank extension directly). What do you see when you try to >> > > > install? >> >> > > > Erik >> >> > > > On Thu, Jun 18, 2009 at 6:55 AM, Vasanth Dharmaraj <[email protected] >> > >wrote: >> >> > > > > Thanks for the update. I just repackaged my extensions: >> > > > >http://www.vasanth.in/2009/06/18/repackaged-my-chrome-extensions/ >> >> > > > > Installation of extensions is still broken in build 3.0.189.0 though. >> > > > > Currently one has to download the extension to a local folder and >> > > > > double click to install it. >> >> > > > > Regards, >> > > > > Vasanth >> > > > >http://www.vasanth.in >> >> > > > > On Jun 17, 8:56 pm, Nick Baum <[email protected]> wrote: >> > > > > > Hi all, >> >> > > > > > **We're excited to see many people are experimenting with the >> > upcoming >> > > > > > extension features of Chrome in the dev channel. We're getting a >> > lot of >> > > > > > great feedback and are working hard to bring extensions to the >> > stable >> > > > > > channel as quickly as possible. >> >> > > > > > As part of the latest dev channel release, we've had to make a >> > breaking >> > > > > > change to the crx format. This change adds signatures to our >> > package >> > > > > format, >> > > > > > which are necessary to enable automatic updates. Unfortunately, >> > this >> > > > > means >> > > > > > that any existing extensions will stop working, and will have to be >> > > > > > repackaged. >> >> > > > > > - *If you've developed an extension,* you can learn how to >> > repackage >> > > > > your >> > > > > > extensions for Chrome v 3.0.189.0 in *the packaging >> > > > > > doc< >> >> >http://dev.chromium.org/developers/design-documents/extensions/packaging> >> > > > > > * on our developer site. Note that your extension ID will now be >> > your >> > > > > > public key, so you'll have to change any code that uses that. >> > > > > > - *If you're using an extension someone else has developed, *you >> > will >> > > > > > have to reinstall it once the developer has repackaged it (as >> > > > > described >> > > > > > above). We've already updated our sample >> > > > > > extensions< >> >> >http://dev.chromium.org/developers/design-documents/extensions/samples> >> > > > > > . >> >> > > > > > Even though the whole point of the dev channel is to make our APIs >> > > > > available >> > > > > > early while they're still changing, we don't make these changes >> > lightly. >> > > > > > Once we push the extension system to the stable channel, breaking >> > changes >> > > > > > should be very rare (we'd like to say non-existent, but we don't >> > want to >> > > > > > jinx ourselves). >> >> > > > > > Let us know if you have any questions or run into any problems. >> > > > > > Cheers, >> >> > > > > > -Nick >> >> > > > > > PS: I'll be cc'ing chromium-dev and discuss for a few days, until >> > people >> > > > > > have had the time to subscribe to >> > > > > > chromium-extensions< >> >http://groups.google.com/group/chromium-extensions>. >> > > > > > We also posted this to the chromium blog <http://blog.chromium.org >> > >, >> > > > > which I >> > > > > > recommend subscribing to if you haven't already. > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss -~----------~----~----~----~------~----~------~--~---
