Known Issues

  1. On Windows and Mac OS X, installation level 2 is known to be partially or wholly incompatible with
    • Covenant Eyes
    • K9
    • Net Nanny
    • Qustodio
    • X3watch
    • BullGuard Antivirus
    • possibly other filters

    When installed along with any of these products, the Internet may become inaccessible (try restarting all browsers). If problems persist, uninstall Pluckeye or one of the conflicting filters.

  2. On Windows 7, Vista, and XP computers that do not have Microsoft hotfix 2590550 installed and that have some other products, may lose Internet connectivity completely when Pluckeye is at installation level 2. The root cause is as yet unknown.
  3. On some older versions of Windows, Pluckeye will not install. Pluckeye should install correctly on Windows 7 Service Pack 1 or newer, Windows Vista with Service Pack 2, or Windows XP with Service Pack 3.
  4. On Mac OS X, per-program rules do not yet have any effect.
  5. On Mac OS X, at installation level 2, iTunes and the App Store are blocked on some machines. The current workaround is to periodically drop down to level 1 to apply updates from the App Store.
  6. On Mac OS X, in Chrome, the lockdown and blackout buttons do not work because the confirmation dialog box is immediately closed by Chrome.
  7. Pluckeye only supports Linux x86-64 distributions with glibc 2.14 or above (circa 2012).
  8. Many distributions of Linux are not well supported. Pluckeye is most likely to work on Debian-based and Arch-based distributions. Pluckeye is not regularly tested on Gentoo or RHEL-based systems such as Fedora, and may not work on such systems. If you would like to volunteer to help test such systems, feel free to email
  9. On uncommon Linux distributions that do not follow the Linux Standard Base (e.g. SliTaz, Puppy Linux), Pluckeye may not install. Pluckeye may still work on such distributions if the necessary prerequisites are installed (e.g., perl).
  10. On some versions of Linux, at installation level 2, Google Chrome (google-chrome-stable) will not start. Chromium (chromium or chromium-browser), on the other hand, should work.
  11. On Linux x86-64, at installation level 2, many electron-based applications fail to start. If this happens to an app you care about, do report it to Pluckeye staff.
  12. In Firefox 57+, especially on slow machines, the Pluckeye panel may only show a "help" button. In most cases the full panel is shown a few seconds after Firefox starts.
  13. If Firefox is installed after Pluckeye, then the Pluckeye button will not appear in Firefox automatically. To fix this, go to about:addons and enable the Plucki extension.
  14. Already existing firefox processes are not affected when a user types the following in a console:

    pluck add "package foo"

    Firefox must be restarted for package settings to take effect.

  15. In Firefox 42 through Firefox 46, two Pluckeye buttons appear in the toolbar by default. To workaround the issue, go to about:addons and disable the one named "Pluckeye". However, be aware that this will also disable Pluckeye in any newer Firefoxes that use the same profile. Speaking of which, why are you using Firefox 42 through 46?
  16. Pluckeye only supports Chrome 45 or newer.
  17. When Chrome starts or a new tab is opened, the page sometimes says "The requested URL /__pluckeye_bounce__%2F_%2Fchrome%2Fnewtab was not found on this server. That's all we know.". Navigating to a site should work fine.
  18. If Pluckeye is set to level 2 before integrating with Chrome (e.g. before Chrome is even installed), or if the Pluckeye extension is removed from Chrome while at level 2, then Chrome will be completely blocked from the Internet. To fix this, drop down to level 1 temporarily, start Chrome, wait for Pluckeye to integrate with Chrome, and then resume using level 2. If the extension was removed by the user, you will need to either remove your Chrome profile or install Pluckeye from the Chrome Web Store.
  19. If the user visits some particular websites, such as,, that host certain types of ads, the CPU will spin while a tab is open on that website. The root cause is thought to be javascript on the page that continually attempts to load ads that are in turn blocked by Pluckeye. The current workaround is to either allow all content on such pages or to close such tabs. This issue seems to affect Firefox more often than Chrome.
  20. Sometimes and Onetime settings permanently overwrite already existing settings that match the same setting. It is best to avoid using sometimes and onetime settings for hosts or urls that also have permanent settings (this might be fixed eventually).
  21. Sometimes unreliability. The sometimes rules sometimes interact badly with non-sometimes rules, or with each other. The whole sometimes system will soon be replaced. If you want to avoid sometimes rules altogether, use

    pluck add "nosometime"

    If you would like to force a different algorithm with respect to the delay imposed on sometimes rules, use

    pluck add "slowsometime"

    It is hoped these options will not be necessary for long.

  22. Invoking pluck with bogus settings does not always yield an error. For example, if a user invokes

    pluck add "program block firefox"

    rather than the correct

    pluck add "program firefox blackout"

    then instead of rejecting the bad syntax, pluck accepts it as a rule that does nothing on the program "block".

  23. When upgrading from one major version of Pluckeye to another, pending settings are lost. The workaround is to re-add the pending settings after upgrading.
  24. If a sometimes rule is removed while it is in effect, the corresponding time-bounded setting remains. The workaround is to remove the corresponding setting manually:

    pluck add "sometimes 0-24 allow" pluck del "sometimes 0-24 allow"

    Also needed:

    pluck del ""

  25. Attempting to reduce the delay on the settings page by double-clicking the "Apply" button on that page will cause the delay to remain unchanged. This occurs because the first click sets a pending delay, and the second click removes it. The workaround is to only click "Apply" once.
  26. In Chrome, if a button that requires confirmation is clicked (e.g. abort, lockdown, or blackout), the confirmation box may render outside of the visible area. One workaround is to resize the Chrome window as that sometimes makes the confirmation box visible.