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

Afghan peace process

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

Flags of the Taliban (left) and the United States (right)

The Afghan peace process comprises the proposals and negotiations in a bid to end the ongoing war in Afghanistan. Although sporadic efforts have taken place since the war began in 2001, negotiations and the peace movement intensified in 2018 amid talks between the Taliban, which is the main insurgent group fighting against the Afghan government and American troops; and the United States, of which 20,000 soldiers maintain a presence within the country to support the Afghan government. Most of the talks have taken place in Doha, the capital of Qatar. It is expected that a mutual agreement between the Taliban and the United States would be followed by a phased American withdrawal and the start of intra-Afghan peace talks.[1] Besides the United States, regional powers such as Pakistan, China and Russia, as well as NATO play a part in facilitating the peace process.[2][3]

On February 29, 2020, the U.S. signed a conditional peace agreement with the Taliban, which calls for the withdrawal of foreign troops in 14 months if the Taliban uphold the terms of the agreement.[4][5] On March 1, 2020, however, the Afghan government, which was not a party to the deal, rejected the U.S. and Taliban's call for a prisoner swap by March 10, 2020, with President Ghani stating that such an agreement will require further negotiation and will also not be implemented as a precondition for future peace negotiations.[6][7][8][9][10] On March 10, 2020, Ghani signed a decree agreeing to swap 1,500 Taliban prisoners starting March 14, 2020, but on the condition that they sign pledges agreeing to not return to combat.[11] The same day, it was also revealed that there were no plans for a full U.S. withdrawal from Afghanistan.[12] On March 10, the United Nations Security Council unanimously backed the U.S.-Taliban peace deal.[13]

On March 11, 2020, however, the Taliban rejected Ghani's prisoner swap proposal.[14][15][16] On March 14, 2020 the U.S.-Taliban peace deal became endangered when Ghani delayed the release of Taliban prisoners.[17] On April 7, 2020 The Taliban officially withdrew from prisoner swap talks,[18] which had been taking place in Kabul starting 30 March 2020 and only resulted in the release of 100 Taliban prisoners on 8 April 2020.[19][20][21][18]

Background[edit source | edit]

The Taliban, which refers to itself as the Islamic Emirate of Afghanistan,[22] is a Sunni Islamic organization that operates in Afghanistan, a country in Central/South Asia. The Taliban emerged in 1994, taking advantage of the power vacuum that was left following the aftermath of the Afghan Civil War.[23] The group was mainly composed of religious students in Pakistani madrassas (who had fought in the Soviet–Afghan War) under the leadership of Mohammed Omar.[24]

Al-Qaeda, an international terrorist network, were granted sanctuary in Afghanistan on the condition that it did not antagonize the United States, but Osama bin Laden reneged on the agreement in 1998 when he orchestrated bombings of US embassies in East Africa. The episode was indicative of tensions that emerged between the two groups. The Taliban was fundamentally parochial while Al-Qaeda had its sights set on global jihad.[24]

After the September 11, 2001 attacks, the U.S. under President George W. Bush made a request to the Taliban leadership to hand over Osama bin Laden, who was the prime suspect in the attacks.[25] The Taliban refused to hand bin Laden over, demanding evidence of his participation in the attacks.[26] Consequently, the U.S., together with its NATO allies, launched the United States invasion of Afghanistan, code-named Operation Enduring Freedom, on October 7, 2001. By December 17 that year, the U.S. and its allies had driven the Taliban from power and begun building military bases near major cities across the country. The International Security Assistance Force (ISAF) was later created by the United Nations Security Council to train Afghan National Security Forces to oversee military operations in the country so as to prevent any resurgence of the Taliban group. The Taliban has launched numerous attacks on the Afghan forces, government facilities, and any organization that they believe are in alliance with the US.[27]

The US has been on the ground and directly involved in the war for 18 years, with analysts describing the situation as a stalemate.[28] Although al-Qaeda in Afghanistan and Pakistan are now considered to be "diminished", the war with the Taliban insurgents continues.[29] Ending the 18-year conflict has eluded former US presidents, and Donald Trump has said that he considers the war too costly.[28] Similarities with the process to end the Vietnam War—America's longest war prior to 2010—have been noted, which resulted in the Paris Peace Accords in 1973.[30][31]

Negotiations[edit source | edit]

Obama administration[edit source | edit]

Negotiations had long been advocated by the former Afghan President, Hamid Karzai, as well as the British and Pakistani governments, but resisted by the American government. Karzai offered peace talks with the Taliban in September 2007, but this was swiftly rejected by the insurgent group citing the presence of foreign troops.[32] By 2009 there was broad agreement in Afghanistan that the war should end, but how it should happen was a major issue for the candidates of the 2009 Afghan presidential election[33] that re-elected Karzai. In a televised speech after being elected, Karzai called on "our Taliban brothers to come home and embrace their land"[34] and laid plans to launch a loya jirga. Efforts were undermined by the Obama administration's increase of American troops in the country.[35] Karzai reiterated at a London conference in January 2010 that he wanted to reach out to the Taliban to lay down arms.[36] US Secretary of State Hillary Clinton cautiously supported the proposal.[37] At the United States Institute of Peace in May 2010, Karzai stated that a "peace process" would be with the Taliban and other militants "who are not part of al-Qaeda or other terrorist networks or ideologically against us". Of the Taliban specifically, he stated, "They're countryside boys who don't hate the United States, perhaps a lot of them would like to visit the United States given the opportunity".[38]

The Taliban's co-founder and then-second-in-command, Abdul Ghani Baradar, was one of the leading Taliban members who favored talks with the US and Afghan governments. Karzai's administration reportedly held talks with Baradar in February 2010; however, later that month, Baradar was captured in a joint US-Pakistani raid in the city of Karachi in Pakistan. The arrest infuriated Karzai, and invoked suspicions that he was seized because the Pakistani intelligence community was opposed to Afghan peace talks.[39][40] The Afghan Peace Jirga 2010 took place in June 2010, however the Taliban did not attend the conference.[41]

A change of mindset and strategy occurred within the Obama administration in 2010 to allow possible political negotiations to solve the war.[42] The Taliban themselves had refused to speak to the Afghan government, portraying them as an American "puppet". Sporadic efforts for peace talks between the US and the Taliban occurred afterwards, and it was reported in October 2010 that Taliban leadership commanders (the "Quetta Shura") had left their haven in Pakistan and been safely escorted to Kabul by NATO aircraft for talks, with assurance that NATO staff would not apprehend them.[43] After the talks concluded, it emerged that the leader of this delegation, who claimed to be Akhtar Mansour, the second-in-command of the Taliban, was actually an imposter who had duped NATO officials.[44]

Karzai confirmed in June 2011 that secret talks were taking place between the US and the Taliban,[45] but these collapsed by August 2011.[46] Further attempts to resume talks were canceled in March 2012,[47] and June 2013 following a dispute between the Afghan government and the Taliban regarding the latter's opening of a political office in Qatar. President Karzai accused the Taliban of portraying themselves as a government in exile.[48] In January 2016, Pakistan hosted a round of four-way talks with Afghan, Chinese and American officials, but the Taliban did not attend.[49] The Taliban did hold informal talks with the Afghan government in 2016.[50]

Trump administration[edit source | edit]

US President Donald Trump accused Pakistan of harboring the Taliban and of inaction against terrorists, first in August 2017 then repeated the accusations in January 2018.[51][52]

On February 27, 2018, following an increase in violence, Afghan President Ashraf Ghani proposed unconditional peace talks with the Taliban, offering them recognition as a legal political party and the release of Taliban prisoners. The offer was the most favourable to the Taliban since the war started. It was preceded by months of national consensus building, which found that Afghans overwhelmingly supported a negotiated end to the war.[53][54] Two days earlier, the Taliban had called for talks with the US, saying "It must now be established by America and her allies that the Afghan issue cannot be solved militarily. America must henceforth focus on a peaceful strategy for Afghanistan instead of war."[55] On March 27, 2018, a conference of 20 countries in Tashkent, Uzbekistan backed the Afghan government's peace offer to the Taliban.[56] However, the Taliban did not publicly respond to Ghani's offer.[citation needed]

A growing peace movement arose in Afghanistan during 2018, particularly following a peace march which the Afghan media dubbed the "Helmand Peace Convoy".[57][58] The peace march was a response to a car bomb on March 23 in Lashkar Gah that killed 14 people. The marchers walked several hundred miles from Lashkar Gah in Helmand Province, through Taliban-held territory,[59] to Kabul. There they met Ghani and held sit-in protests outside the United Nations Assistance Mission in Afghanistan and nearby embassies.[60] Their efforts inspired further movements in other parts of Afghanistan.[61]

Following the march, Ghani and the Taliban agreed a mutual ceasefire during the Eid al-Fitr celebrations in June 2018. During the Eid ceasefire, Taliban members flocked into Kabul where they met and communicated with locals and state security forces. Although civilians called for the ceasefire to be made permanent, the Taliban rejected an extension and resumed fighting after the ceasefire ended on June 18, while the Afghan government's ceasefire ended a week later.[62][63][64]

American officials secretly met Taliban members in July 2018, at the latter's political office in Qatar.[65] In September 2018, Trump appointed Zalmay Khalilzad as special adviser on Afghanistan in the US State Department, with the stated goal of facilitating an intra-Afghan political peace process.[66] Khalilzad led further talks between the US and the Taliban in Qatar in October 2018.[67] Russia hosted a separate peace talk in November 2018 between the Taliban and officials from Afghanistan's High Peace Council.[68] The talks in Qatar resumed in December 2018,[69] though the Taliban refused to allow the Afghan government to be invited,[70] considering them a puppet government of the US.[71] The Taliban spoke with Afghans including former President Hamid Karzai, held at a hotel in Moscow in February 2019, but again these talks did not include the Afghan government.[72]

A further round of talks in Qatar were held in February 2019, this time including Baradar in the Taliban delegation[71] - he had been released by Pakistan in October 2018 at the US' request.[73][74] Khalilzad reported that this round of negotiations was "more productive than they have been in the past" and that a draft version of a peace agreement had been agreed. The deal involved the withdrawal of US and international troops from Afghanistan and the Taliban not allowing other jihadist groups to operate within the country.[71] The Taliban also announced that progress was being made in the negotiations.[71]

Between April 29 and May 3, 2019, the Afghan government hosted a four-day loya jirga to discuss peace talks. The Taliban were invited but did not attend.[75] Later in May, a third meeting was held in Moscow between a Taliban delegation and a group of Afghan politicians.[76] An eighth round of US-Taliban talks in Qatar was held in August 2019.[77] The Washington Post reported that the US was close to reaching a peace deal with the Taliban and was preparing to withdraw 5,000 troops from Afghanistan.[78] In September, Khalilzad stated that an agreement had been reached by the US and the Taliban, pending approval by Trump.[79] However, less than a week later, Trump canceled the peace talks in response to an attack in Kabul that killed an American soldier and 11 other people.[80] Following the collapse of the talks with the US, the Taliban sent a delegation to Russia to discuss prospects for a withdrawal of US troops from Afghanistan.[81] On September 18, 2019, the Taliban stated that their "doors are open" should Trump decide to resume peace talks in the future.[82]

Peace negotiations resumed in December 2019,[83] leading to a seven-day partial ceasefire which began on February 22, 2020.[84]

2020 agreement[edit source | edit]

US representative Zalmay Khalilzad (left) and Taliban representative Abdul Ghani Baradar (right) sign the agreement in Doha, Qatar on February 29, 2020

On February 29, 2020, the United States and the Taliban signed a peace agreement in Doha, Qatar.[85] The provisions of the deal include the withdrawal of all American and NATO troops from Afghanistan, a Taliban pledge to prevent al-Qaeda from operating in areas under Taliban control, and talks between the Taliban and the Afghan government.[86] The United States agreed to an initial reduction of its force level from 13,000 to 8,600 by July 2020,[87] followed by a full withdrawal within 14 months if the Taliban keeps its commitments.[88] The United States also committed to closing five military bases within 135 days,[89] and expressed its intent to end economic sanctions on the Taliban by August 27, 2020.[88]

The resulting intra-Afghan negotiations were scheduled to begin on March 10, 2020[88] in Oslo, Norway.[90] The composition of the Afghan government negotiating team has not yet been determined, because the results of the 2019 Afghan presidential election are disputed.[91] The deal requires the Afghan government to release 5,000 Taliban prisoners by the start of the talks, in a prisoner exchange for 1,000 government soldiers held by the Taliban.[89] The Afghan government was not a party to the deal, and on March 1 Ghani stated that he would reject the prisoner exchange: "The government of Afghanistan has made no commitment to free 5,000 Taliban prisoners. [...] The release of prisoners is not the United States authority, but it is the authority of the government of Afghanistan."[7][9][10][6] Ghani also stated that any prisoner exchange "cannot be a prerequisite for talks," but must be a part of the negotiations.[8] On March 2, a Taliban spokesperson stated that they were "fully ready" for the intra-Afghan talks, but that there would be no talks if about 5,000 of their prisoners are not released. He also said that the agreed-upon period of reduction in violence was over and that operations against Afghan government forces could resume.[92]

The Taliban resumed offensive operations against the Afghan army and police on March 3, 2020, conducting attacks in Kunduz and Helmand provinces.[93] On March 4, the US conducted airstrikes on Taliban fighters in Afghanistan's southern Helmand province.[94]

The intra-Afghan negotiations did not begin as planned on March 10, 2020. However, on that day Ghani signed a decree ordering the Afghan government to start releasing 1,500 Taliban prisoners on March 14 if they agreed to sign pledges guaranteeing they will not to return to battle[11] If they do not sign the pledges, the decree will not go into effect.[11] The same day, the U.S. started withdrawing some troops.[12] Despite the fact that the terms of the peace agreement also received unanimous backing from the UN Security Council,[13] sources close to the Taliban, including Taliban spokesman Suhail Shaheen, afterwards announced that the group had rejected Ghani's prisoner swap decree and still insisted on the release of 5,000 Taliban prisoners.[15][14][16] On March 14, 2020, Javid Faisal, a spokesman for the National Security Council, announced that President Ghani had delayed the release of Taliban prisoners, citing a need to review the list of the prisoners, thus endangering the peace agreement between the U.S. government and Taliban.[17]

On 27 March 2020, the Afghan government announced the formation of a 21-member negotiation team for the peace talks. However, on 29 March the Taliban rejected the team, stating that "we shall only sit for talks with a negotiation team that conforms with our agreements and is constituted in accordance with the laid out principles."[95] On 31 March 2020, a three-person Taliban delegation arrived in Kabul to discuss the release of prisoners.[21][96] They are the first Taliban representatives to visit Kabul since 2001.[21] The Afghan government had also previously agreed to hold the talks in Bagram Prison.[21] The same day, however, the Afghan government announced that the Taliban's refusal to agree to another ceasefire and the Taliban delegation's refusal to show up at the prison at the scheduled time both resulted in the postponement of the prisoner swap.[97][98][99] Following the arrival of the Taliban delegation, a senior Afghan government official told Reuters "the prisoner release might go ahead in a few days if everything goes as planned.”[96]

On 31 March 2020, the UN Security Council urged for all warring parties to declare a ceasefire in order for the peace process to progress further.[100][101] On 1 April 2020, it was revealed that the both the Taliban and Afghan government did in fact hold face-to-face talks in Kabul the previous day, unlike the previous video conference talks, and that they were overseen by the International Committee of the Red Cross (ICRC).[18] However, Afghanistan's Office of the National Security Council stated that the only progress made so far was "on technical matters" and Taliban spokesperson Zabihullah Mujahid afterwards stated "There will be no political talks there."[18] Outside the talks, tensions between the Afghan government and Taliban also showed when Afghan authorities blamed the Taliban for an 1 April 2020 explosion which killed several children in Helmand.[18] On the second second day of negotiations, it was agreed that on 2 April 2020, up to 100 Taliban prisoners would be released in exchange for 20 Afghan military personnel[102]

On 7 April 2020, the Taliban departed from the prisoner swap talks, which Taliban spokesman Suhail Shaheen described as "fruitless."[103][20] Shaheen also stated in a Twitter that hours after walking out of the talks, the Taliban's negotiating team was recalled from Kabul.[20] The Taliban also failed to secure the release of any of the 15 commanders they sought to be released.[103] Arguments over which prisoners to swap also resulted in a delay of the planned prisoner swap.[103] The next day, Faisal maintained that only 100 Taliban prisoners would be released.[20] Faisal later stated that the 100 prisoners, who were incarcerated at Bagram, were released.[19] The Taliban refused to verify these releases, in part due to the fact that the Taliban's withdrawal from Kabul prevented its "technical team" from making verifications of the prisoner identities.[19] As the Afghan government solely determined which prisoners were released, it also could not be confirmed if any of the prisoners released were on the Taliban's list of preferred names.[19]

Issues[edit source | edit]

Issues which are expected to arise during the negotiations include women's rights; the 2004 Constitution of Afghanistan protects women's freedom of speech and education, which had been suppressed under Taliban rule of Afghanistan. Khalilzad, Ghani, his rival for the presidency Abdullah Abdullah, and several other senior Afghan officials have all stated that these rights should be protected,[72][104][105] and should not be sacrificed in a peace agreement.[106] The First Lady of Afghanistan, Rula Ghani, has been active in protecting women's rights.[107]

Continued violence on both sides remains an obstacle to a final peace agreement. While preliminary talks were going on, the Taliban continued to fight on the battlefield and launch terror attacks in the capital city, and also threatened the 2019 Afghan presidential election on September 28.[108] According to US Air Force statistics released in February 2020, the US dropped more bombs on Afghanistan in 2019 than in any other year since 2013.[109]

The US ambassador to Afghanistan warned that a peace agreement could risk the Taliban coming back into power, similar to the aftermath of the 1973 Paris Peace Accords, during which the US-supported South Vietnamese government was defeated in the Fall of Saigon.[110][111] Pakistan warned that rising tensions in the Gulf region after the killing of Iranian general Qasem Soleimani could affect the already-delayed US-Afghanistan peace process.[112]

See also[edit source | edit]

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. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  4. 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).[permanent dead link]
  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. 7.0 7.1 https://www.politico.com/news/2020/03/01/afghan-peace-deal-prisoner-release-118473%7Ctitle=Afghan peace deal hits first snag over prisoner releases|author=Associated Press|publisher=Politico|accessdate=March 1, 2020}}
  8. 8.0 8.1 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 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 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 11.2 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 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  14. 14.0 14.1 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 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  18. 18.0 18.1 18.2 18.3 18.4 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.0 19.1 19.2 19.3 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  20. 20.0 20.1 20.2 20.3 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  21. 21.0 21.1 21.2 21.3 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. 24.0 24.1 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. 28.0 28.1 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. 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. 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. 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. 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. 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 71.2 71.3 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 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. 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. 88.0 88.1 88.2 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  89. 89.0 89.1 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. 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. 96.0 96.1 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. https://borneobulletin.com.bn/afghan-prisoners-exchange-postponed/
  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. 103.0 103.1 103.2 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. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).