A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::open($save_path, $name) should either be compatible with SessionHandlerInterface::open(string $path, string $name): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 6

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::close() should either be compatible with SessionHandlerInterface::close(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 7

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::read($session_id) should either be compatible with SessionHandlerInterface::read(string $id): string|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 8

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::write($session_id, $session_data) should either be compatible with SessionHandlerInterface::write(string $id, string $data): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 9

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::destroy($session_id) should either be compatible with SessionHandlerInterface::destroy(string $id): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 10

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::gc($maxlifetime) should either be compatible with SessionHandlerInterface::gc(int $max_lifetime): int|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 11

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 284

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_set_cookie_params(): Session cookie parameters cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 291

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 306

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 316

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 317

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 318

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 319

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 377

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_set_save_handler(): Session save handler cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 110

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_start(): Session cannot be started after headers have already been sent

Filename: Session/Session.php

Line Number: 143

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

NRIPage | Articles | Karnataka CM Siddaramaiah Faces Rs 500 Crore Bribery Allegation Over Mining Lease Renewals | Get Indian Desi Latest Political News & Updates in USA. Get domestic, republic government updates - NRI Page
Edit

Karnataka CM Siddaramaiah Faces Rs 500 Crore Bribery Allegation Over Mining Lease Renewals

Karnataka CM Siddaramaiah Faces Rs 500 Crore Bribery Allegation Over Mining Lease Renewals

Karnataka Chief Minister Siddaramaiah has landed in fresh controversy after social activist H Ramamurthy Gowda submitted a formal petition to Governor Thaawarchand Gehlot, seeking sanction to prosecute the CM under the Prevention of Corruption Act, 1988. The complaint alleges that Siddaramaiah accepted a Rs 500 crore bribe in 2015 for renewing eight mining leases without opting for the auction route. The petition, accessed exclusively by India Today, claims that Siddaramaiah’s decision as then-Chief Minister led to a massive loss of Rs 5,000 crore to the state exchequer. Some of the mining leases reportedly renewed by him were allegedly linked to firms under investigation in the infamous Karnataka mining scam. According to the complaint, Siddaramaiah bypassed auction procedures that would have ensured competitive bidding and state revenue, choosing instead to renew the leases directly—raising suspicions of corruption and favoritism.

Charges Under Prevention of Corruption Act and Bharatiya Nyaya Sanhita

Gowda’s petition requests prosecution under several sections of the Prevention of Corruption Act, including:

  • Section 7: Public servant taking gratification

  • Section 9: Taking gratification to influence a public servant

  • Section 11: Receiving valuable things from persons involved in official transactions

  • Section 12: Abetment of offenses

  • Section 15: Attempting to commit offenses

In addition, the petition invokes a series of charges under the Bharatiya Nyaya Sanhita (BNS):

  • Sections 59 & 61: Concealment of designs to commit offenses

  • Section 201: Destruction of evidence

  • Section 227: Violation of remission conditions

  • Sections 228 & 229: Interfering with judicial proceedings and impersonation

  • Section 239: Possession of counterfeit currency

  • Sections 314, 316(5), 318(1): Offenses involving miscarriage and secret disposal of bodies

  • Section 319, 322, 324(2), 324(3): Grievous hurt and extortion

  • Sections 335 to 340: Forgery and use of forged documents

Governor Seeks Legal Opinion

The Governor has acknowledged the complaint and forwarded it to the state’s legal department for review. Additionally, he has asked the Solicitor General to assess the submitted evidence before making a final decision on whether to grant permission for prosecution. Sources confirmed that Gowda met with Governor Gehlot on April 1, 2025, after being invited for a detailed discussion. The Governor’s legal advisors have scrutinized the documents, which reportedly include financial records indicating a sharp increase in Siddaramaiah’s assets post-lease renewals.

Political Reactions and Public Debate

BJP leaders have been quick to respond to the unfolding developments. MLA Ashwath Narayan welcomed the activist's move and stressed the need to examine the supporting documents thoroughly. Suspended BJP MLA Basanagouda Patil Yatnal took to social media platform X, alleging that the CM’s actions resulted in substantial financial damage to the state. “A social activist by the name of Ramamurthy Gowda has complained to the Governor saying that the permission accorded by Chief Minister Shri Siddaramaiah to renew 7 licenses of Ramghad Minerals in his first term caused a Rs 5,000 crore loss to the state exchequer,” Yatnal posted.

Yatnal further claimed that documents presented by Gowda point to a notable rise in Siddaramaiah’s personal assets during the period, demanding an explanation from the CM regarding the deviation from established rules in granting the mining lease renewals. “Chief Minister Siddaramaiah, who claims that he is the messiah of the poor, should explain why he gave renewal to the mines against the prevalent rules and substantiate the allegation of the increase in his assets,” Yatnal wrote.

With the Governor’s office now officially engaged and a legal review underway, the case could intensify political tensions in Karnataka. If the Solicitor General recommends prosecution, Siddaramaiah may face formal legal proceedings under multiple sections of corruption and criminal law. The Chief Minister has yet to issue an official statement in response to the allegations. The coming days will be crucial as the Governor weighs legal advice and public sentiment before deciding whether to allow the case to move forward. The developments are expected to have significant political implications for the ruling party in Karnataka as the state navigates a period of increasing scrutiny over governance and transparency.

What is your response?

joyful Joyful 0%
cool Cool 0%
thrilled Thrilled 0%
upset Upset 0%
unhappy Unhappy 0%
AD
AD