The important concept to bear in mind when discussing software issues with Linux apologists is the "Linux Fault Threshold". Clever use of this concept helps you to avoid losing your temper with someone who might actually be able to render practical help, while ensuring that you give the correct dose of venom (60cc of scorpion juice, administered per anem with a rusty syringe) to the vast crowd of mindless apologists who just want you to use their pet operating system because it makes them feel good and gives them something to boast about on Slashdot. I provide this as a service to all the blind, alcoholic, incontinent grandmothers out there who appear to be installing Linux without any trouble if the Slashdot comments on any article remotely related to user interface design are to be believed.
The Linux Fault Threshold is the point in any conversation about Linux at which your interlocutor stops talking about how your problem might be solved under Linux and starts talking about how it isn't Linux's fault that your problem cannot be solved under Linux. Half the time, the LFT is reached because there is genuinely no solution (or no solution has been developed yet), while half the time, the LFT is reached because your apologist has floundered way out of his depth in offering to help you and is bullshitting far beyond his actual knowledge base. In either case, a conversation which has reached the LFT has precisely zero chance of ever generating useful advice for you; it is safe at this point to start calling the person offering the advice a fucking moron, and basically take it from there. Here's an example taken from IRC logs to help you understand the concept.