{"id":11852,"date":"2026-05-20T18:45:45","date_gmt":"2026-05-20T17:45:45","guid":{"rendered":"https:\/\/innovatenews.site\/index.php\/2026\/05\/20\/deepins-security-problems-just-cost-it-another-major-linux-distro\/"},"modified":"2026-05-20T18:45:50","modified_gmt":"2026-05-20T17:45:50","slug":"deepins-security-problems-just-cost-it-another-major-linux-distro","status":"publish","type":"post","link":"https:\/\/innovatenews.site\/index.php\/2026\/05\/20\/deepins-security-problems-just-cost-it-another-major-linux-distro\/","title":{"rendered":"Deepin's security problems just cost it another major Linux distro"},"content":{"rendered":"
\n

The topic Deepin’s security problems just cost it another major Linux distro<\/strong> is currently the subject of lively discussion \u2014 readers and analysts are keeping a close eye on developments.<\/p>\n

This is taking place in a dynamic environment: companies\u2019 decisions and competitors\u2019 reactions can quickly change the picture.<\/p>\n

There are a lot of desktop environments out there, but only a few can claim the title of being truly beautiful. One of them is Deepin, a Chinese-based DE that also has its own distro. We’ve given the distro a try in the past and found that it “looks more beautiful than anything Microsoft or Apple ever made.”<\/p>\n

However, it seems the desktop environment is having a rough time staying in place on other distros. Just over a year since SUSE retired Deepin’s packages from its OS, the Fedora team has gotten together and agreed to do the same.<\/p>\n

\"\"<\/figure>\n

As reported by Phoronix, this story starts back in May 2025, when SUSE decided to cut ties with Deepin. The desktop environment had security issues, and SUSE noted that there were “attempts by the packager to bypass SUSE’s security review process.” This then prompted Fedora to take a look, with a review that contained this stinging remark:<\/p>\n

This might also be a good juncture to ask ourselves why we are apparently a long way behind SUSE in terms of having policies and mechanisms for reviewing security-sensitive package changes.<\/p>\n

The Fedora team then tried to get some fixes out alongside the Deepin team, but things began to fall apart. From the comments, it looks like the Fedora team lost contact with some of the key people behind implementing Deepin. The Fedora team created an ultimatum: it would try one more time to get in touch with the people behind Deepin’s maintenance, as “the DDE packages appear to have been in very bad shape for an extended period of time.” If they didn’t reply within four weeks, Fedora would ditch Deepin.<\/p>\n

\"\"<\/figure>\n

Well, that was a month ago, and as you may have expected, some key people within Deepin didn’t get back to the Fedora team, while those who did claimed that people were simply too busy to work on Fedora’s problems. As such, Fedora pulled the plug:<\/p>\n

TOPIC:#3409 Deepin security review request (@siosm:fedora.im, 17:08:35)<\/p>\n

AGREED: Retire all packages maintained by the deepinde-sig group, with the message mentioning the fesco ticket. Ask releng to not unretire those packages if a request is made, unless they passed review again. APPROVED (+7, 0, 0) (@siosm:fedora.im, 17:31:41)<\/p>\n

So it seems that it’s not a complete ban; Deepin can get itself back on Fedora if it undergoes a review. However, it may not come back for a while, if ever.<\/p>\n

After a decade of loyalty, I finally bid farewell to Ubuntu, but not without a heavy heart.<\/p>\n