- Android Browser Using Extra Space? Check Gears!
Android's web browser stores several types of data: cache, history, cookies and passwords...and Gears, which might use more memory than you'd expect!
- Can’t Log into Feedly or Pinterest on Firefox 40? Check Ghostery!
After upgrading to Firefox 40, logging into Feedly with Google or Pinterest with a Facebook account failed. It turned out to be Ghostery.
- Fedora 7 Problems With Glint Video Driver
Grab the Live CD first and make sure that all your hardware works properly. If not, see if the fix is available before you actually upgrade.
- Fixing Flash in Fedora Core 5
Flash hard-codes the paths where it looks for fonts, instead of letting the X server tell it where to look.
- Fixing Twhirl
Just delete the entire ~/.appdata/Adobe/AIR/ELS/ folder and start from the ground up.
- Flock and self-hosted WordPress
If you can't post to your self/third-party-hosted WordPress blog through a program other than the website, and you use ModSecurity - check those settings.
- How to Get Rid of Windows Live Messenger
Start to uninstall Windows Live Essentials, then choose which pieces you want to get rid of. And WLM will go away.
- Jetpack Related Posts Missing on an SSL WordPress Site?
If you can't get Jetpack's related posts to load on self-hosted WordPress running HTTPS, check your SSL settings to see if you need to disable RC4.
- Nepomuk is Not Running
KMail kept tossing errors on launch because an old config was trying to load the wrong Nepomuk backend.
- NVIDIA on Fedora 27: Bad Resolution and Painful Mouse Lag (Fixed)
As of 2017, Wayland didn't work with the binary NVIDIA drivers, and the system would lag painfully. If you tell GDM not to use Wayland, it will fall back to the older display system.
- PHP5 and WP Cache 2
Finding and fixing errors with WordPress' WP Cache plugin and PHP5.
- Resolving SELinux audit errors on boot in Fedora Core 4
Rebuild the initrd so it can label the boot filesystem with the new policy.
- Workaround for Gmail being blocked by “Temporary Error” in Firefox on Fedora
In this case it was a Fedora-specific issue, but it could be worked around by holding down shift and hitting reload.