OpenMandriva’s latest brush with internal conflict has rattled the Linux community. A former contributor with lingering admin rights wiped portions of the project’s GitHub repositories. He pushed an empty package aimed at obsoleting GNOME and COSMIC desktop components. The moves could have broken systems for users on those environments. Yet the damage stayed limited. Recovery efforts began immediately.
The incident unfolded in early July 2026. It started with a dispute over contributor behavior. One individual turned abusive toward users and team members via private messages and public attacks. Project leaders kicked him from the Matrix chat channel for OpenMandriva Cooker. They stopped short of a full ban. In retrospect, one developer admitted regret over the slow response. “I didn’t ban him, just kicked him out,” the statement read. Two people left the project, including Davide Beatrici.
Beatrici, best known as the lead developer of the Mumble voice chat application, had earned trust earlier. He migrated the project’s repositories from GitHub to his private OneDev instance and created backups. Those admin privileges remained active. After the departures, he acted. He deleted years of work from GitHub. He published the empty package in the Cooker development repository. The package carried instructions to remove GNOME and COSMIC support entirely.
Inside the Dispute That Led to Sabotage
AngryPenguin, a longtime OpenMandriva maintainer, laid out the sequence in a forum post. The team had welcomed Beatrici and others. They appreciated his help with infrastructure. But tensions rose. One new contributor directed hostility at users and members. The project removed him from chat. Beatrici and another participant exited. Then came the deletions. “This infuriated Davide so much that, abusing of the administrative privileges he still had, he sabotaged the distribution today in the early morning hours,” AngryPenguin wrote. (OpenMandriva Forum)
The statement stressed transparency. It warned the open source community about Beatrici’s actions. It described the deletions as targeting work accumulated over a decade. One maintainer noted personal investment spanning nearly ten years, set to mark a full decade in September 2026. The empty package, if installed, risked leaving GNOME or COSMIC users with broken desktops. But quick detection prevented widespread rollout.
Beatrici pushed back. In comments relayed by The Lunduke Journal and covered by BleepingComputer, he rejected the sabotage label. “Let me state right away that this was by no means a ‘sabotage.’ I’m not the kind of person to do something like that,” he said. He explained his moves targeted only Cosmic and GNOME repositories on GitHub and corresponding Cooker packages. The trigger, he claimed, came from other members deleting “.onedev-buildspec.yml” files without consultation. Those members, according to Beatrici, favored KDE and LXQt focus and showed little regard for security or clean Git history. He insisted his goal was never to harm users or the distribution he had supported for three years. (BleepingComputer)
Phoronix first broke the news to a wide technical audience on July 8, 2026. Michael Larabel highlighted the deleted repository parts and the nefarious package push. He noted the potential impact on GNOME and COSMIC users. The article pointed back to the forum statement for full context. OpenMandriva developers moved fast to restore what was lost. They addressed the obsolete package. A full audit followed to check for other unauthorized changes. No additional violations turned up. (Phoronix)
The project traces its roots to the 2012 fork of Mandriva Linux after the original company’s decline. It stands apart by building most packages with the LLVM/Clang compiler rather than GCC. Recent releases like Lx 6.0 Rock in April 2025 shipped KDE Plasma 6 by default, Linux 6.14 kernel, and options for GNOME, LXQt, Xfce, and early COSMIC. That desktop diversity made the targeted removal especially pointed. Users on rolling Cooker branch faced the highest risk.
But here’s the larger point. Open source projects run on trust. Contributors gain commit rights, repository access, and sometimes production repository control. When disputes turn personal, that trust can shatter. Beatrici’s retained privileges after leaving illustrate the gap. Many projects rely on social norms rather than strict access revocation policies. This case shows why those norms fall short.
Discussions on Hacker News and Reddit quickly broadened. Commenters debated governance models. Some pointed to similar past incidents in other distributions. Mageia, another Mandriva descendant, received passing mentions as a more stable fork. Others stressed the need for two-person rules on destructive actions and automated mirrors outside any single contributor’s control. OpenMandriva had backups thanks to Beatrici’s earlier work. That helped. Still, the deletion of decade-old material stung.
The team chose not to pursue legal action. “Although these actions constitute a criminal offense, we have decided not to take any legal action against him,” the statement said. They viewed the behavior as shameful but drew the line at court. The focus stayed on restoration and prevention. A complete security review is underway. New controls on administrative access will follow.
Beatrici’s defense added nuance. His three years of contributions included infrastructure improvements. The buildspec file deletions apparently violated his expectations for coordination. Disagreement over desktop priorities, KDE versus broader support, had simmered. Yet the method, deleting repositories and forcing package obsolescence, crossed into destructive territory. Even if intent stopped short of total project ruin, the effect risked user disruption.
Recent coverage reinforces the pattern. BleepingComputer on July 9, 2026, detailed both sides and noted unanswered outreach to Beatrici and the Mumble team. X posts from cybersecurity accounts framed the event as a supply-chain reminder. Internal actors can pose as much risk as external ones. One post from Blue Team News amplified the BleepingComputer story to thousands of followers.
OpenMandriva’s response offers lessons. First, revoke privileges immediately upon departure. Second, maintain independent mirrors beyond any contributor’s infrastructure. Third, document and enforce contribution guidelines that survive personality clashes. The project already audits systems. It restores deleted code. Users on stable branches likely noticed nothing. Cooker users may have seen warnings or held updates.
And the community watches. Linux distributions depend on volunteer labor. Drama like this can deter new participants. It also highlights how small teams balance speed with safety. OpenMandriva never grew to the scale of Fedora or Ubuntu. Its LLVM focus and desktop choices attract a niche. That makes internal stability even more vital.
Recovery continues. The statement promised ongoing updates. No evidence suggests broader compromise. The audit cleared other accounts. Yet the event lingers as a warning. Trust remains essential. Verification matters more. Projects that treat admin rights as permanent invitations court exactly this outcome. OpenMandriva survived. Others may not be so fortunate.
WebProNews is an iEntry Publication