Seeking ban on MQM: Respondent to file comments on Nov 1

SHC Chief Justice Sajjad Ali Shah asked the lawyer to make arguments on the next hearing


Our Correspondent October 27, 2016
PHOTO: EXPRESS

KARACHI: The Sindh High Court (SHC) granted on Thursday time to Barrister Farogh Nasim to file comments on a petition seeking to ban the Muttahida Qaumi Movement (MQM) and disqualification of its legislators over the alleged August 22 anti-state speech of its founder Altaf Hussain.

While heading a two-judge bench, SHC Chief Justice Sajjad Ali Shah asked the lawyer to make arguments on the next hearing.

During hearing, Nasim filed his power of attorney on behalf of the MQM legislators and sought time to file comments. Allowing the request, the bench fixed the matter for November 1.

Maulvi Iqbal Haider, a lawyer, had approached the court seeking direction for the federal ministries of law, justice and interior and provincial authorities to ban the MQM.

In his petition, Haider had said that the MQM legislators had neither agitated nor raised any slogans against their party’s founder; however, for the sake of saving their own skins, they disassociated themselves from the speech.

On September 29, the Ministry of Law and Justice had informed the court that it had nothing to do with banning the MQM as the issue is related to the Interior Ministry.

The ministry maintained that the petitioner has challenged Hussain’s August 22 speech and prayed that the respondents may be directed to take legal action against him and respondents number nine to 81 (MQM legislators).

“From the perusal of the petition, it appears that the issues involved therein substantially and exclusively relate to the interior ministry and other respondents, which have already been impleaded as necessary parties in the instant petition,” the petition added.

Published in The Express Tribune, October 28th, 2016.

 

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ