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

2019 Bolivian political crisis

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

2019 Bolivian political crisis
Jeanine Áñez assuming presidency.jpg
Conferencia de Prensa de Evo Morales en el Museo de la Ciudad de México 3.jpg
Jeanine Áñez assuming the presidency (left), Evo Morales speaking in Mexico, where he received political asylum after his resignation (right)
Date10 November 2019
Location
La Paz, Bolivia
MethodsBarricades, demonstrations, hunger strike
Resulted inTemplate:Bulletlist
Parties to the civil conflict
Lead figures
Template:Bulletlist Template:Bulletlist
Casualties
Death: 33 (26 November 2019)[1]
Injured: 715 (17 November 2019)

On 10 November 2019, after 19 days of civil protests following the disputed election results of October 2019 and the release of a report from the Organization of American States (OAS), which alleged irregularities in the electoral process, trade unions, the military and the police of Bolivia suggested that president Evo Morales resign. After General Williams Kaliman Romero made the military's request for Morales's resignation public, Morales complied, accompanied by other resignations by high-level politicians throughout the day, some citing fears for the safety of their families. The government of Mexico offered political asylum to Morales the following day, which Morales accepted a day afterwards.[2][3]

The second vice president of the Senate, opposition senator Jeanine Áñez, assumed the role of president on 12 November, being the next in line for the presidency after a vacuum had been left following a string of resignations. This was not without controversy, as her initial appointment was made during a brief legislative session that lacked quorum, due to a boycott by Morales's party, Movement for Socialism (MAS).[4] Bolivia's Plurinational Constitutional Tribunal then confirmed Áñez's assumption of the presidency as legitimate and the ruling party returned most members to both chambers, with some assuming key positions such as Leader of the Senate.[5][6][7] They have also committed to working with the interim government towards new elections.[8]

Despite the return of his party to the role of government, Morales has called for the Bolivian people to reject the leadership of Áñez. He and his supporters argue that the event was a coup d'état. International politicians, scholars and journalists are divided between describing the event as a coup or popular uprising.[9][10][11][12][13][14][15][16] The Bolivian Congress, with the majority being members of Morales' MAS party, unanimously approved a bill on 23 November 2019 that annulled the results of 20 October election, allowed for new elections and prevented Evo Morales from participating in the new elections.[17][18][19] The bill was signed into law the next day by president Áñez.[20]

On 4 December 2019, the OAS released its final report related to 20 October election, detailing what they called "deliberate" and "malicious" tactics to rig that election in favor of President Evo Morales.[21][22] Two subsequent independent non-peer-reviewed analyses of election data from different sources disagreed with the statistical analysis of election data presented by the OAS. OAS's counter-response stated that doing statistical exercises on falsified data does not prove the data is not false, and pointed out that the counter-analyses do not address or discount other evidence of fraud in the report.[23][24]

Background[edit source | edit]

2019 Bolivian general election and subsequent investigations[edit source | edit]

On 20 October 2019, the first round of voting for all government positions was held. After the polls closed, the Supreme Electoral Tribunal began to release the preliminary results of the presidential election; at 7:40 pm, when 83.8% of the votes had been counted, the preliminary count stopped. The Tribunal's president, María Eugenia Choque, said that the preliminary count had stopped because the official results had begun to be released. At the time that the preliminary count was stopped, Morales led with 45.3%, and his primary opponent, Carlos Mesa, had 38.2%. Less than a 10-point lead would have resulted in another round of runoff voting.[25] At 9:25 pm, President Morales declared himself the winner, stating that rural areas would guarantee his victory.[26][27]

Although uncounted votes in rural areas were expected to go his way, one body observing the election—the Organization of American States (OAS)—stated that even if Morales did win outright, his lead beyond the 10-point threshold would be so negligible as to warrant a runoff anyway. The OAS expressed concern about the day-long gap in results reporting: after 24 hours, the updates resumed, but with a surge for Morales at the first update.[28]

On 21 October, the Plurinational Electoral Organ reported a still-incomplete count,[29] suggesting that with only 95.3% of verified votes, Morales had too large of a margin above 10 points to overcome, avoiding a second run-off round, and so Morales would remain in power for a fourth term.[30][31] Based on this result, along with reported irregularities and the two-term presidential limit that the Bolivian Constitutional Tribunal had nullified, the Bolivian opposition and protestors as well as some foreign governments and international observers called for an audit of the process and results, to which Morales agreed.[32] The OAS audit of the election began on 31 October and was observed by Spain, Mexico, and Paraguay.[33]

Protests[edit source | edit]

By 24 October, Morales began describing the actions taken against him as a coup.[34] On 25 October, when the results were officially announced with Morales as the winner, various countries in Latin America, as well as the United States and European Union, had called for the second round to go ahead regardless.[35]

On 31 October, two deaths were announced by the government.[36]

The third death during the protests occurred on 7 November when a 20-year-old student called Limbert Guzman was killed during clashes.[37]

Events[edit source | edit]

Allegations of electoral fraud and OAS audit[edit source | edit]

On 6 November, the Bolivian opposition published a 190-page long report containing fraud accusations, including irregularities such as mistaken electoral acts additions, data swiping and electoral acts where the ruling party obtained more votes than registered voters, expecting to send it to international organizations such as the OAS and the United Nations.[38]

Although a complete report was not yet due, mounting tension in the country prompted the OAS to release a preliminary report on 10 November concluding that they had discovered sufficient evidence of election fraud to warrant new elections.[39][40] This led to a string of events culminating in the resignation of Morales. The OAS uncovered multiple irregularities, including failures in the chain of custody for ballots, alteration and forgery of electoral material, redirection of data to unauthorized servers and data manipulation.[41] They added that it was statistically unlikely that Morales had secured the 10-percentage-point margin of victory needed to win outright, saying that election should be annulled after it had found "clear manipulations" of the voting system, and that "The manipulations to the computer systems are of such magnitude that they must be deeply investigated by the Bolivian State to get to the bottom of and assign responsibility in this serious case."[9][42]

An analysis by the Center for Economic and Policy Research (CEPR) disputed the OAS's preliminary findings and criticized what it called a "politicization of the electoral observation process."[43] The co-director of the think-tank, Mark Weisbrot, stated the OAS showed "no evidence – no statistics, numbers, or facts of any kind" to support its claim of electoral manipulation.[44] CEPR concluded that due to Morales' voter base being in more rural regions, the results from peripheral areas received towards the end of the count were more likely to be in his favour.[45] The New York Times noted, however, that this criticism has "not addressed the accusations of hidden data servers, forged signatures and other irregularities found by the O.A.S. observers, nor have they tried to explain the electoral council’s sudden decision to stop the count".[46] The OAS also dismissed the report as "neither honest, nor fact-based nor comprehensive".[47]

On 5 December, the full 95-page OAS report[48][49] was released along with 500 pages of corroborating details as appendices. These included that an outside user who controlled a Linux AMI appliance with "root privileges" — conferring the ability to alter results — accessed the official vote-counting server during the counting and that in a sample of 4,692 returns from polling stations around the country, 226 showed multiple signatures by the same person for different voting booths, a violation of electoral law. On those returns, 91 percent of votes went to MAS, approximately double the rate recorded elsewhere.[50] However, this statistic reflects sampling bias, as the only tally sheets selected for study were those in which the MAS received 90% or more of the vote as well as those in which the MAS received at least 77% of the vote and which only appeared in the official count.[51]

On 21 December, the Technical Mission of Electoral Experts sent by the European Union published a 67-page report that made similar observations and conclusions to those of the OAS. They noted that "there were minutes with an unusually high number of null votes, blank votes and a hundred percent participation of voters in a series of polling stations" and highlighted the general failure of the TSE to declare these irregularities.[52][53]

On 3 January 2020, at a meeting of the Committee for Latin America of Socialist International, it was declared that they accepted the findings of the OAS and that Morales was not a victim of a coup. A document containing discussions of the Bolivian political crisis states that "“After a broad mobilization of citizens in that country in protest of electoral fraud that was informed and verified by an audit conducted by the Organization of American States (OAS) of the elections that took place on 20 October, the president Evo Morales did not suffer a coup d'etat.” [54]

Independent contract researchers for CEPR, John Curiel and Jack R. Williams refuted the claims of voter fraud made by OAS with a statistical analysis released on 27 February 2020. They contended that the OAS allegations were made on two unproven premises: "...the unofficial count accurately reflects the vote continuously measured, and that reported voter preferences do not vary by the time of day". The researchers asked OAS for comment before publishing, but OAS did not respond. Curiel and Williams concluded, "There is not any statistical evidence of fraud that we can find — the trends in the preliminary count, the lack of any big jump in support for Morales after the halt, and the size of Morales’s margin all appear legitimate. All in all, the OAS’s statistical analysis and conclusions would appear deeply flawed."[55] Subsequent analysis by researchers at the University of Pennsylvania found that there was no evidence of statistical fraud on the part of Morales. Neither study addressed any other claims of fraud, only the OAS's statistical analysis. Following this, the New York Times later admitted in June 2020 that the OAS audit—and the stated reasoning behind Morales' ouster—was wrong: "A close look at Bolivian election data suggests an initial analysis by the OAS that raised questions of vote-rigging — and helped force out a president — was flawed."[56]

Authorities abandon Morales[edit source | edit]

After weeks of repelling protesters at the Casa Grande del Pueblo presidential palace, units of the Police Operations Tactical Unit (UTOP) tasked with defending Morales assembled a meeting on 8 November.[57] UTOP officers ultimately decided at the gathering to abandon their posts and to call for the resignation of Morales.[57] According to Reuters, UTOP turned away from Morales for multiple reasons: complaints of alleged orders to suppress opposition protestors while avoiding Morales loyalists; resentments over perceived preferential treatment given to the military; and the exhaustion of combating protestors.[57]

On 9 November, Morales organized a meeting and ordered the military to put down protesters, with officers present rejecting Morales' orders according to former general Fernando Sánchez.[19] According to The Wall Street Journal, following this meeting, officers feared of "violent military suppression" similar to 2003 protests during the Bolivian gas conflict, which happened before Morales become president.[19] At this time, all UTOP officers had left their positions, leaving Morales vulnerable to protesters.[57] At a police station near the presidential palace, officers climbed onto the roofs and chanted "The Police with the People".[58] Police nationwide began to retreat from protesters, returning to their stations, while other departments began to mutiny against the Morales government, arguing that they did not want to be an "instrument of any government". Head of the Bolivian Armed Forces, General Williams Kaliman, refused to suppress demonstrations, saying that the military would "never confront the people among whom we live" and that the events unfolding were "a political problem and it should be resolved within that realm".[58]

After police left their posts at the presidential palace, Morales never returned and was forced into hiding in an improvised office protected by a small group of his guard.[19] He ultimately held a press conference at the Bolivian Air Force's presidential hangar in El Alto International Airport later in the day, leading some to suspect that Morales had already lost control of the government.[59] Franklin Pareja, a professor of the Higher University of San Andrés, said that because of the abandonment police, the Morales government "lost its shield" and that "it was totally vulnerable and couldn’t go on".[57]

According to members of the Bolivian military quoted by the Wall Street Journal, authorities had questioned Morales' actions for some time.[19] Morales had performed multiple actions that had offended officers within the armed forces, including glorifying Che Guevara after his guerrillas killed 59 Bolivian troops during their insurgency in the 1960s and forcing officers to attend the Anti-Imperialist Military Academy that was led by a convicted former rebel.[19] General Tomás Peña y Lillo, who was chief of the Bolivian armed forces until 2010, stated that officers within the military were traditionally conservative and had refused plans proposed by Morales to be guided by Cuban military and intelligence agents, damaging Morales' hold of the military.[19] Roberto Ponce, former chief of staff of the Bolivian military, also explained that Morales spent little on the country's armed forces as he feared that he would be overthrown, which frustrated military officers.[19]

Protesters overrun La Paz[edit source | edit]

By the night of 9 November, violence escalated throughout Bolivia.[60] The Morales government called on supporters to gather in the capital city of La Paz "defend" him, with reports of pro-Morales groups attacking buses of opposition protesters.[60] However, anti-Morales protesters had already overrun the streets of La Paz, with some groups of police joining in protests against Morales.[60] Demonstrators began to overrun government offices, with protesters flooding the stations of Bolivia TV and Radio Patria Nueva, accusing them of serving Morales.[60] Relatives of Morales had their homes attacked by protesters, with his older sister's home in Oruro being burned while other regional governors had their homes torched as well.[60] The next day, two miners from Potosí were shot and injured, reportedly by snipers, when cooperative miners where marching to join protests in La Paz.[61]

Calls for Morales to resign[edit source | edit]

After the release of 10 November OAS audit, multiple Bolivian entities called on Morales to resign. Morales had initially relied on support from civil organizations to protect him from protests instead of the military since he enjoyed popular support.[19] However, the two main civil groups of Bolivia had begun aligning themselves with the opposition to Morales; the Bolivian Workers' Center (COB), Bolivia's largest trade union and a traditionally pro-Morales entity, and the Single Trade Union Confederation of Workers (CSUTCB), an indigenous workers union.[62][63][64]

CSUTCB had already met with opposition leader Luis Fernando Camacho, announcing an alliance[63] and in the morning of 10 November, the leader of COB suggested Morales resign if it would help solve the violence, and called for new elections.[63] Indigenous and Aymara leader Nelson Condori, the director of CSUTCB, intensified his condemnation of Morales later in the day while at an event beside Camacho, stating, "Evo, we have cried, you have made our lives bitter, you have lied to us. ... When have you forgotten the slogan of our ancestors, do not steal, do not lie, do not be lazy?"[65] Condori also called for a "purge" of the Bolivian government, demanding that Morales and his governmental allies be jailed for electoral fraud.[65]

After the COB and other civil groups formerly supportive of Morales called on him to resign, Morales held a second press conference at the presidential hangar, changing his position on the October election results and announced that new elections would be held.[66][67] Morales released a statement, saying "As President, my main mission is to preserve peace, social justice and economic stability. Listening to the Bolivian Workers' Center (COB), the Pact of Unity and other social sectors, I have decided first to renew all the members of the Supreme Electoral Tribunal".[67]

Since popular social groups had abandoned Morales, the military was the only group protecting him from protesters.[19] Officers who feared punishment if they deployed troops against civilians pressured General Williams Kaliman, the commander-in-chief of the Armed Forces of Bolivia and Morales loyalist, to turn away from Morales.[19] Later, Kaliman announced that the military had suggested[68][69] Morales resign to "help restore peace and stability" after weeks of protests over the vote, adding that the military was calling on the Bolivian people to refrain from violence and disorder.[42] The military also said it would conduct operations to "neutralise" any armed groups that attacked the protesters.[9][70] The military press release invoked[71] Article 20, paragraph b, of Law No. 1405[72] which states:

Article 20. The attribution and responsibilities of the military high command are: [...] b. To analyze inner and foreign troubled situations to suggest to whom it may concern the appropriate solutions.

Morales resigns[edit source | edit]

After Kaliman's statement, Morales took the presidential plane from El Alto International Airport to an undisclosed location, announcing his immediate resignation on television, stating that he was resigning to "protect the families" of Movement for Socialism members.[73] He concluded by stating that he believed Carlos Mesa had "achieved his objective", and asked protesters to "stop burning down the houses of [his] brothers and sisters".[74][75][76] Vice President Álvaro García Linera also resigned after consulting with Morales.[9]

Shortly thereafter, it was reported that Morales was on a plane to Argentina;[77] however, the Argentine foreign minister, Jorge Faurie, said that Argentina would not grant him asylum.[78] Commander Yuri Calderón assured that there was no warrant for Morales' arrest, though armed individuals had entered his home.[79]

Later in the day, Adriana Salvatierra, the President of the Senate, Victor Borda, the leader of the Chamber, and Rubén Medinaceli, First Vice President of the Senate, also all resigned.[80] Mexico's foreign minister declared that twenty members of Bolivia's executive and legislative branches were at the official Mexican residence in the capital seeking asylum following the resignation.[81] Following the resignation of Morales and his allied successors, protesters called for a board to be convened to oversee the government and new elections, though Mesa disagreed with the proposal, stating protesters should not "violate the Constitution so as not to give Evo Morales an excuse that he was the victim of a coup d'etat" and that the Legislative Assembly should determine the constitutional successor.[82]

Later on 10 November, BBC Mundo published an article suggesting that five main reasons combined to force Morales to resign: the audit results, the opposition from the military and police, the ongoing protests, the growing radicalization of the political opposition, and the public distaste towards his continued re-elections.[83]

OEP detentions and TSE arrests[edit source | edit]

At 8:20 pm, the Associated Press reported that Bolivian police had detained 38 members of the Plurinational Electoral Organ (or Órgano Electoral Plurinacional (OEP)) on suspicion of falsification and other electoral crimes, including the former president and vice president of the Supreme Electoral Tribunal (TSE), Maria Eugenia Choque and Antonio Costas. According to police commander Yuri Calderón, Choque was apprehended whilst disguised as a man. The attorney general's office earlier announced that it was opening an investigation into allegations raised by the OAS report.[79] An election official in Santa Cruz, Sandra Kettels, was arrested Monday morning, with arrest warrants issued for the remaining TSE officials.[84]

Succession of presidency[edit source | edit]

Assumption of presidency by Jeanine Áñez[edit source | edit]

Jeanine Áñez, pictured here in 2016, was the next in the line of succession and became interim president

On the evening of 10 November, Jeanine Áñez, the second vice president of the Senate and the highest-ranking official remaining in the line of succession after the resignations, announced she would be assuming the presidency on an interim basis from 11 November onward, with the responsibility of calling new elections. She stated that she would assume the office once the Senate had formally recognized the previous day's resignations. Upon inauguration, Áñez would officially become the President of Bolivia.[85][86]

The Bolivian Constitution does not make specific provisions for the process of a Senator assuming the presidency; article 169 says that "In case of impediment or definitive absence of the president of the State, he will be replaced in office by the Vice President and, in his absence, by the President of the Senate, and in the absence of this by the President of the Chamber of Deputies. In the latter case, new elections will be called within a maximum period of ninety days." It also establishes the line of succession.[87]

The following day, Áñez arrived at La Paz-El Alto airport and was taken in a military helicopter to a nearby Air Force base; from here she traveled in convoy to the Senate.[88]

On 12 November 2019, in a brief legislative session without quorum, due to the ruling party's boycott,[4] Áñez declared herself as acting president of Bolivia while holding a large bible, stating that "the bible has returned to the government palace".[89] Áñez obtained the favourable vote of the opposition parties, a third part of the parliament, while the Movement for Socialism ruling party did not participate in the voting, rejecting the succession.[4]

Áñez's assumption of the presidential office was supported by Bolivia's Plurinational Constitutional Tribunal, which interpreted citing articles referring to the presidential succession of the 2001 Constitutional Declaration, that the next person in the succession line assumes the presidency ipso facto despite not having the required quorum, stating that "the functioning of the executive should not be suspended".[90][5][6][91]

Reactions and anti-Áñez protests[edit source | edit]

A demonstration in support of Morales in El Alto on 11 November 2019

Reactions to the transfer of power and to Ms Áñez's assumption of the presidency have been mixed, being met with both celebrations and protests.[92] Demonstrators celebrating the removal of the government chanted "yes we can" and set off fireworks.[93] Hundreds of supporters of Morales made their way toward the center of La Paz from the mountains surrounding the city, some of them armed with sticks, chanting "here we go, civil war".[94]

The police said the armed group had vandalized police offices, causing panic in some neighborhoods where people blocked their doors with furniture to protect stores and houses. After receiving requests for help from the national police and politicians, the armed forces announced that night they would mobilize to defend gas, water and electricity services around the capital, and also begin joint patrols with the police around the city.[94]

On 13 November, a dozen MAS senators were blocked by police from entering the National Assembly building during the session.[95][96][97]

The next few days were marked by protests and roadblocks on behalf of Morales' supporters. In Cochabamba, Sacaba and Senkata, civilians were killed during clashes with security forces.[98][99][100]

On 20 November, Evo Morales offered not to run for reelection if he was allowed to return to Bolivia and finish his presidential term.[101]

Capital shut down[edit source | edit]

The drinking water supplies to parts of both La Paz and El Alto, the second and third largest cities in Bolivia, were cut off.[102] According to Gen. Williams Kaliman, it was the plan of insurgents to leave these cities without water or fuel and counteractions to guard public services were covered under the so-called "Sebastián Pagador" plan.[103][104]

La Paz's legislature closed down the capital's infrastructure, schools, and workplaces, for public safety.[84] Supporters of Morales also built barricades on roads that lead to the airport.[84]

Barricades were placed around the Senkata refinery in El Alto by Morales supporters, cutting power and fuel to El Alto and La Paz. Pro-Morales demonstrators stormed the premises and set fire to vehicles within the compound.[105] The Bolivian military re-took the site on 19 November using armored vehicles and helicopters,[106] killing three protesters and injuring 22 in the process.[107]

As a result of blockades from various protests surrounding the city, some goods were also not able to enter.[106] Food supply was affected, leading to rationing and controlled prices in El Alto and La Paz.[108]

Interim government response to protests[edit source | edit]

In the face of protests against the interim government, Áñez called for police to restore order and, on 14 November, issued a decree that would exempt the military from any type of criminal responsibility when maintaining order, when acting in a "legitimate defense or state of necessity."[109][110][111][112] On 15 November, security forces fired upon coca farmers protesting against the government in Cochabamba. The clash left nine dead and dozens injured.[111]

Human rights concerns[edit source | edit]

José Miguel Vivanco, head of Human Rights Watch in the Americas, said that the decree "sends a very dangerous message to the military that they have carte blanche to commit abuses".[113] The Inter-American Commission on Human Rights (IACHR) condemned Áñez's government for issuing the decree.[114]

UN Human Rights Chief Michelle Bachelet issued a statement, saying that "while earlier deaths mostly resulted from clashes between rival protestors", the latest incidents appear to be due to the "disproportionate use of force by the army and police", stating that "in a situation like this, repressive actions by the authorities will simply stoke that anger even further and are likely to jeopardise any possible avenue for dialogue." Bachelet also expressed concern that "widespread arrests and detentions" were adding to the tensions; according to her office, more than 600 people had been detained since 21 October. Furthermore, Bachelet also declared being concerned that the situation could "spin out of control if the authorities do not handle it sensitively and in accordance with international norms and standards governing the use of force, and with full respect for human rights", stating that it couldn't be solved through "force and repression".[115] The decree was later repealed by Áñez.[116]

The Inter-American Commission on Human Rights has expressed concerns over human rights violations that occurred after the 2019 Bolivian general election.[117][115][113][1] Paulo Abrão, who heads the IACHR, declared that due to the "massive" number of human rights violations amid post-election violence, the country may need outside help to investigate the situation and recommended Bolivia coordinate with an international panel of experts to ensure findings are seen as credible.[1] On 5 December 2019, Áñez approved an act to provide compensation to the families of those killed and injured during the conflict.[118] On 10 December, the government and IACHR signed an agreement to investigate the acts of violence that occurred.[119] On 30 Dec, Eva Copa, MAS head of the Senate, stated that a report had been filed with Arturo Murillo to give an account of the deaths in Sacaba and Senkata after the Assembly recess in the new year.[120]

Interim government activities[edit source | edit]

New elections[edit source | edit]

Áñez stated on 15 November that in order to restore faith in the electoral process, a vote would first be held to elect a new Electoral Commission, before having a new vote for president.[121]

On 20 November the interim government presented a bill that aimed to forge a path to new elections. The two chambers congress were expected to debate the bill which would annul 20 October election and appoint a new electoral board within 15 days of its passage, paving the way for a new vote.[122] The bill, drafted jointly by MAS and anti-Morales legislators, was approved on 23 November; it also prohibited Morales from participating in the fresh election.[123] In exchange, Áñez's government agreed to withdraw the armed forces from all protest areas (although some servicemen were still permitted to stay at some state companies to "prevent vandalism"), revoke her decree which granted the army immunity from criminal prosecution, release arrested protesters, protect lawmakers and social leaders from attacks and provide compensation for the families of those killed during the crisis. She approved the bill shortly thereafter.[124]

Domestic policy[edit source | edit]

Immediately after his resignation, protests emerged in support of Morales and against the new government.[125] In response, Áñez signed decree no. 4078, granting total impunity to the armed forces to quell protestors. Resulting in the masacres of Senkata and Sacaba, where at least 18 people were killed.[126] This decree was subject to international criticism. José Miguel Vivanco, Americas Director of Human Rights Watch described the decree as, “give[ing] the armed forces a blank check to commit abuses instead of working to restore the rule of law in the country”.[127]

The Áñez administration appointed government ministers between 13 and 18 November.[128][129][130][131] The first eleven members of the interim cabinet, appointed 13 November, did not contain any indigenous members.[132][133] The Guardian described this partial cabinet as showing "no signs that [Áñez] intended to reach across the country's deep political and ethnic divide".[132] Áñez did, however, designate two persons of indigenous origin as ministers of culture and mining as the remaining positions were filled.[134][135] Morales's first cabinet was majority indigenous (14 out of 16 positions), though this number decreased over the course of his tenure as president.[136][137] Among the senior ministers in Áñez' cabinet were prominent Bolivian businesspeople.[132] Shortly after taking office, Áñez also appointed a new military high command.[95] The new commander of the armed forces, General Carlos Orellana Centellas, pledged to take orders from Áñez.[95][138]

On 20 November, Áñez granted safe-conduct to Evo Morales' daughter, Evaliz, to receive political asylum in Mexico.[139]

From early on, the interim government took the decision to fly the patujú in addition to the wiphala and Flag of Bolivia.[140] The patujú is a symbol of the Eastern indigenous peoples of Bolivia and of Santa Cruz, Bolivia's largest city. This flag was also adopted by indigenous opposition to Morales during the TIPNIS protests.[141]

The government renamed the state newspaper, known as Cambio under president Morales, as Bolivia on 17 November.[142] On 25 November, the Áñez met with civil groups Bolivian Workers' Center, the country's largest union, and the Pact of Unity, a prominent indigenous grassroots group, to sign agreements on how to pacify Bolivia following previous violent events.[143]

Patujú flag representing the eastern peoples of Bolivia

In the week following the inauguration of Áñez, the new government came under criticism. The New York Times described Áñez as "reaching beyond her caretaker mandate of organizing national elections by January".[111] Javier Corrales, a Latin American politics professor at Amherst College in Massachusetts, said "without a popular mandate, [the government] are pushing forward some of the most objectionable aspects of their agenda".[clarification needed] Oliver Stuenkel, associate professor of international relations at the Getúlio Vargas Foundation in São Paulo, said that "the only thing this government was supposed to do was calm things down and call elections, and that’s just about the only thing it has not done".[113]

By late November and December, progress was made in passing legislation for new elections,[144][145] appointing a new electoral body,[146] entering dialogue with representatives from protesting factions in El Alto [147] and cooperating with Morales' MAS party in joint participation in the coming elections,[148] albeit without Morales as a presidential candidate. A survey by Bolivian newspaper, Página Siete, showed that 43% of Bolivians approved of how Áñez has handled the presidency, while 23% disapproved.[149] On 13 Dec, Áñez approved an agreement between the three main parties over a so-called "Law of Guarantees" formulated to restore faith among political actors in the process of moving forward, including reparations for those killed and injured after she came to power.[150] This act was welcomed by the Secretary General of the UN.[151] A previous incarnation of this legislation, passed in both chambers by the MAS majority, had not been given presidential approval due to articles that implied immunity from prosecution for representatives of the previous government. This version was described by opposition lawmakers as an attempted "cover up" on behalf of the MAS party [152][153] and caused friction among members of MAS itself.[154]

On 1 January 2020, Áñez presented a change in the law that would it make it mandatory for presidential candidates to engage in public debate with their opponents to support "the strengthening of informed democracy". Morales has never taken part in such a debate.[155]

Foreign policy[edit source | edit]

Karen Longaric, appointed as foreign minister by Jeanine Áñez, announced the formal departure from the country of the Bolivarian Alliance for the Peoples of Our America (ALBA) and breaking all diplomatic relations with Venezuela's Maduro government,[156][157] recognizing Juan Guaidó as acting president of Venezuela in the Venezuelan presidential crisis.[158] Longaric also announced that the interim government was considering leaving the Union of South American Nations (UNASUR).[156]

A month later, the country announced its entry into the Lima Group, a regional bloc established in 2017 with the purpose of finding a way out of the Venezuelan crisis. The Bolivian foreign ministry said in a statement that it hoped to “contribute to a peaceful, democratic and constitutional solution to the crisis in Venezuela, which must be guided by the Venezuelan people.”[159] On the same month, the interim government announced that they would give refuge to 200 Venezuelans "who have fled their country for reasons of political order, of political persecution promoted by the Nicolás Maduro government."[160]

In January 2020, the interim government suspended relations with Cuba in response to remarks made by Foreign Minister Bruno Rodríguez Parrilla, who called Áñez a "liar," "coupist" and "self-proclaimed" in reference to her latest statements about the role of Cuban medical doctors in the country.[161]

Diplomatic row over Mexican Embassy[edit source | edit]

Since the resignation of Morales, several members of the past administration have taken diplomatic refuge in the Mexican Embassy in La Paz. Several of these are facing accusations and prosecution under the interim government, the most senior being the former Minister of the Presidency, Juan Ramón Quintana. Anti-Morales protesters have routinely gathered at the doorstep of the Embassy to voice their discontent and demand that they be turned over to the Bolivian authorities.[162] An increased security presence by police and army in the vicinity of the Embassy has led to accusations of harassment and a "siege". On 27 Dec, tensions were further increased visiting Spanish diplomats were stopped by police during a visit to the Embassy. The Mexican Embassador accused the Bolivian government of María Teresa Mercado violating the Vienna Convention on Diplomatic Relations.[162] Longaric responded by saying the presence of masked and armed guards aroused suspicion that there would be an attempt to smuggle Quintana from the Embassy to another location. "No country in the world could tolerate what happened last Friday. In that case, the Vienna Convention empowers the host State to declare those diplomats who violate the rules of the conventions themselves personas non gratas," Longaric said.[163] On 30 Dec, Áñez made an announcement giving a number of Mexican and Spanish diplomats 72 hrs to leave the country, Spain responding by declaring that three Bolivian diplomats likewise must leave the country.[162] Eva Copa, MAS head of the Senate, criticised Áñez for the expulsion of diplomats of countries who helped bring stability to Bolivia and urged her to reconsider the action.[164]

Counteractions[edit source | edit]

On 15 November, Longaric expelled 725 Cuban citizens, mostly medical doctors, after she raised concerns about their alleged involvement in protests.[156][165] The government announced it arrested nine Venezuelans in the border city of Guayaramerín (near Brazil) with boots and insignias of the Bolivarian National Police (PNB), identification cards of the United Socialist Party of Venezuela (PSUV) and microchips containing photos of themselves with other people armed with guns. After the arrest and the discovery of the microchips, the interim government accused the men of participating in "violent acts" in the country, and transferred them to the Bolivian Special Crime Fighting Forces to conduct a preliminary investigation.[166]

Arturo Murillo, Áñez's new interior minister, vowed to "hunt down" his predecessor Juan Ramón Quintana, a prominent Morales ally, stoking fears of a vendetta against members of the previous administration.[132] He later announced he would start arresting certain members of the previous government who he accused of "subversion".[167] Roxana Lizárraga, Áñez's communication minister, stated that she had a list of journalists who were "involved in sedition" and threatened them with prosecution.[111]

On 22 November, after an audio recording, allegedly of Morales, leaked in which Morales supporters were directed to block main roads to La Paz, the interim government opened an investigation into Morales for "terrorism and sedition".[168] Hours later, the vice-president of MAS-IPSP was arrested for allegedly using a car of the ministry of the President; in the car, according to Télam, police discovered computers and biometric devices that belonged to the electoral commission.[169][170]

Reactions[edit source | edit]

See also[edit source | edit]

References[edit source | edit]

  1. 1.0 1.1 1.2 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. 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 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  5. 5.0 5.1 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 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  7. 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. 9.0 9.1 9.2 9.3 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).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).
  10. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  11. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  12. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  13. 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. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  16. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  17. 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. 19.00 19.01 19.02 19.03 19.04 19.05 19.06 19.07 19.08 19.09 19.10 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. 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. https://www.nytimes.com/2020/06/07/world/americas/bolivia-election-evo-morales.html?auth=login-email&login=email
  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. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  33. 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. 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. 42.0 42.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  43. 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. 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. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  48. 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. OAS 2019, p. 56.
  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. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  57. 57.0 57.1 57.2 57.3 57.4 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  58. 58.0 58.1 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. 60.0 60.1 60.2 60.3 60.4 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. 63.0 63.1 63.2 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. 65.0 65.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  66. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  67. 67.0 67.1 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. 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).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).
  71. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  72. 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. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  76. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  77. 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. 79.0 79.1 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. 84.0 84.1 84.2 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. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  91. 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. 95.0 95.1 95.2 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. 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. 106.0 106.1 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. 111.0 111.1 111.2 111.3 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  112. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  113. 113.0 113.1 113.2 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  114. 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. 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. 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. 132.0 132.1 132.2 132.3 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. 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. 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 156.2 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).