Tag: troubleshooting

Major Linux Problems or Why Linux is not (yet) Ready for the Desktop, 2012 edition

Major Linux Problems or Why Linux is not (yet) Ready for the Desktop, 2012 edition

Every operating system has its problems.  Some things work better than in others, some do worse.  Here is an interesting (and very up-to-date) overview of the problems in the Linux space.  The good thing about it is that it’s not just bashing Linux over Windows or Mac and it doesn’tjust wine about minor things here and there.  There are issues all over, some are being worked on, and some are not, for a variety of reasons.  But just knowning these issues is already a good start in fixing them.

Solution to WordPress with WP Super Cache blank pages problem

This took me a while to figure out, so I’ll post it here in case someone else ever gets into this problem.  After enabling WP Super Cache for a project at work, we’ve started seeing really weird and really random white page issues.  WordPress would show a blank page and then a few minutes later it would start working again.  But then it would disappear and so on and so forth.

Tracking the issue down, I’ve tweaked the WP Super Cache configuration quite a bit, but that didn’t help.  And I was sure that it was related to WP Super Cache, since periods of appearing and disappearing were consistent with cache timeout settings.  Browsing through WordPress support forums (threads one, two, and three) game an idea that it wasn’t just WP Super Cache on its own, but a combination of WP Super Cache plugin with something else on the system.

After a lengthy troubleshooting process, I think I nailed it.  APC – an alternative PHP cache module – wasn’t friendly with WP Super Cache.  So, as a short-term solution to the problem, I’ve disabled the APC and now everything seems to work well.  I’m a bit busy now to troubleshoot the problem further, but if you have any idea of why that could be happening, please share.

Huge, huge thanks to git bisect! With its help, I …

Huge, huge thanks to git bisect! With its help, I just sorted out a huge argument about who removed a piece of code and when.  With an actively developed project among few developers and branches, it’s not trivial to say when the change was introduced.  Unless, of course, you are using git bisect.  Every developer should know how to use it.