Closed GoogleCodeExporter closed 8 years ago
I'd tested few seconds ago and it worked fine but it sounds like a problem with
the
extensions page. Maybe there's some problem with the page itself.
I uploaded the file as an attachment to the ticket. Try to install it that way.
Original comment by noctariushtc@googlemail.com
on 4 May 2010 at 7:35
Attachments:
Thanks for the quick reply, amazing! But it didn't work. The same message
appears when
dragging the crx-file into Chrome. My stupid fault: only now I notice that the
the
"title-bar" of the appearing error-message says: "Extension Install Failure".
My apologies for my lack of awareness earlier..
Original comment by geert.ve...@gmail.com
on 4 May 2010 at 7:51
So did you managed to install it?
Original comment by noctariushtc@googlemail.com
on 4 May 2010 at 9:16
Nope, the same message appears when dragging the crx-file (attachment in this
bug-
report) into Chrome.
Original comment by geert.ve...@gmail.com
on 4 May 2010 at 9:20
Try the actual version I uploaded seconds ago.
Original comment by noctariushtc@googlemail.com
on 4 May 2010 at 9:21
Same problem for me. Can't install from chome extentions or when downloading it
from
here. error:
Invalid value for 'content_scripts[0].matches[4]'.
I'm on ubuntu 10.04 64 bit/chromium 5.0.342.9 (43360)if it helps.
Original comment by stobbsan...@gmail.com
on 5 May 2010 at 7:04
Is that the Beta build? Since the actual dev build is 5.0.375.29
Original comment by noctariushtc@googlemail.com
on 5 May 2010 at 7:40
hm actual beta is the same version: 5.0.375.29, did you tried to simply update
Chrome
using apt-get?
Original comment by noctariushtc@googlemail.com
on 5 May 2010 at 10:40
Ok, I updated manually on my Ubuntu Netbook Remix 10.04 (via the Ubuntu Update
Manager
which included a Chrome update). After the update my Chrome version is:
5.0.375.29
beta and then the extension installed the way it should. Problem solved for me.
Thanks
for your quick replies! It keeps amazing me how well this bug reporting works.
Original comment by geert.ve...@gmail.com
on 5 May 2010 at 12:38
Thanks I'll try to keep up. But interesting that the version of chrome had a
problem. I
guess the problem was adding "chrome://" urls to the handled one. Maybe that
version
doesn't wanted it.
I'll close this one but good to know if this problem will come back in future
questions.
Original comment by noctariushtc@googlemail.com
on 5 May 2010 at 2:19
Issue 21 has been merged into this issue.
Original comment by noctariushtc@googlemail.com
on 5 May 2010 at 4:36
Bug reappears with 5.0.396.0~svn20100504r46318-0ubuntu1~ucd1 (as posted in
issue 21).
Downgrading to 5.0.375 from the beta/dev channel works around it.
The chromium-daily ppa package details view suggests that 6.0 will be tagged as
of svn
r46428 (6.0.396.0~svn20100505r46428-0ubuntu1~ucd1), so perhaps the behavior
(chrome://
being refused) is staying.
Original comment by zor...@gmail.com
on 5 May 2010 at 5:12
The problem seams to be, that from what I read is that chromium works quietly
differnt
from chrome.
I'm not sure why the devs did it but the ppa version is from build from pure
chromium
sources.
At the moment I'm thinking about how to make it possible that both versions
work as
expected.
Original comment by noctariushtc@googlemail.com
on 5 May 2010 at 5:57
I completely removed that chrome namespace since the new version doesn't
recognizes it
as well. Seems to be a permanent change and the access api to the chrome pages
isn't
avaiable yet.
Original comment by noctariushtc@googlemail.com
on 8 May 2010 at 6:59
Original issue reported on code.google.com by
geert.ve...@gmail.com
on 4 May 2010 at 7:25