Closed Bug 533535 Opened 16 years ago Closed 16 years ago

Firefox fails to launch when certain extensions are enabled

Categories

(Firefox :: Extension Compatibility, defect)

Product:
Firefox
Component:
Extension Compatibility
Version:
3.6 Branch
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED DUPLICATE of bug 551152

People

(Reporter: neil, Unassigned)

Details

User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.2b4) Gecko/20091124 Firefox/3.6b4 Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.2b4) Gecko/20091124 Firefox/3.6b4 When any of the following extensions are enabled, Firefox 3.6 Beta 4 fails to start on Mac OS X (the icon bounces on the dock, but then disappears): 1Password 3.0.1 Echofon 1.9.4 Greasemonkey 0.820091129.3 Nightly Tester Tools 2.0.3 All of the above extensions result in this problem - i.e. Firefox will only start correctly if all are disabled (or it is run in Safe Mode) For reference, the following extensions are also installed but seem to work: Adblock Plus 1.1.1 British English Dictionary 1.19 Shareaholic 1.9 I have not used Nightly Tester Tools to override compatibility for any of these and they are the latest versions. Also, Firefox was working correctly with all addons installed and enabled bar Greasemonkey - this problem only started after Greasemonkey was installed, but persists even after I uninstalled Greasemonkey. I have also pasted the Terminal output when running /Applications/Firefox.app/Contents/MacOS/firefox-bin in Terminal. I have also tried this with a clean profile and after replacing Firefox.app with a fresh copy from mozilla.com Reproducible: Always Steps to Reproduce: 1. Enable one of the named extensions 2. Quit Firefox 3. Start Firefox Actual Results: Firefox fails to start Expected Results: Firefox should start with the extensions enabled and working correctly. 2009-12-08 20:32:13.240 firefox-bin[682:903] *** __NSAutoreleaseNoPool(): Object 0x280d6c0 of class NSCFString autoreleased with no pool in place - just leaking 2009-12-08 20:32:13.244 firefox-bin[682:903] *** __NSAutoreleaseNoPool(): Object 0x2810ca0 of class NSPathStore2 autoreleased with no pool in place - just leaking 2009-12-08 20:32:13.245 firefox-bin[682:903] *** __NSAutoreleaseNoPool(): Object 0x2811270 of class NSPathStore2 autoreleased with no pool in place - just leaking 2009-12-08 20:32:13.246 firefox-bin[682:903] *** __NSAutoreleaseNoPool(): Object 0x2810e20 of class NSPathStore2 autoreleased with no pool in place - just leaking 2009-12-08 20:32:13.247 firefox-bin[682:903] *** __NSAutoreleaseNoPool(): Object 0x280de10 of class NSPathStore2 autoreleased with no pool in place - just leaking 2009-12-08 20:32:13.248 firefox-bin[682:903] *** __NSAutoreleaseNoPool(): Object 0x2811390 of class NSPathStore2 autoreleased with no pool in place - just leaking 2009-12-08 20:32:13.248 firefox-bin[682:903] *** __NSAutoreleaseNoPool(): Object 0x1531bf0 of class NSPathStore2 autoreleased with no pool in place - just leaking 2009-12-08 20:32:13.249 firefox-bin[682:903] *** __NSAutoreleaseNoPool(): Object 0x2811510 of class NSPathStore2 autoreleased with no pool in place - just leaking 2009-12-08 20:32:13.250 firefox-bin[682:903] *** __NSAutoreleaseNoPool(): Object 0x280dd20 of class NSPathStore2 autoreleased with no pool in place - just leaking 2009-12-08 20:32:13.250 firefox-bin[682:903] *** __NSAutoreleaseNoPool(): Object 0x1531fa0 of class NSPathStore2 autoreleased with no pool in place - just leaking 2009-12-08 20:32:13.252 firefox-bin[682:903] *** __NSAutoreleaseNoPool(): Object 0x28119a0 of class NSPathStore2 autoreleased with no pool in place - just leaking 2009-12-08 20:32:13.252 firefox-bin[682:903] *** __NSAutoreleaseNoPool(): Object 0x2811730 of class __NSCFDate autoreleased with no pool in place - just leaking 2009-12-08 20:32:13.254 firefox-bin[682:903] *** __NSAutoreleaseNoPool(): Object 0x2812460 of class NSCFString autoreleased with no pool in place - just leaking 2009-12-08 20:32:13.254 firefox-bin[682:903] *** __NSAutoreleaseNoPool(): Object 0x1532290 of class NSCFString autoreleased with no pool in place - just leaking 2009-12-08 20:32:13.255 firefox-bin[682:903] *** __NSAutoreleaseNoPool(): Object 0x1531d60 of class NSCFSet autoreleased with no pool in place - just leaking 2009-12-08 20:32:13.256 firefox-bin[682:903] *** __NSAutoreleaseNoPool(): Object 0x2811840 of class __NSCFDate autoreleased with no pool in place - just leaking 2009-12-08 20:32:13.257 firefox-bin[682:903] *** __NSAutoreleaseNoPool(): Object 0x28122d0 of class NSCFTimer autoreleased with no pool in place - just leaking 2009-12-08 20:32:13.258 firefox-bin[682:903] *** __NSAutoreleaseNoPool(): Object 0x28123f0 of class __NSCFDate autoreleased with no pool in place - just leaking
Version: unspecified → 3.6 Branch
Now working okay with Greasemonkey 0.8.4. Closing.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
Re-opening as it appears to be happening again. And it persists after uninstalling Greasemonkey as well.
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Same, or related problem here. I thought it's 1Password, but it seems not. I think it started when i installed Skipscreen, on Beta 3 of 3.6. Now i just can stay with that exact configuration. If i update ANY extension, Firefox will not launch (os x 10.6.2). Just a short bouncing of the icon, and then nothing. I tried to erase the 3 files extensions.cache/.ini/.rdf, but also doesn't help. Uninstalled every extension. Then it works. As soon as i then install just one extension again, firefox will not launch again. Only solution is save mode + disable all extensions, then it launches. Upgrading to b4 or b5 doesn't help either. Seems like my library has some traces in it that Firefox doesn't like. When i use time machine to set back my library to the last working situation, it works again, but then again: upgrading any extensions makes firefox not launch.
I've also previously had SkipScreen installed, but do not any longer.
no, me neither. but now something seems broken, and i cannot reverse it, as i wrote... all changes in extensions will make FF unusable. do you also have that problem? for example, when you download stylish extension: can you install it? my FF doesn't start then. i'm gonna see if i can clean my user profile a bit and then upload it somewhere, so others can check if they can reproduce it.
so wicked. did the same things i did before without success, but now it works and i fail to generate a reproducible bug. i did this now: - backup bookmarks - CMD+click FF, to get the reset dialog. reset everything, disable all extensions, restart, delete all extensions - delete places.sqlite and signons.sqlite - update beta 3 to beta 5 - re-install all extensions - play back bookmarks from the backup. before, when doing these steps and enabling just 1 extension it would fail to launch. now it works. maybe year 2009 bug ;-)
I've experienced this again recently - I am unsure what caused it but disabling the named extensions allowed the browser to work again. And then a day later I re-enabled the extensions and it launched fine. As you say, it's impossible to accurately reproduce.
I confirm that. It showed first alt least in 3.6b4 and still in 3.6rc. On 3.5b4 can sometimes be reproduced. Fixed by disabling and re-enabling plugins. On 3.6rc it can't be fixed, can always be reproduced. To reproduce just install any of mentioned below add-ons. Disappears in safe-mode or if addon is disabled. Plug-ins affected are: Delicious Bookmarks 2.1.072 Read It Later 2.0.3 Stylish 1.0.7 Platform Mac OS 10.6.2 on MBP.
I can confirm this with the final 3.6 release on MBP (late 2009) using Mac OS X 10.6.2 as well. I checked Plugins like * Delicious Bookmarks * DownThemAll FF just don't start at all.
I have also experienced this on Firefox 3.6 final. I've found that a system reboot usually fixes this. That implies it may be a memory issue. Can anyone else try running Firefox from the command line and printing the output in terminal? Open Terminal and then run /Applications/Firefox.app/Contents/MacOS/firefox-bin - on mine I get a series of errors and this may help the developers pinpoint a cause.
More user reports on this issue: http://support.mozilla.com/no/forum/1/562036 Which steps should be done to move this issue to NEW from UNCONFIRMED?
(In reply to comment #11) > Which steps should be done to move this issue to NEW from UNCONFIRMED? Vote for this bug.
Sorry but add-ons bugs are not Firefox bugs, please contact extensions authors. Moving to extension compatibility
Component: General → Extension Compatibility
QA Contact: general → extension.compatibility
I tried the addons listed in Comment 8 and was not able to reproduce the bug using Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6. If someone can identify which extension or combinations of extensions is causing the issue we can contact the extension authors.
I've closed all Firefoxes, backed up and removed ~/Library/Application Support/Firefox, all files from /Library/Internet Plug-Ins and ~/Library/Internet Plug-Ins, and ran FF3.6. Than I've installed delicious plug-in and FF3.6 did not crash. I've returned all plug-ins and profile back and it works with FF3.6 now. I suspect a plug-in issue (not extension). Can anyone verify if this solution helps?
(In reply to comment #15) > Can anyone verify if this solution helps? I tried the procedure as mentioned above, but FF fails again to start after installing the Delicious Plugin.
Totally removed all traces of FF 3.6 from my Mac OS X 10.6.2 system. Installed FF 3.6, ran it, and all is fine. Quit, run again, everything works. Run FF 3.6, install the Weave addon. Restart FF 3.6 and it fails to start. Run FF 3.6 in Safe Mode and it runs fine. Disable Weave addon, FF 3.6 starts fine. Turn Weave back on, restart FF, fails to start. I get the same effect with about half the addons I use, which are pretty mainstream and have been working fine for months. Everything even worked fine when I first upgraded to 3.6. I believe some of my issues started happening after an Apple Security Update came across; I'm not sure about the timing, sorry. What has be confused is that I was running all the 3.6 betas, the RC's and then 3.6 Final itself without any issues until early in the last week of January. Same addons, etc. Nothing new, which leads me to believe that maybe a 'system change' could be causing this, such as the latest security update. I can't confirm this, but it looks like the addons that have issues seem to be the ones that affect the UI, like putting something in the bottom statusbar (like Weave does), or adds something to the top navigation area, like 1Password, AdBlock, etc do.
Maybe it's not related, but I've seen today checking about:plugins, in FF 3.6 there are no plugins listed at all. After reinstalling FF 3.5.7 (just replaced the Firefox.app folder via Drag'n'Drop) about:plugins lists several installed plugins like Java, Flash, QuickTime etc.
I think I am seeing the same problem running Linux (FF 3.6). If I enable CookieSafe 3.0.5 or GreaseMonkey 0.8.20091209.4, Firefox doesn't start. No error messages or anything, just a new command prompt. If I start Firefox in safe mode and exits, I can run it for exacly one time after that. I think I have traced the outcome to the value of LastVersion in compatibility.ini; if it is set to "Safe Mode" (as it is the first time after starting in safe mode), Firefox starts normally. If it is set to "3.6_20100115133306/20100115133306" as it is otherwise, Firefox doesn't start.
I beleive that the status of this bug needs to be changed from Unconfirmed to New. The list of Firefox users experiencing this issue is growing daily: https://support.mozilla.com/en-US/forum/1/562036#threadId576315 This is NOT an isolated issue with a couple addons. There seems to be an issue within the addon engine itself.
(In reply to comment #21) > I believe I've found a workaround: > > http://support.mozilla.com/en/forum/1/562036?forumId=1&comments_threshold=0&comments_parentId=562036&comments_offset=20&comments_per_page=20&thread_style=commentStyle_plain#threadId576485 > > With any luck it should tell somebody where to start looking. Someone closed that thread as 'solved'; the message they flagged as the solution is that of a user saying that it DIDN'T fix it for him. I'm not sure what to do anymore; we're all telling Mozilla we have an issue and describing exactly what's going on. They're closing threads that document the issue as being solved when it isn't, and there's no reply or acknowledgement here. So, Firefox 3.6 is unusable on 2 of my Macs running Snow Leopard when 3.5.7 worked just fine. If Mozilla wants to claim there's still no issue, then there's not much I can do other than switch to Chrome until someone over there decides that our issue is worthy of their precious time. I'm tired of talking to the void.
New support thread opened here: http://support.mozilla.com/en-US/forum/1/590191
Just a note that I'm still having this issue. Furthermore, restarting the computer does not seem to fix it. I've also tried disabling all of the installed plugins (i.e. FLash, Java, Silverlight etc.) and this makes no difference. As long as at least 1 of the extensions I named in the first comment on this bug is enabled, Firefox will not start.
Neil, I'm not sure the bug you initially described is the same as the one that Tomas K and I have found the workaround for. When ours manifests, Firefox fails completely silently rather than produce the diagnostic spew you've seen. Perhaps this is an OS X vs Linux thing, though. Is yours at all sensitive to what's in compatibility.ini? And does visiting Safe Mode give you exactly one working Firefox session afterward?
Affects (at least some) Ubuntu 10.04 users too. For me it hits with xmarks and requestpolicy (at a min) I now have a /usr/local/bin that does an rm of compatibility.ini on every launch which is allowing launch (with extensions). Without that, firefox never launches. https://bugs.launchpad.net/firefox/+bug/518422
Debian 2.6.26-2-686: I'm experiencing the same exact behavior; it is indeed a bug. Works with new profile. After adding addons must deal with compatibility.ini each time to start, or silently fails to start.
As an option to deleting the file, the following edit works for me (again, each time before starting ff): perl -ni -e 'print unless /LastOSABI/' <your profile dir>/compatibility.ini That line seems to cause the trouble (for me, at least)
I don't understand. What's to confirm? Just google 'compatibility.ini firefox start'. Something's definitely broken.
I tried a strace -f /usr/bin/firefox... Looks like the issue ties to this read... 25377 read(3, 0xb7662058, 4096) = -1 EAGAIN (Resource temporarily unavailable) grep 0xb7662058 firefox-strace.txt |wc 425 4250 36975 Leading up to that read.. 25377 socket(PF_FILE, SOCK_STREAM, 0) = 3 25377 connect(3, {sa_family=AF_FILE, path=@"/tmp/.X11-unix/X0"}, 20) = 0 25377 getpeername(3, {sa_family=AF_FILE, path=@"/tmp/.X11-unix/X0"}, [20]) = 0 25377 uname({sys="Linux", node="lt", ...}) = 0 25377 access("/var/run/gdm/auth-for-ryan-D3btog/database", R_OK) = 0 25377 open("/var/run/gdm/auth-for-ryan-D3btog/database", O_RDONLY) = 4 25377 fstat64(4, {st_mode=S_IFREG|0600, st_size=47, ...}) = 0 25377 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb74d1000 25377 read(4, "\1\0\0\2lt\0\0010\0\22MIT-MAGIC-COOKIE-1\0\20\27"..., 4096) = 47 25377 read(4, "", 4096) = 0 25377 close(4) = 0 25377 munmap(0xb74d1000, 4096) = 0 25377 getsockname(3, {sa_family=AF_FILE, NULL}, [2]) = 0 25377 fcntl64(3, F_GETFL) = 0x2 (flags O_RDWR) 25377 fcntl64(3, F_SETFL, O_RDWR|O_NONBLOCK) = 0 25377 fcntl64(3, F_SETFD, FD_CLOEXEC) = 0 25377 poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}]) 25377 writev(3, [{"l\0\v\0\0\0\22\0\20\0\0\0", 12}, {"", 0}, {"MIT-MAGIC-COOKIE-1", 18}, {"\0\0", 2}, {"\0273\203\3672'\0\367\360\375\" \377s\17\256", 16}, {"", 0}], 6) = 48 25377 read(3, 0xb7603a40, 8) = -1 EAGAIN (Resource temporarily unavailable) 25377 poll([{fd=3, events=POLLIN}], 1, -1) = 1 ([{fd=3, revents=POLLIN}]) 25377 read(3, "\1\0\v\0\0\0\3\3", 8) = 8 25377 read(3, "hX\243\0\0\0\340\3\377\377\37\0\0\1\0\0\24\0\377\377\1\7\0\0 \10\377\0\0\0\0"..., 3084) = 3084 25377 poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}]) 25377 writev(3, [{"b\0\5\0\f\0\0\0BIG-REQUESTS", 20}], 1) = 20 25377 poll([{fd=3, events=POLLIN}], 1, -1) = 1 ([{fd=3, revents=POLLIN}]) 25377 read(3, "\1\0\1\0\0\0\0\0\1\221\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0", 4096) = 32 25377 poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}]) 25377 writev(3, [{"\221\0\1\0", 4}], 1) = 4 25377 poll([{fd=3, events=POLLIN}], 1, -1) = 1 ([{fd=3, revents=POLLIN}]) 25377 read(3, "\1\0\2\0\0\0\0\0\377\377?\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0", 4096) = 32 25377 read(3, 0xb7662058, 4096) = -1 EAGAIN (Resource temporarily unavailable) 25377 poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}]) 25377 writev(3, [{"7\0\5\0\0\0\340\3\255\1\0\0\10\0\0\0\377\377\377\0\24\0\6\0\255\1\0\0\27\0\0\0"..., 44}, {NULL, 0}, {"", 0}], 3) = 44 25377 poll([{fd=3, events=POLLIN}], 1, -1) = 1 ([{fd=3, revents=POLLIN}]) 25377 read(3, "\1\10\4\0,\0\0\0\37\0\0\0\0\0\0\0\255\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 4096) = 208 25377 read(3, 0xb7662058, 4096) = -1 EAGAIN (Resource temporarily unavailable) 25377 poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}]) 25377 writev(3, [{"b\0\5\0\t\0\340\3", 8}, {"XKEYBOARD", 9}, {"\0\0\0", 3}], 3) = 20 25377 poll([{fd=3, events=POLLIN}], 1, -1) = 1 ([{fd=3, revents=POLLIN}]) 25377 read(3, "\1\0\5\0\0\0\0\0\1\223v\251\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0", 4096) = 32 25377 read(3, 0xb7662058, 4096) = -1 EAGAIN (Resource temporarily unavailable) Just after the last unavailable (400+), firefox removes the 'lock' file in the profile dir. I'd rather not attach the full strace since it has some personal bits from the profile - if a dev would like to review the output I'd be happy to provide it directly.
Above looks like x related auth issue to me /tmp/.X11-unix/X0 , then tries to set auth, then fails to read and closes.. fwiw - Replicated with nightly: http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-firefox-3.6.x/firefox-3.6.2pre.en-US.linux-i686.tar.bz2 md5sum: 50e87e4dcbcf2dd5bed29e80c5ab1b4e firefox-3.6.2pre.en-US.linux-i686.tar.bz2 Would sure be cool if a dev joined the bug report. :)
hmm... extension devs say it's Mozilla's problem. Mozilla says it's extension devs problem. After all the finger pointing, we've still got tons of FF users with a browser that will not launch. How is this bug not getting more attention? For now, I'm just using a workaround to rm -f compatablitity.ini in the launcher script, but this is unacceptable long-term. Is there any debugging information I could provide to help expedite this critical show-stopper?
we have a similar issue in ubuntu. has something to do with extensions being reachable through a link on the filesystem _and_ extensions shipping .xpt files. https://launchpad.net/bugs/518422 I attached an unverified first patch for that issue there: https://bugs.edge.launchpad.net/ubuntu/+source/firefox/+bug/518422/comments/17 ... but i doubt its the same problem for all reporters in this bug.
(In reply to comment #33) > we have a similar issue in ubuntu. has something to do with extensions being > reachable through a link on the filesystem _and_ extensions shipping .xpt > files. > > https://launchpad.net/bugs/518422 > > I attached an unverified first patch for that issue there: > > https://bugs.edge.launchpad.net/ubuntu/+source/firefox/+bug/518422/comments/17 > > ... but i doubt its the same problem for all reporters in this bug. See bug #551152
after a long time, i get it now again. some month ago, i erased almost everything in my profile, and started all over. but that was the only way to fix it. now i have my settings from yesterday on time machine (os x 10.6.2). they work. firefox finds updates for autopager, downloadhelper, firebug and stylish. if i update any of them (all together, or just one), firefox won't launch after restart. back to time machine backup.. works. is there anything i can send to somebody to have a look? which file might be the "bad" one?
I had the same problem. Firefox 3.6 as distributed by Ubuntu Linux. Firefox starts in safe mode and *first time after* running in safe-mode, otherwise it fails to start. Removing compatibility.ini before start resolves the problem. In my it turned out Prism extension was responsible, once I disabled it, the problem disappeared. But see for example http://getsatisfaction.com/foxmarks/topics/firefox_3_6_fails_to_launch_with_xmarks_installed_rm_compatibility_ini_works_around_issue It may be that the problem happens only on 32-bit, I did not experience it on 64-bit Ubuntu
And, with prism extension isntalled, here is the "after-safe-mode" compatibility.ini with which firefox starts: [Compatibility] LastVersion=Safe Mode LastOSABI=Linux_x86-gcc3 LastPlatformDir=/usr/lib/firefox-3.6 LastAppDir=/usr/lib/firefox-3.6 and here is the "after-normal-mode" compabibility.ini with which firefox fails to start: [Compatibility] LastVersion=3.6_20100301022810/20100301022810 LastOSABI=Linux_x86-gcc3 LastPlatformDir=/usr/lib/firefox-3.6 LastAppDir=/usr/lib/firefox-3.6
(In reply to comment #36) > It may be that the problem happens only on 32-bit, I did not experience it on > 64-bit Ubuntu I have experienced it on both 32-bit and 64-bit OS X, but in both cases I was using the 32-bit build of Firefox.
in addition to my last post: upgrading to FF 3.6.2 fixed it for me. after upgrading, i could update the extensions in question and had no problems.
I would also like to add that upgrading to Firefox 3.6.2 has also fixed the problem for me, at least for now.
3.6.2 fixes it for me as well. Comment #13 author might want to think about that.
Neil/Stephen - on what platform? On Ubuntu 10.04 beta - I tried a mozilla.org download of 3.6.2 - and there was no change to the behavior for me. :(
The problems still exists for certain users with 3.6.2 : https://bugzilla.mozilla.org/show_bug.cgi?id=554794
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago → 16 years ago
Resolution: --- → DUPLICATE
I was wrong; 3.6.2 didn't fix it for me (Ubuntu 8.04 + Ubuntuzilla). I was fooled into thinking it had because I had forgotten that on my computer it only manifests for user accounts other than mine.
Hi from Germany, same problem here. MacOS 10.6.3, FF 3.6.3. Very frustrating. Plugins which will work: Adblock Plus Adblock Plus Element Hiding Helper All-in-One Gestures Counterpixel Deutsches Wörterbuch ebay Toolbar Feed Filter Fission LiveClick Long URL Please NoScript Quick Locale Switcher QuickJava ReloadEvery TinEye Reverse Trashmail.net UrlbarExt User Agent Switcher Plugins which DONT WORK: DownloadHelper DownthemAll! Greasemonkey Modify Headers Stylish Weave At least i've seen a couple of problems here with GreaseMonkey, Downthemall and Weave. So what do these plugins have in common? Is this already a known bug to mozilla?
You need to log in before you can comment on or make changes to this bug.