You should: Sign up > Write articles > tell people about your articles > Monetize them > Earn money  > learn/do/earn more

2020 Delhi riots

From Wikiafripedia, the free afripedia (encyclopedia)
Jump to navigation Jump to search

2020 Delhi riots
North East Delhi Riots 2020 (1).jpg
Relief camps for Delhi riot-affected victims.jpg
(top) Muslim homes and businesses were set on fire during the rioting in Shiv Vihar, Delhi.[lower-alpha 1]
(bottom) A relief camp at Eidgah in Mustafabad, Delhi set up by the Government of Delhi[lower-alpha 2] and the Muslim Waqf board, with beds for 800 women and 700 men, and with doctors from St Stephens Hospital and Holy Family Hospital volunteering.[lower-alpha 3]
Date23 February 2020 – 29 February 2020 (6 days)[citation needed]
Location
28°40′55″N 77°16′26″E / 28.682°N 77.274°E / 28.682; 77.274Coordinates: 28°40′55″N 77°16′26″E / 28.682°N 77.274°E / 28.682; 77.274
Caused by
Goals
Methods
Casualties
Death(s)53[10]
Injuries200+[9]
Arrested2200 (including detained)[11]
<mapframe latitude="28.676792" longitude="77.273456" zoom="11" width="300" height="227" align="center">{
 "type": "FeatureCollection",
 "features": [
   {
     "type": "Feature",
     "properties": {},
     "geometry": {
       "type": "Point",
       "coordinates": [
         77.27542877197266,
         28.685768802287086
       ]
     }
   },
   {
     "type": "Feature",
     "properties": {},
     "geometry": {
       "type": "Point",
       "coordinates": [
         77.26186752319337,
         28.671310915880834
       ]
     }
   },
   {
     "type": "Feature",
     "properties": {},
     "geometry": {
       "type": "Point",
       "coordinates": [
         77.27251052856447,
         28.693900486320242
       ]
     }
   },
   {
     "type": "Feature",
     "properties": {},
     "geometry": {
       "type": "Point",
       "coordinates": [
         77.28315353393556,
         28.703085517776877
       ]
     }
   },
   {
     "type": "Feature",
     "properties": {},
     "geometry": {
       "type": "Point",
       "coordinates": [
         77.27010726928712,
         28.703687786758284
       ]
     }
   },
   {
     "type": "Feature",
     "properties": {},
     "geometry": {
       "type": "Point",
       "coordinates": [
         77.27439880371095,
         28.716786279385452
       ]
     }
   }
 ]
}</mapframe>

The 2020 Delhi riots, or North East Delhi riots, were multiple waves of bloodshed, property destruction, and rioting in North East Delhi, beginning on 23 February and caused chiefly by Hindu mobs attacking Muslims.[12][13] Of the 53 people killed, two-thirds were Muslims who were shot, slashed with repeated blows or set on fire.[14][15][16] The dead also included a policeman, an intelligence officer and over a dozen Hindus, who were shot or assaulted.[15] More than a week after the violence had ended, hundreds of wounded were languishing in inadequately staffed medical facilities and corpses were being found in open drains.[17] By mid-March many Muslims had remained missing.[12]

Muslims were marked as targets for violence.[18][19][20] In order to have their religion ascertained, Muslim males—who unlike Hindus are commonly circumcised—were at times forced to remove their lower garments before being brutalised.[21][22][23] Among the injuries recorded in one hospital were lacerated genitals.[24][25] The properties destroyed were disproportionately Muslim-owned and included four mosques, which were set ablaze by rioters.[26] By the end of February, many Muslims had left these neighbourhoods.[13] Even in areas of Delhi untouched by the violence, some Muslims had left for their ancestral villages, fearful for their personal safety in India's capital.[22]

The riots had their origin in Jaffrabad, in North East Delhi, where a sit-in by women against India's Citizenship (Amendment) Act, 2019 had been in progress on a stretch of the SeelampurJaffrabadMaujpur road.[27][28] On 23 February 2020, a leader of the ruling Hindu nationalist Bharatiya Janata Party (BJP), Kapil Mishra, called for Delhi Police to clear the roads, failing which he threatened to do so himself with help from his supporters.[29][30] After Mishra's ultimatum, violence erupted.[31] Initially, Hindu and Muslim attacks were equally lethal.[32] Most deaths were attributed to gunfire.[33] By 25 February 2020, the balance had shifted.[32] Rioters wearing helmets and carrying sticks, stones, swords or pistols, and the saffron flags of Hindu nationalism entered Muslim neighbourhoods, as the police stood by.[34][35] Chants were heard of "Jai Shri Ram" ("Victory to Lord Rama"), a slogan to which the ruling party is partial.[16] In the neighbourhood of Shiv Vihar, groups of violent Hindu men attacked Muslim houses and businesses for three days, often firebombing them with cooking gas cylinders and gutting them without resistance from the police.[36] In some instances, Muslims countered perceived threats by returning the violence; on the 25th a Muslim mob approached a Hindu neighbourhood throwing stones and Molotov cocktails and firing guns.[37] During this time, stories were also told of Sikhs and Hindus coming to the aid of besieged Muslims;[38] in some neighbourhoods, the religious communities cooperated in protecting themselves from violence.[39]

The Indian government swiftly characterised the violence as spontaneous.[13] The Delhi Police, which is directly overseen by India's central government, moved into the area in strength on 26 February after the Delhi High Court had ordered it to help remove injured victims to hospitals.[33][40] India's national security advisor, Ajit Doval, visited the area; the prime minister, Narendra Modi, made an appeal for peace on Twitter.[33] The Delhi police were accused by the affected citizens, eyewitnesses, human rights organizations and Muslim leaders around the world of falling short in protecting Muslims.[17] Videos showed police acting in a coordinated manner against Muslims, on occasion purposefully helping Hindu gangs.[41] Witnesses said some police officers joined the attacks on Muslims.[42]

After the violence had abated in the thickly-settled mixed Hindu-Muslim neighbourhoods of North East Delhi, some Hindu organisations continued to parade alleged Hindu victims of Muslim violence in an attempt to reshape the accounting of events and to further inflame hostility towards Muslims.[43] About 1,000 Muslims sought shelter in a relief camp on the fringes of Delhi.[44] Gangs of Hindus appeared in several Muslim neighbourhoods in the days preceding the Hindu festival of Holi, celebrated in 2020 on 9 March, to scare Muslims into abandoning their homes.[45] In the midst of prevailing anti-Muslim attitudes, senior lawyers in Delhi were not accepting cases on behalf of the riot victims.[46] Among Muslims who have continued to live in their neighbourhoods, the violence has created potentially long-living divisions.[47] For at least two weeks post-rioting, Hindus and Muslims avoided each other during the day and at night blocked their lanes with barriers.[47]

Background[edit source | edit]

Protests began across India in December 2019 in response to the passage of the Citizenship (Amendment) Act (CAA), which allows fast-tracked naturalisation for immigrants from Pakistan, Bangladesh and Afghanistan belonging to six religions vis-à-vis Hinduism, Sikhism, Christianity, Zoroastrianism, Jainism and Buddhism. The Act has been seen as discriminatory to Muslims and threatening to their existence in India when combined with the anticipated National Register of Citizens (NRC).[48][49][50][51][52]

Several anti-CAA protests were held in New Delhi. Some protesters burned vehicles and pelted stones at Security forces.[53] In Shaheen Bagh, protesters blocked roads, which led to a traffic jam.[54]

The Delhi Legislative Assembly election was held on 8 February 2020, in which the Bharatiya Janata Party (BJP) was defeated by the Aam Admi Party; widespread usage of incendiary slogans by BJP equating the protesters to anti-national elements and asking for them to be shot were noted.[lower-alpha 4] Delhi BJP chief, Manoj Tiwari, has since attributed hate speeches by fellow party-candidate Kapil Mishra (who coined the slogans) as a cause of the BJP defeat.[56][57]

On 22 February, around 500 to 1,000 protesters, including women, began a sit-in protest near the Jaffrabad metro station. The protest blocked a stretch of SeelampurJaffrabadMaujpur road, as well as the entry and exit to the metro station.[58][59] According to the protesters, the sit-in was in solidarity with the Bharat Bandh called by the Bhim Army, which was scheduled to begin on 23 February. Police and paramilitary personnel were deployed at the site.[60]

Timeline[edit source | edit]

23 February and incitement[edit source | edit]

On 23 February between 3.30 p.m. and 4 p.m., Bharatiya Janata Party (BJP) leader Kapil Mishra and his supporters reached a protest site at Maujpur Chowk "to give an answer to Jaffrabad [blockade]".[6] Mishra then spoke out in a rally against the CAA protesters[lower-alpha 5][48] and threatened to take matters into his own hands if the police failed to disperse the protesters from the Jaffrabad and Chand Bagh areas in three days' time.[4][62][63] This has been widely reported to be the major inciting factor:[56][64] however, Mishra rejects the allegations.[65]

At approximately 4 p.m., protesters were reported to have hurled stones at the pro-CAA gathering at Maujpur Chowk and near a temple.[66] Between 9 and 11 p.m., clashes broke out between the anti-CAA and pro-CAA demonstrators in Karawal Nagar, Maujpur Chowk, Babarpur and Chand Bagh. Vehicles were gutted and shops were destroyed.[6][67] The police used baton charge and tear gas to disperse the crowd.[68][66]

Seven hundred emergency calls were made to the police control room that day.[69]

24 February[edit source | edit]

Charred cars in North East Delhi after mobs set fire to the area.[lower-alpha 6]
Gokulpuri Tyre Market after mobs set fire to the shops.[lower-alpha 7]

On the morning of 24 February, a pro-CAA mob arrived at an anti-CAA protest site at Jaffrabad and refused to leave until the anti-CAA protesters left the area. At around 12:30 p.m., protesters wearing masks and waving swords clashed with the police force.[66] By afternoon, violent clashes broke out in several areas of North East Delhi, including in the Gokulpuri and Kardampuri areas.[71] There was heavy stone pelting and vandalism of property. The police used tear gas and lathi charge against the protesters in the Chand Bagh area,[72][73] but the protesters retaliated by throwing stones at the police.[74] A head constable, Ratan Lal, died of a bullet injury in this clash.[75][76][77][lower-alpha 8]

In Bhajanpura, in afternoon a group numbering around 2000 attacked a petrol pump, chanting slogans of Āzādī (transl. 'Freedom') and carrying petrol bombs, sticks and weapons. They attacked the owner and employees of the petrol pump with sticks, burning vehicles and petrol tanks after looting available cash.[66][78][79]

Violence was also reported from the areas of Seelampur, Jaffrabad, Maujpur, Kardampuri, Babarpur, Gokulpuri and Shivpuri.[80][81] Section 144 (ban on assembly) was imposed in all the affected areas but to little effect.[82][83] In Jaffrabad, a man, allegedly linked with the anti-CAA side, opened fire at the police, before being arrested days later in Uttar Pradesh.[84][85]

In Shiv Vihar, in the afternoon, several shops and homes owned by Hindus were torched by a Muslim mob. Later, mutilated bodies of workers were recovered from the site. A massive parking lot with 170 cars was burned by a mob.[86][87][88] In the evening around 8:30 p.m., a tyre market (predominantly owned by Muslims) was set on fire with the screaming of "Jai Shri Ram" being heard.[71][75] Later that night, at around 10:30 p.m., a mob beat a Hindu man and his elder father travelling on a scooter with sticks, stones and swords while screaming "Allahu akbar". The man died on the spot.[89] On that day, five people died including a police constable and four civilians.[76]

3,500 emergency calls were made to the police control room that day.[69][90] The Delhi Fire Service stated that it had attended 45 calls from areas in northeast Delhi and three firemen were injured, on 24 February. While attending calls, a fire engine was attacked with stones, while another fire engine was set on fire by rioters.[91]

25 February[edit source | edit]

The Auliya Mosque in Shiv Vihar was firebombed with gas cylinders.[lower-alpha 9]

On 25 February, stone pelting was reported from Maujpur, Brahampuri and other neighbouring areas. Rapid Action Force were deployed in the worst affected areas.[91] It was a full-blown riot with intense religious sloganeering and violence from both sides.[93]

In Ashok Nagar, a mosque was vandalized and a Hanuman flag was placed on one of the minarets of the mosque. It was also reported that prayer mats of the mosque were burnt and torn pages from the Quran were strewn outside the mosque.[94] A mob shouting the slogans Jai Śrī Rām (transl. "Hail Lord Rama") and Hindūō̃ kā Hindustān (transl. "India for Hindus") marched around the mosque before setting it on fire and looting adjacent shops and houses. According to local residents, the attackers did not belong to the area.[7] After the first wave of violence by rioters, the police evacuated Muslim residents and took them to the police station. While the residents were away, a second mosque in Ashok Nagar and a third in Brijpuri were also torched along with a three-storey house and eight shops in the vicinity; the rioters could not be identified.[95][96] Another mosque was vandalised in Gokulpuri.[97]

At 3 p.m. in Durgapuri, Hindu and Muslim mobs clashed, pelting stones and shooting at each other. The rioters sported tilaka on their foreheads, and shouted religious slogans whilst shops and vehicles belonging to Muslims were exclusively torched. Police were not present initially in the area and arrived almost an hour later.[98]

At Gamri extension, a Hindu mob attacked a lane, and an 85-year-old woman was burnt to death when her house was set on fire.[99] In Karawal Nagar, acid was thrown by protesters on the paramilitary personnel, who were deployed in the area to maintain law and order.[100] A Muslim man was shot and burnt to death by a mob in Shiv Vihar, with cries of "Jai Shri Ram" being heard.[101] People wielding sticks and iron rods were reported to be roaming streets in the areas of Bhajanpura, Chand Bagh and Karawal Nagar localities.[72]

By 9:30 p.m., it was reported that 13 people died due to violence.[72] Among the injured, more than 70 people suffered gunshot injuries. At 10 p.m., shoot at sight orders were given to police in the riot-affected area.[91]

The dead body of a trainee driver in the Intelligence Bureau at Chanakyapuri, was found in a drain in Jaffrabad, a day after he went missing.[102] The circumstances leading to his death are under investigation,[103][104] with a lot of confusion regarding them.[105][106] According to a post-mortem report, he was repeatedly stabbed, leading to his death.[107] Tahir Hussain, who was an Aam Aadmi Party (AAP) councillor, was arrested for allegedly murdering Sharma.[108][109][110]

7,500 emergency calls were made to the police control room throughout the day, the highest in the week.[69][90]

26 February[edit source | edit]

The National Security Advisor of India, Ajit Doval, visited violence-affected areas of North East Delhi in the evening. However, reports of violence, arson and mob lynching emerged from Karawal Nagar, Maujpur and Bhajanpura later that night.[111]

1,500 emergency calls were made to the police control room that day.[69][90] Complaints of delayed post-mortem reports were heard from several hospitals while witnesses and affected individuals who claimed to be civilians gave statements. Some of them blamed Kapil Mishra for the riots while one individual stated that a mob attacked them with stones and swords while chanting the Takbir.[112]

27 to 29 February[edit source | edit]

Burnt shops at Shiv Vihar.[lower-alpha 10]
27 February

In Shiv Vihar, between 7 a.m. and 9 a.m., clashes were reported. Three injured persons were reported, one of whom had bullet wounds. A godown, two shops, and a motorcycle were torched.[114]

28 February

A 60-year-old rag picker, who had stepped out of home assuming the situation had normalized, was attacked and died on way to the hospital due to head injuries.[115]

29 February

With no fresh cases of violence reported to the police on the day, the situation was said to be returning to normal with some shops reopening.[116] Thirteen cases were registered against people posting provocative content on social media.[117] In the Welcome area, one shop was set on fire.[118]

Attacks on journalists[edit source | edit]

Several incidents of mobs attacking journalists were reported during the riots. A journalist of JK 24x7 News was shot by Anti-CAA protestors on 25 February while reporting in the Maujpur area.[119][120] Two journalists of NDTV along with a cameraman were attacked by the mob while they were recording the torching of a mosque in the area. One of the journalists sustained severe injuries. A journalist involved in the same incident had to intervene and convince the mob that the journalists were Hindus to save them from further assault.[121]

On 25 February, a photojournalist for The Times of India was heckled by the Hindu Sena members while taking pictures of a building that had been set on fire. The group tried to put a "tilak on his forehead" claiming that it will "make his job easier" as he could then be identified as a Hindu by the rioters. They questioned his intentions of taking pictures of the building on fire and further threatened to remove his pants to reveal that he is not circumcised, as evidence of being a Hindu.[119][121][122] The reporter was later approached by another rioter who demanded him to prove his religion.[119]

Several journalists shared their experience with rioters on Twitter. A journalist of Times Now tweeted that she was attacked by pro-CAA and right-wing protesters. She said that she had to plead with the mob, who were carrying stones and sticks, to escape from the site.[119] Journalists of Reuters,[123] India Today,[124] CNN-News18[125] too stated that they were assaulted.[119]

The Hindustan Times reported that a motorcycle, which belonged to one of its photographers who was documenting the violence in Karawal Nagar, was set on fire by a masked mob. After torching the motorcycle, the mob threatened, assaulted him and seized the memory card in his camera. They asked for his official identity card and took a photograph of it before letting him leave.[126]

The Editors Guild of India issued a statement on 25 February expressing concern about the attacks on journalists as an assault on freedom of the press in India. They urged the Home Ministry and the Delhi Police to investigate the incidents and bring the perpetrators to justice.[127][128]

Interfaith solidarity[edit source | edit]

For further information, see Hindu-Muslim unity

ThePrint journalists, who covered the incidents, reported that the people of the localities were confident that their neighbours did not engage in violence against them. Rather they blamed the "outsiders".[129] The neighbourhood between Jaffrabad and Maujpur, which has a mixed population of Hindus and Muslims, demonstrated unity by guarding one another and barricading the gate to prevent outside mobs from entering and destroying the communal harmony that exists there.[130][131] In the area of Mustafabad, Hindus and Muslims joined together to keep guard to prevent miscreants to enter the area.[132]

Some Hindu families worked to protect their Muslim friends and neighbours amidst the riots by inviting them into their homes for a few days until the riots calmed down.[133][134] A local Hindu rescued his Muslim friends from their burning house, suffering 70% burns while doing so.[135] In the area of Chand Bagh, some Muslims visited their Hindu neighbours and assured their safety.[39] At the Mandir Masjid Marg of Noor-e-Ilahi, Muslims gathered around Hanuman Mandir, the Hindu temple, to protect it from being damaged while Hindus did the same for Azizya Masjid, a mosque in the area.[136][137][138] A Sikh father-son duo rescued around seventy Muslims from a mosque and a madrasa that were surrounded by a mob, by transporting them to safety on their motorcycle, giving safe passage to two children at a time.[139] Amidst the rioting, the Sikh community allowed those seeking shelter into the gurudwara.[139]

Both Hindus and Muslims comforted one another and mourned the loss of their kin who were killed by the rioters.[140]

On 1 March, Muslim and Hindu residents of Jaffrabad organised a peace march together.[141] Later that week, Anil Joseph Thomas Couto, the Catholic Christian archbishop of the Roman Catholic Archdiocese of Delhi appealed "for peace and non-violence" and clergy from the Christian, Hindu, Muslim, Sikh and Jain faiths gathered in front of the Sacred Heart Cathedral, New Delhi, to pray in solidarity.[142]

Handling by emergency services[edit source | edit]

Delhi Police[edit source | edit]

The Delhi Police's ability to maintain the law and order and bring the peace back in riot-affected areas has been questioned by multiple sources. The police took no action even though present when the violence resulted in murders. They remained lax in deploying policemen on 23 February, when multiple intelligence reports requested more forces to prevent the tense situation (created by Mishra's speech) from escalating further. Victims of the riot reported that the police did not respond promptly when called, claiming that the officers were busy.[143][144] Other reports also suggested that the police encouraged rioters[145] and physically attacked residents of riot-affected areas, going on to shoot people randomly. The police, however, denied these assertions.[146]

A video shared on social media on 26 February showed a group of men being assaulted by the police as they lay on the ground, forcibly singing the national anthem of India and "Vande Mataram" on the demands of the policemen.[147] The families of the men claimed that they were detained in the lockup for two days and beaten further. One of them, Mohammad Faizan,[148] was admitted in the neurosurgery wing of LNJP Hospital and died on 29 February from critical gunshot wounds. Another was reported to have suffered serious injuries.[149][150]

The lack of the police's prompt response may be attributed to the large police force deployed to line the roads for the visit of the United States President Donald Trump. The police had reportedly informed the Ministry of Home Affairs of the shortfall of policeman available for immediately controlling the violence,[151] but this was denied by the Ministry.[152]

When the Delhi High Court bench, on 27 February, ordered the Delhi Police to file FIRs against the people whose speeches triggered the riots, the police and the government remarked that they had consciously not done so, citing that arresting them would not restore immediate peace. They further informed the court that they would need more time to investigate the matter.[153]

When a team of lawyers visited Jagatpuri police station to visit the anti-CAA protestors detained by the police, they were reportedly abused by police personnel.[154] The lawyers then wrote to the Delhi commissioner of police, demanding action against the officer who assaulted them.[155]

Delhi Health Services[edit source | edit]

The Jan Swasthya Abhiyaan (JSA), a public health advocacy group, compiled a report on the information gathered by their volunteers working in the hospitals during the riots. The report, titled The Role of Health Systems in Responding to Communal Violence in Delhi[156] and released on 2 March, alleged that doctors had harassed the victims by referring to them as terrorists, and had asked victims if they knew the full forms of "NRC" and "CAA". The report documented instances of negligence, denying victims treatment in some cases, while disregarding the safety of patients in others. Multiple cases were reportedly rejected for not having the required medico-legal case documentation. It was also alleged that the doctors did not provide detailed reports of the injuries and autopsies to the victims and their families.[157]

The report indicated that citizens had grown fearful of government services such as ambulances and government hospitals, with victims taking private vehicles to go to private hospitals,[158] due to the treatment and abuse that they had received from the police.[156] This problem compounded the existing issues of the mobs not allowing ambulances near the riot-affected areas.[159] In some areas, primary health centres and hospitals remained closed throughout the riots, either due to the violence or due to lack of medical facilities available at the grassroots level even before the riots began.[160] Families of the victims also reported delayed post-mortem reports from several hospitals.[112]

Response and reactions[edit source | edit]

Response by the government[edit source | edit]

On 24 February 2020, the Ministry of Home Affairs stated that the violence appeared orchestrated to coincide with President Donald Trump's February 24–25, 2020 visit to India.[161] The Ministry also refused to bring in the Army to control the riots and stated that the number of central forces and policemen on the ground was adequate. More than 6,000 police and paramilitary personnel were deployed in the area.[72]

On 25 February the Chief Minister of Delhi, Arvind Kejriwal stated that the Delhi Police, despite its efforts, had been unable to control the violence and requested the Army's assistance in stopping the violence as the number of deaths climbed to 23.[94][162][163]

Home Ministry's meeting[edit source | edit]

On the morning of 25 February 2020, the Chief Minister Kejriwal chaired an urgent meeting of all party MLAs from the violence-hit areas and senior officials. Several MLAs raised concerns on the lack of deployment of enough policemen.[91] The concerns were raised by Kejriwal in the subsequent meeting chaired by Home Minister Shah and attended by Delhi Lieutenant-Governor Anil Baijal and senior police officials. The meeting concluded with the decision to take all possible steps to contain violence. Kejriwal stated that Shah had assured the availability of an adequate number of policemen.[91]

National Security Advisor Ajit Doval was given the responsibility of restoring peace in the region.[162][164] On 26 February, Doval travelled to the violence-hit regions and spoke to locals, assuring them of normalcy.[165]

Relief measures[edit source | edit]

On 27 February, Kejriwal announced free treatment for the injured in government as well as private hospitals under the Farishta scheme. The government had made arrangements with the help of NGOs to supply food in areas where a curfew had been imposed. He also announced a compensation amount of 1 million (US$14,000) to affected people, 100,000 (US$1,400) ex-gratia, and 500,000 (US$7,000) in the case of a death of a minor.[114] He also announced that the Delhi government had set up nine shelters for the people affected by the riots. For people whose houses were completely burnt, immediate assistance of 25,000 (US$350) was announced.[115]

Food and other relief materials were distributed with the help of resident welfare associations and NGOs.[166] BJP leaders Tajinder Bagga and Kapil Mishra collected 7.1 million (US$100,000) for the Hindu victims of Delhi riots via crowdfunding.[167]

Reactions[edit source | edit]

AAP leader Sanjay Singh released a video in which BJP MLA from Laxmi Nagar, Abhay Verma, was seen leading crowds that raised slogans Jō Hindū hit kī bāt karēgā, vahī dēś pē rāj karēgā (transl. "Whoever talks about the welfare of Hindus, only they will rule the country") and Jai Śrī Rām (transl. "Hail Lord Rama"). Singh accused Home Minister Amit Shah of holding an "all-party meeting, pretending to restore peace and their MLA is engaged in inciting riots." Verma meanwhile defended himself claiming the slogans were raised by civilians.[168]

Indian National Congress president Sonia Gandhi held a press conference at which she said that Shah should resign for failing to stop the violence. She asked for the deployment of an adequate number of security forces.[162] Gandhi's press conference was followed by a press conference by Prakash Javadekar; he said that there is "selective silence" from AAP and Congress and he added that they are politicising violence.[169]

After three days of violence with 20 deaths, the Prime Minister of India, Narendra Modi, shared a message on Twitter asking people to maintain peace. Commentators said that he reacted only after the departure of President Trump, whom he had been hosting on a state visit while the riots began.[170][171][172][173]

On 26 February, the US Commission on International Religious Freedom (USCIRF) conveyed "grave concern" over the riots and requested the Indian government to provide protection to people, no matter which faith they belonged to.[174] US Senator and 2020 US presidential candidate Bernie Sanders and other American politicians expressed their concerns over the events. In response, on 27 February 2020, the Ministry of External Affairs spokesperson, Raveesh Kumar, stated that these remarks were "factually inaccurate", "misleading" and "aimed at politicising the issue".[175] BJP general secretary BL Santhosh threatened Sanders with election interference due to his condemnation.[176] The US issued a travel advisory for its citizens to exercise caution.[177]

On 27 February, United Nations High Commissioner for Human Rights, Michelle Bachelet, stated, "Indians in huge numbers, and from all communities, have expressed—in a mostly peaceful manner—their opposition to the Act, and support for the country's long tradition of secularism".[178] She expressed concern on the citizenship law and reports of "police inaction" during the communal attacks in Delhi.[179] Twelve eminent citizens of Bangladesh also expressed grave concern over the communal clashes on that day. They expressed fear that India's failure to handle the situation could create a volatile environment in its neighbouring countries, which could destroy peace, democracy, development and communal harmony in the region.[180] The Governor of Meghalaya, Tathagata Roy, wanted lessons to be learned from Deng Xiaoping's handling of the 1989 Tiananmen Square protests for ways to handle the riots.[181] Also on the same day, Turkish president Erdogan criticised the violence. He said, "India right now has become a country where massacres are widespread. What massacres? Massacres of Muslims. By who? Hindus."[182]

On 2 March, the Chief Minister of West Bengal, Mamata Banerjee, alleged that the Delhi riot was a "planned genocide".[183][184] On 5 March, Supreme Leader of Iran, Ayatollah Ali Khamenei, asked the Indian Government to confront extremist Hindus and their parties and stop the massacre of Muslims of India, to prevent India from being isolated from the world of Islam.[185]

Investigation[edit source | edit]

On 27 February 2020, the Delhi Police reported that two Special Investigation Teams (SIT) had been formed to investigate the violence.[186][187] DCP Joy Tirkey and DCP Rajesh Deo were appointed head of these SITs respectively, along with four Assistant Commissioners in each team.[188] Additional Commissioner of crime branch, B.K. Singh, was announced to be supervising the work of the SITs. On 28 February 2020, the police also called in forensic science teams, who visited the crime scenes to collect evidence.[189]

As of 7 March 2020, police had registered 690 FIRs and around 2200 individuals involved in the violence were taken into custody.[11] Some activists were charged with offences under the Indian Penal code and the Arms Act. Their friends and relatives alleged that they were tortured in custody.[190][191][192][193] During a parliamentary debate over the riots on 11 March, Home Minister Amit Shah stated that rioters who had come from Uttar Pradesh had been identified.[194]

Supreme Court hearing[edit source | edit]

Bhim Army chief Chandrashekhar Azad Ravan, along with former Chief Information Commissioner Wajahat Habibullah and social activist Syed Bahadur Abbas Naqvi, filed an appeal in the Supreme Court requesting that the police be directed to file reports over cases of violence that had occurred since the night of 23 February. The petition also accused Mishra of "inciting and orchestrating the riots".[195] During the hearing held on 26 February, the Supreme Court criticized the Delhi Police for not having done enough to stop the violence. However, the bench, consisting of Justices Sanjay Kishan Kaul and K. M. Joseph, did not entertain the plea, stating that the case was already in the Delhi High Court.[196][197]

High Court hearing[edit source | edit]

Activists Harsh Mander and Farah Naqvi filed a plea in the Delhi High Court, demanding that the police report and arrest those involved in the violence on 25 February. The plea further demanded that a Special Investigation Team (SIT) be set up to investigate the incident and that compensation be provided to those killed and injured. It also requested for the immediate deployment of the Indian Army in the affected areas.[91]

Court hearing on 26 February[edit source | edit]

At midnight on 26 February, the court bench, consisting of Justices S. Muralidhar and Talwant Singh, heard the emergency plea,[198][199] following which, the court ordered the police to safeguard and help all victims to reach their nearest hospitals.[200][201][202]

In the hearing during the morning, DCP of crime branch, Rajesh Deo, and the Solicitor General of India, Tushar Mehta, surprised the court by admitting that they had not watched the video of the inflammatory speech given by Kapil Mishra. However, Deo admitted to have watched the videos of Anurag Thakur and Parvesh Verma.[203][204] The Court then played the video clip of Kapil Mishra's speech.[205] The bench expressed "anguish" over the inability of the Delhi Police to control the riots and its failure to file FIRs against four BJP leaders, Kapil Mishra, Anurag Thakur, Parvesh Verma and Abhay Verma[3] for their hate speeches. The bench also noted that incidents like the 1984 anti-Sikh riots must be prevented from ever occurring again in Delhi.[206]

Transfer of Justice Muralidhar[edit source | edit]

Late on the night of 26 February, Justice S. Muralidhar, who had presided over the plea hearing, was transferred to the Punjab and Haryana High Court. This was the same day on which he had condemned the Delhi Police for its failure in controlling the riots or filing cases against BJP leaders for hate speech.[207][208] However, the Law Minister Ravi Shankar Prasad stated that this was a routine transfer[207] which had been recommended by the Supreme Court a fortnight before.[209] BBC News reported that Muralidhar's "biting comments could have hastened his transfer". The news of his removal from the case was criticised by many Indians who expressed concern.[208] The Congress party called his transfer a move to protect the accused BJP leaders.[210] The Delhi High Court Bar Association criticised the transfer and asked the Supreme Court collegium to revoke it.[211]

Court hearing under new bench[edit source | edit]

On 27 February, the court resumed the hearing with a new bench consisting of Chief Justice D.N. Patel and Justice C. Hari Shankar. During the previous hearing, the Delhi police were given 24 hours to decide on the filing of FIRs over hate speeches by four BJP leaders. The government's lawyer claimed that the situation was not "conducive" and that the government needed more time before it could take appropriate action. The new bench accepted the same arguments that the previous bench had rejected and agreed to give the government more time to decide on filing of the cases for hate speech.[212] The petitioners' lawyer requested an earlier hearing, citing the increasing number of deaths, but the court set 13 April as the date of the next hearing.[213]

On 28 February, the court issued notices to the local and central governments seeking their responses on registering FIRs on Congress party leaders Sonia Gandhi, Rahul Gandhi, and Priyanka Gandhi on the charges of delivering hate speeches.[214][215] Hearing another plea, the bench also issued notice to the Delhi police and the central government for their response on registering FIR on AAP MLA Amanatullah Khan, actress Swara Bhaskar, activist Harsh Mander and on AIMIM leaders like Akbaruddin Owaisi, Asaduddin Owaisi, and Waris Pathan. The court later posted the matter to be heard again on 13 April.[216][217]

Aftermath[edit source | edit]

In the aftermath of the riots, many Muslims who had been living in the riot-affected neighbourhoods left with all their belongings.[13] Even in areas of Delhi which were not affected by the violence, many Muslim families packed up their belongings and left for their ancestral villages, showing no intention of ever coming back.[22] According to complaints received by lawyers representing Muslim victims of the riots, the police had threatened to falsely implicate the victims in police cases if they filed any complaints against the rioters.[218]

For those left homeless or who had run away from their homes out of fear, temporary relief camps were set up in houses, temples,[219] madrasas and the Al-Hind Hospital.[220] Camps housing larger numbers were erected in areas like Idgah, the Mustafabad prayer ground.[221] The Idgah camp was the largest among nine others and was funded by the government. However, it soon grew crowded. Volunteers helped victims by distributing carts to vendors and providing others with legal aid or even simple help in filling forms. Doctors volunteered to provide medical attention to people suffering from injuries. Most of the refugees were reported to suffer from skin rashes and the common cold.[222] Many others, including the children, were reported to be suffering from anxiety and mental trauma. They reported to have lost their homes and their livelihoods and were awaiting government help to rebuild their lives.[223][224] In another camp in Khajuri Khas, a team of paralegals ran a relief assistance booth of the government. These victims then faced the threat of coronavirus, with social distancing being impossible given the number of people crowded in these camps.[225] Following this, the Delhi government forcefully evicted the residents of the Idgah camp by 30 March, leaving many homeless. The victims were promised rations and a sum of 3,000 (US$42) to rent rooms for themselves, but not all were able to avail of these relief measures.[226]

Archbishop Couto of Delhi stated that churches were using their resources to help those affected by the 2020 Delhi riots; the Holy Family Hospital, for example, engaged physicians, nurses, as well as ambulances to provide relief to affected people. He further stated that Catholic churches would accept those affected by the riots, especially with it being the season of Lent.[142]

Hindus and businesses run by them in the riot-affected areas began boycotting traders and refused to hire workers who were Muslims. They alleged that the Muslims had started the riots and had then blamed the Hindus for the violence. As a result of the growing distrust between the two communities in these areas, the Hindus and Muslims would avoid each other during the day and block the lanes to their respective neighbourhoods with barriers at night. Neighbourhoods of both communities put up metal gates to slow down the passage of rioters in the future, with some keeping themselves permanently armed with wooden lathis (batons).[47]

Hindu politicians paraded injured victims with bandages wrapped around their heads in multiple "peace marches", alleging that they were victims of violence at the hands of Muslims. This incited more hatred towards Muslims.[43] One such rally held on 29 February was organised by the Delhi Peace Forum, an NGO backed by the Rashtriya Swayamsevak Sangh, with people holding placards that said, "Delhi against jihadi violence". Kapil Mishra was seen at the rally,[227] while inflammatory slogans inciting people to "shoot the traitors" were heard.[228][229] Gangs of Hindus later appeared in multiple neighbourhoods and threatened the Muslims living there to abandon their homes before the Hindu festival of Holi, which was celebrated on 9 March 2020.[45]

Malayalam news channels Asianet News and MediaOne TV were banned by the Ministry of Information and Broadcasting for 48 hours on 6 March[230] for broadcasting about the Delhi riots and the lack of action taken by the police. However, the ban was soon reversed by I&B Minister Prakash Javadekar, following multiple complaints.[231]

During a parliamentary debate over the riots on 11 March, Home Minister Amit Shah gave his condolences to the families of those who died due to the violence and assured them of justice. He went on to commend the Delhi Police for their efforts and blamed Muslim leaders and members of the Congress party for instigating the riots. Another BJP MP, Meenakshi Lekhi, accused ISIS elements of having organised the riots. Members of the opposition like Kapil Sibal, Adhir Ranjan Chowdhury and Asaduddin Owaisi criticised the government for its lack of timely action.[194][232]

In response to an RTI application on 13 April, the Delhi Police stated that 23 people had died and 48 people had been arrested in connection with the riots. This was in stark contrast to the report of 52 deaths and 3,304 arrests submitted by Junior Home Minister G. Kishan Reddy on 18 March, who had obtained the figures from the Delhi Police.[233]

See also[edit source | edit]

Footnotes[edit source | edit]

  1. The following reference to a published source that includes a similar photo supports description in caption and provides additional context. This is not the photo published by that source.[1]
  2. The Government of Delhi is different from the Government of India.
  3. The following reference to a published source supports description in caption and provides additional context. This photo was not published by that source.[2]
  4. At a rally in Delhi, a Union Cabinet minister shouted Desh ke ġaddāroṉ ko ("What's to be done with the traitors to the nation?") and the crowd screamed back, Goli māro sāloṉ ko ("Shoot the bastards!").[55]
  5. Previously, on 17 December 2019, violence occurred during the CAA-protests in the Seelampur area, in North East Delhi. On 3 January 2020, DCP Surya told media that adequate security personnel and proper security arrangements were in place in the Seelampur area and no further gatherings and violence were expected.[61]
  6. The following reference to a published source that includes a similar photo is offered solely for context. This is not the photo published by that source.[17]
  7. The following reference to a published source that includes a similar photo is offered solely for context. This is not the photo published by that source.[70]
  8. Initial reports said that Ratan Lal had died of a head injury after being hit by a stone. However, the autopsy report said that a bullet was found in his body.[77]
  9. The following reference to a published source is offered solely for context. This photo was not published by that source.[92]
  10. The following reference to a published source that includes the same photo is offered solely for context.[113]

References[edit source | edit]

  1. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  2. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  3. 3.0 3.1 3.2 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  4. 4.0 4.1 4.2 4.3 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  5. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  6. 6.0 6.1 6.2 6.3 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  7. 7.0 7.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  8. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  9. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  10. 10.0 10.1 10.2 10.3 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  11. 11.0 11.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  12. 12.0 12.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  13. 13.0 13.1 13.2 13.3 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  14. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  15. 15.0 15.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  16. 16.0 16.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  17. 17.0 17.1 17.2 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  18. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  19. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  20. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  21. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  22. 22.0 22.1 22.2 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  23. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  24. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  25. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  26. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  27. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  28. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  29. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  30. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  31. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  32. 32.0 32.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  33. 33.0 33.1 33.2 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  34. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  35. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  36. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  37. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  38. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  39. 39.0 39.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  40. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  41. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  42. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  43. 43.0 43.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  44. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  45. 45.0 45.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  46. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  47. 47.0 47.1 47.2 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  48. 48.0 48.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  49. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  50. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  51. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  52. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  53. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  54. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  55. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  56. 56.0 56.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  57. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  58. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  59. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  60. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  61. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  62. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  63. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  64. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  65. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  66. 66.0 66.1 66.2 66.3 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  67. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  68. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  69. 69.0 69.1 69.2 69.3 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  70. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  71. 71.0 71.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  72. 72.0 72.1 72.2 72.3 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  73. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  74. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  75. 75.0 75.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  76. 76.0 76.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  77. 77.0 77.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  78. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  79. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  80. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  81. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  82. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  83. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  84. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  85. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  86. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  87. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  88. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  89. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  90. 90.0 90.1 90.2 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  91. 91.0 91.1 91.2 91.3 91.4 91.5 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  92. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  93. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  94. 94.0 94.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  95. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  96. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  97. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  98. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  99. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  100. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  101. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  102. Sources for trainee driver.
    • Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
    • Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
    • Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
    • Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  103. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  104. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  105. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  106. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  107. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  108. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  109. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  110. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  111. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  112. 112.0 112.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  113. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  114. 114.0 114.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  115. 115.0 115.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  116. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  117. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  118. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  119. 119.0 119.1 119.2 119.3 119.4 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  120. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  121. 121.0 121.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  122. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  123. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  124. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  125. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  126. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  127. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  128. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  129. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  130. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  131. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  132. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  133. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  134. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  135. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  136. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  137. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  138. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  139. 139.0 139.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  140. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  141. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  142. 142.0 142.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  143. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  144. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  145. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  146. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  147. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  148. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  149. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  150. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  151. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  152. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  153. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  154. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  155. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  156. 156.0 156.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  157. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  158. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  159. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  160. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  161. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  162. 162.0 162.1 162.2 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  163. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  164. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  165. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  166. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  167. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  168. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  169. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  170. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  171. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  172. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  173. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  174. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  175. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  176. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  177. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  178. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  179. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  180. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  181. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  182. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  183. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  184. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  185. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  186. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  187. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  188. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  189. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  190. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  191. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  192. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  193. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  194. 194.0 194.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  195. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  196. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  197. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  198. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  199. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  200. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  201. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  202. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  203. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  204. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  205. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  206. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  207. 207.0 207.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  208. 208.0 208.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  209. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  210. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  211. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  212. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  213. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  214. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  215. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  216. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  217. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  218. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  219. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  220. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  221. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  222. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  223. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  224. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  225. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  226. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  227. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  228. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  229. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  230. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  231. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  232. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  233. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).

Bibliography[edit source | edit]

  • Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  • Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  • Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).

Template:Citizenship Amendment Act protests Template:Riots in India Template:Religious persecution