the bugs that are most likely related to user configuration (like a specific hardware, codec or driver prob) or impossible to find a logical reason at the moment. The problems in this category might be fixed in future versions as users keep confirming them with additional information.

I was facing the problem till 3.1 and not yet tried 3.2. Will try 3.2 and let you know. To be clear, I am talking about the original problem posted by Shubam bro in the first post of scanning INSAT 4A at 83e. But any idea if this is fixed in 3.2?