They are different package formats. The updates from Control Center are for deb packages mostly, while some native applications are provided in Linyaps( https://linyaps.org.cn/en ), which need to be updated through App Store or Terminal.
deepin That's precisely what I'm requesting be taken into account in future developments. It doesn't make sense that updates from the control center only update third-party applications/packages but not native applications, forcing users to go to the terminal or an external link like Linyaps (https://linyaps.org.cn/en) or the app store to complete the update, and without a system backup.
As an end user, I shouldn't have to know where to update the system from. When I go to the control center and check for updates, and they are available, the update should cover the entire installed system. The user should be able to decide from the control center what to update and whether to back up the system during the process. Otherwise, the current procedure seems incomplete. The system isn't fully updated, and a system backup isn't created as and when it should be. I just want to clarify that this is only a suggestion, and as a Deepin user since version 15, I believe, thank you very much.
Popular Ranking
ChangePopular Events
More
中文 
The native Deepin applications aren't updated
Why is it that when I update the system from the Control Center, Deepin's native applications don't update, and I have to run the command "sudo ll-cli upgrade" from the terminal for them to update? Also, when I run the update check from the Control Center, the system often tells me there are no pending updates, but when I run the command "sudo ll-cli upgrade," there are updates for native applications, and they are updated, but no backup is created during the process. I believe that when updating from the Control Center, the native applications in LongArch64 format should also be updated. Thank you very much.