The Adblock Project

[NoBrandHero]

I've rm -rf'd /usr/lib/MozillaFirebird and ~/.phoenix, and the adblock xpi install still tries to write to the /usr/lib... chrome dir instead of my profile dir. And so, I get the -202 no permissions error.

Is AdBlock installable only by root, or did I overlook something in the faq?

This is with d2 nightly 17 trying to install on
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6b) Gecko/20031116 Firebird/0.7+

[Guest]

I am also unable to install the new adblock. It seems to require root, and that is a bit hard for me (at school). The old version (0.3) worked without problems.

[rue]

The current intall-routine checks the parameter 'buildID', to determine if component-installation will be necessary. For browser-builds older than June 24th, 2003, root-installation is forced.
.
It sounds like the 'buildID' variable might not be available anymore.
.
I don't run Firebird, so let me set up a test-install for you to check this. I'll post again to this thread when it's ready (later today).

[rue]

This test won't install anything, but it does throw an alert with the buildID.
That's what I need to know.
.
Right-click: save: drag to browser-pane -- buildID-test XPI

[Morten]

I have compiled my own Mozilla Firebird 0.7 (or to be precise, the FreeBSD port system has), and when running your buildID-test-xpi it returns "0". A long time ago, when Firebird was still called Phoenix I used to se "BuildID: 0000000" in the titlebar of the program.

Is it possble that only mozilla.org's versions of Firebird has a buildid?

[Morten]

I changed the if test in the install.js to a "if (1)" and successfully installed the adblock 0.5 dev.

Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031024 Firebird/0.7

[NoBrandHero]

I also got "0" returned. Morten reminded me that I neglected to mention that I too am running a self-compiled cvs build.

[rue]

Morten:
I'm glad you've got it goin'. Mozdev isn't allowing cvs-access right now, so I can't post this yet:


NoBrandHero:
I've updated the install-routine. Should root-install fail, it will now ask if you'd like to try profile-installation. I'll post a heads-up to this thread when it's available for download.

[rue]

build 18 is posted.
.
Grab it off the Dev. page.

[NoBrandHero]

Thanks rue.

Earlier I had done as Morten did and unzipped and edited the install.js. The prompt to profile install is of course the better solution.

The build 18 install worked, but before I could install it I had to manually delete adblock.jar from my chrome dir. I was under the impression that the Deinstall menu option would have taken care of deleting the .jar file. After I chose from the menu to deinstall b17, Adblock was gone from the Tools menu but it remained in the Options->Extensions list. So when I then ran the b18 install, it of course complained that it couldn't install because the old jar file was still there.

Is the uninstall supposed to be able to delete the adblock.jar file and remove itself from chrome.rdf?

[rue]

NoBrandHero:
While deinstalling, were any alerts thrown? -- it's supposed to notify you if something wasn't removed.
.
Someone mentioned deinstall failing in another thread, so I guess the latest browser-builds changed something. I only run moz1.3.1, so I can't check to see what's happening.

[NoBrandHero]

Sorry for not responding sooner.

No, there were no alerts shown during the uninstall.

[rue]

NoBrandHero:
If you're patient, a two-minute timer should inform you of what failed.
.
I'll redirect you to this thread, now -- since we're no longer covering the install-issue.