Deepin 25：请倾听全球用户的声音

[Meliodas2077]

大家好，

我想就一个非常重要的问题发表我的看法。我在多个系统上深入测试了 Deepin 25，并在之前的帖子中提到了一些严重的问题，而这些问题并不仅仅是我一个人遇到的，而是影响到了世界各地的大量用户。

我不理解为什么在社区中，有些帖子明明反映了真实的问题，却被直接关闭（marked as “closed”）。Deepin 是一个开源项目，属于整个开源社区，而不是某一个国家或群体。开源的精神是自由、协作与透明，应该欢迎来自世界各地用户的反馈与建议。

我甚至尝试用中文发言，就是希望能够更直接地沟通，推动问题的解决。因为我非常认同 Deepin 的潜力，也希望它能在全球范围内取得成功。

我本人长期活跃在开源社区，主要在 Debian 社区。Deepin 也是基于 Debian 开发的系统，对我来说有着特别的意义。我不是来批评的，而是带着建设性建议，希望 Deepin 能够变得更加易用，更加国际化，更加符合全球用户的期待。

以下是我个人测试中发现的一些关键问题：

1. 加密时的键盘布局问题
   使用非亚洲布局（如德语或美式键盘）时，" 符号无法输入，即使切换成 US 键盘也无效。我已尝试在启动 ISO 前通过 GRUB 添加 de_DE.UTF-8 和无重音键盘布局，但仍无法解决问题。这个问题对系统加密用户来说是致命的。

2. 安装流程不合理
   建议在安装引导界面中首先选择键盘布局，然后再输入用户名和密码。否则输入过程中可能出现字符错误，影响用户体验。

3. 缺少全局单击设置
   在 Deepin 23 中可以全局启用单击操作，Deepin 25 中只能在文件管理器内设置。这对很多用户尤其是行动不便者并不友好，希望恢复该功能。

4. 界面风格缺乏 Deepin 原有的独特性
   Deepin 25 的外观虽然现代，但部分设计过于类似 Windows。我更喜欢 Deepin 过去那种有辨识度的风格。希望未来版本能重新找回 Deepin 自己的设计语言。

5. 请认真对待用户反馈
   我们花时间测试、写报告、总结问题，是出于对这个项目的支持和热爱。这些反馈是礼物，不是批评。关闭问题不等于解决问题，真正的进步来自倾听和改进。

我衷心希望我的建议能为 Deepin 项目的发展带来一些正面推动。也祝 Deepin 团队在未来取得更大的成功。

三人行，必有我师。
三个人同行，其中必有可以让我学习的人。
—— 希望我们都能互相学习，共同进步。

感谢大家的关注！

[BLumia]

Thanks for the feedback! To avoid confusion that might cause by machine translation, feel free to use English as well.

1. 加密时的键盘布局问题
2. 安装流程不合理

For the 2nd feedback, It's known that we can improve keyboard layout support and it's planned to improve such support in future updates.

For the 1st feedback, do you mean the keyboard layout option from Control Center doesn't work at all when LUKS disk encryption is enabled?

3. 缺少全局单击设置

I can't recall if other deepin components uses double-click to open folder/execute file, so such feature request might sounds ideal but actually useless. Or did I miss something?

4. 界面风格缺乏 Deepin 原有的独特性

TBH IMO modern Windows nowaday looks more and more like Linux desktop environments. I personally think it's more important to address the bugs that users are facing (e.g. the keyboard layout one you've mentioned above) than changing the UI just to make it look different from Windows :p

我不理解为什么在社区中，有些帖子明明反映了真实的问题，却被直接关闭（marked as “closed”）
5. 请认真对待用户反馈

Just to be clear, we do treat user feedback seriously, and we always do! If you are referring to #11781 and https://github.com/orgs/linuxdeepin/discussions/11828, it's very important to note that please ensure all feedbacks are actually tested by human being to ensure the bug is actually valid. #11781 looks very specious since even its first mentioned issue is invalid. Adding that the post looks like in a format that it's LLM-generated, we would rather do look into other bug reports than spending time validating if the remaining content is actually valid.

If that report by any chance is NOT LLM-generated, I personally suggest use English and avoid using LLM for bug report so it could reduce the chance that machine translation software and/or LLM might turn the original valid issue into something that might sounds incorrect and invalid 😂

---

By the way, we do have an International Testing group, are you already in that group? If not, I can send an invite so you (and other users who wants to help out) can join :)

[UMSGirl]

BLumia,

okay, yes, I use AI assistance when writing. Not because I'm lazy, but because I have respect for you guys and thought properly formulated reports are better than my broken English. I wanted to come across as professional, not like a troll.
I've been testing Linux distributions for various publications for years. I completely tested Deepin 25, from the first alpha to the final release. Not just me, but a whole team of people from different countries. We used real hardware, made real installations, found real problems.

The LUKS keyboard problem is damn real. Take a German keyboard, do an encrypted installation, try to enter your password. Doesn't work. This isn't a phantom problem, this is a blocker for every European user. I tested this on three different computers. Same problem every time.

Single click mode was available system-wide in Deepin 23. In Deepin 25 it's only in the file manager. That's a regression, not an improvement. People with motor disabilities depend on it. Why was this removed?

4K display scaling is broken. Fonts are blurry, UI elements scale wrong, icons are pixelated. These aren't minor issues, this makes the system unusable on modern monitors.

Treeland compositor crashes regularly. Not just sometimes, but reproducibly. Open a few applications, switch between desktops, boom, black screen and restart. This is a stability problem, not a feature.

Office applications have layout problems. LibreOffice, WPS Office, Qt applications. The UI is mangled, menus overlap, buttons are cut off. This isn't an edge case, these are the most important productivity apps.

You know what really pisses me off? I invested months testing and documenting Deepin. Not because I get paid for it, but because I believe in the project. And then I get this kind of response from you, like I'm some troublemaker.

I work for the press. I write about Linux, about open source, about community management. Deepin is on my list for a major article. The only question is whether it'll be a positive story about technical innovation or a negative one about arrogant community management.

You say we're wasting your time? I say you're wasting our time. Point release 25.0.1 is out, but none of the documented problems were addressed. Instead, testers get insulted.

I thought KDE had problems with community feedback. But this is a whole new dimension. At least there bugs don't get dismissed as AI hallucinations.

The problems exist, other users confirm them too, and you ignore them. This doesn't get better by attacking the messengers.
Either you take feedback seriously or you don't. But then don't waste our time with responses like this.
I'm going to write my article either way. You're writing the story yourselves with your behavior.

Kind Regards

[BLumia]

I invested months testing and documenting Deepin. Not because I get paid for it, but because I believe in the project. And then I get this kind of response from you, like I'm some troublemaker.
You say we're wasting your time? I say you're wasting our time.
The problems exist, other users confirm them too, and you ignore them. This doesn't get better by attacking the messengers.

Still, first thing first. I'd like to get it 100% clear. I thought AI hallucinations is wasting my time, not "you" (real person). I've got other AI- or bot-generated feedbacks before (while not under the linuxdeepin organization), you will understand if you also facing such issue.

As long as we are sure it's not AI hallucinations but lacking additional information to reproduce given issues, we will continue looking into the issues reported.

By the way I am one of the developers that actually fixing the l10n/i18n issues, not a "public relation" guy.

I use AI assistance when writing. Not because I'm lazy, but because I have respect for you guys and thought properly formulated reports are better than my broken English.

Broken English is 1000% better than Chinese content that doesn't make sense. "技术现状分析" indicates it's not a bug report (which it actually is). "经过从预览版、Alpha、Beta到2025年6月26日最终发布的密集社区共创测试阶段，Deepin 25以"全面进步，全新焕发"为主题，带来超过1000项优化和四大主要创新。社区持续进行从所有开发阶段到当前生产环境使用的全程测试。" is a classic glowing term that might only appear in a presentation. "关键系统阻塞问题" is never something that can be decided from the end user but the project leader/manager. You can imagine how much confusion it brings, and it can only get worse if we keep reading the remaining content...

The LUKS keyboard problem is damn real. Take a German keyboard, do an encrypted installation, try to enter your password. Doesn't work.

TBH, this exact sentence is way more useful than the original one you provided in https://github.com/orgs/linuxdeepin/discussions/11828. This sentence we know, to reproduce we should:

• Take a German keyboard,
• do an encrypted installation,
• try to enter your password. Doesn't work.

and there are no other obstacles that can cause confusion understating the exact issue.

Since now we know, I'll ensure this issue is tracked.

For convenience, here is a list of issues that you mentioned here that I've tracked:

• Take a German keyboard, do an encrypted installation, try to enter your password. Doesn't work.
• Single click mode was available system-wide in Deepin 23. In Deepin 25 it's only in the file manager.

Some other remaining issues need additional information, like the LibreOffice one (e.g. are you getting it from apt install or the built-in app store? Their versions are not the same), WPS Office one (which version? The international one? WPS 365? Other possible version?), "Qt application" one (As I response in the original post, Krita works fine, and I don't know which one is actually having trouble). I hope more useful information can be provided to help us triaging issues.

4K display scaling is broken. Fonts are blurry, UI elements scale wrong, icons are pixelated.

In our bug tracker there are tons of similar reports and different components have different root causes for the Hi-DPI issues. It's worth posting some screenshots so we can know which component(s) you are referring to. It might be known or new issues depends on your actual case.

Treeland compositor crashes regularly. Not just sometimes, but reproducibly.

As previously mentioned, Treeland is still in tech preview phase. It has known issues and lacking features that are still on the roadmap to be implemented. It's not supposed to be daily-drived by the end user at least for now.

You know what really pisses me off? I invested months testing and documenting Deepin. Not because I get paid for it, but because I believe in the project. And then I get this kind of response from you, like I'm some troublemaker.

I'm sorry if my previous response lets you feel that way, I hope my current response can get things clear. I respect everyone that takes their time contributing to open source, I really hope you don't get me wrong.

Kind Regards

[Meliodas2077]

🔹 English Version

Hello and thank you for your reply

I’ve seen that another point-release for Deepin 25 has been released recently, which shows that the project is actively maintained – and I really appreciate that. However, I have to be honest: the issues I previously reported are still not resolved.

About the installer sequence:

What I wrote in my original feedback wasn’t a random opinion. This structure has proven itself for years, especially in Debian-based systems. The keyboard layout and language selection should come at the very beginning, before entering any passwords. This is not a rare wish – it's a well-established standard in user-friendly system installers. Maybe it would be useful to take some inspiration from the Debian installer here, especially regarding modularity and international accessibility.

About my Chinese:

I'm not a native speaker, so I can't be sure if my Chinese is 100% correct. But I hope the intention comes across. At least it shows I'm trying to communicate directly. Maybe other users will also understand what I meant, even if it's not perfect.

About the Deepin group:

If there is a group or dedicated chat channel, I’d be glad to join. Please share a link if possible – I’d love to contribute more directly.

About LLM usage (Language Models):

Using AI to help with phrasing doesn’t mean the content isn’t my own. Like many others, I use these tools to better express technical thoughts in a foreign language. I think, write, and check what I want to say. I don't let the LLM make up anything. It’s just a way to write clearer. This is a common and accepted tool worldwide, especially in international open-source communication.

It was disappointing to see a detailed post like #11781 being dismissed as “LLM-generated” just because it was well-structured. We should encourage precise and helpful reports, not judge them by format alone.

And just to clarify: if needed, I could even remaster the Deepin 25 ISO myself. I have the skills to adjust packages, keyboard settings, and layout. I could easily provide a more user-friendly version for others. But I would much prefer if such improvements came from the official project – not as workarounds by individuals.

Thanks again for your time. I’m not here to criticize – I’m here to help Deepin become stronger and more globally usable.

🔹 Chinese Version （中文翻译）

大家好，谢谢你们的回复

我注意到你们最近发布了 Deepin 25 的新版本，这表明项目仍在积极维护，这一点我非常感谢。但我必须坦率地说：我之前反馈的问题目前仍然没有解决。

关于安装流程的问题：

我在原始反馈中提到的并不是临时的想法。这种安装顺序在 Debian 等系统中已经验证多年，实践中效果非常好。键盘布局和语言选择应当在安装开始时就完成，而不是在设置用户名或密码之后。这并不是什么“特殊需求”，而是提升用户体验的标准流程。建议可以参考一下 Debian 的安装器，在模块化和国际化方面做得非常好。

关于我写的中文：

我不是中文母语者，所以无法判断我的表达是否完美。但我希望大家能理解我的用意。至少我在努力用中文与大家沟通。即使语言不完美，也许其他用户可以理解我的意思。

关于 Deepin 群组：

如果你们有专门的讨论组或社区交流群，我非常希望能加入。请分享一个链接，我希望能更直接地参与到项目中来。

关于使用 LLM（语言模型）的问题：

我确实使用了 AI 来帮助我更好地表达内容，尤其是在使用非母语写技术报告时。但这并不意味着这些内容不是我自己思考出来的。我自己构思内容、结构、检查逻辑，然后借助工具来表达得更清楚一些。这已经是全球开源协作中非常常见的方式。

坦率地说，我觉得像 #11781 这样的帖子被直接归类为“LLM生成”并因此忽略，是非常可惜的。我们应该鼓励清晰、有条理的问题反馈，而不是仅凭格式来否定其价值。

另外，如果真的有必要，我完全可以自己重新打包 Deepin 25 的 ISO。我有能力调整键盘布局、语言配置、系统组件，甚至可以为其他用户提供一个更加友好的版本。但我更希望这些改进能由官方实现，而不是让用户自己去解决。

再次感谢你们的时间。我不是来批评的，我只是想帮 Deepin 变得更强大、更国际化。

[BLumia]

It was disappointing to see a detailed post like #11781 being dismissed as “LLM-generated” just because it was well-structured.

I guess this will be the most important issue for me to respond to.

This (being dismissed as “LLM-generated” just because it was well-structured) is NOT the case.

Firstly, the first issue mentioned in that thread is invalid. I have used Krita for years, of course I know it's Qt 5-based and it's not broken. I also tested it in a clean installation of deepin 25, and I even attached a screenshot of me validating such issue. If the reporter uses LLM to generate feedback content and cannot even get the first one right, I doubt if the following reports can be valid.

Secondly, we don't accept "Priority Assessment" from the end user, and also some of the "Technical Root Causes" doesn't make sense. It's pretty weird and specious having user feedback and comes with a "Priority Assessment" or incorrect "Technical Root Causes". Adding that the first issue it mentioned is not valid, it really gives me a feeling that this is a pure LLM-generated task assignment thread.

The first time I checked #11781 took me more than 30 minutes to validate the first issue mentioned in that thread in a clean environment. When I get the result that the issue is invalid, add that the specious content. I really do feel frustrated and think it's not worth wasting time validating the rest of them.

Trigging and fixing issues is pretty time consuming. It's absolutely okay to use LLM as an accessibility tool, but PLEASE validate the issues before reporting, or simply don't use LLM for bug report. All we care about is if we can reproduce the bug so we can address it. The most important stuff is providing valid/correct/real information to help us triaging/reproducing issue. Any INVALID content will make triaging issues harder. I "dismissed" (actually, "closed") the issue simply because I saw too much invalid stuff at the first glance and also after validating the first issue it mentioned, not because of its "well-structured".

a detailed post like #11781

And also to be clear, that one and the other one reported by the same person are the only two issues/discussions closed by me because it looks specious. "Closing" that issue simply means I don't think it's valid. If helpful information is provided, it can be reopened as well. It doesn't mean "We don't accept issue from you anymore"

---

For other questions:

the issues I previously reported are still not resolved.

Triaging, addressing, fixing issues take time. You need to at least wait for a release cycle to get the bugfix delivered to the end user. Don't expect your issue to be delivered to the user in a single day (unless it's a security-related one).

About the installer sequence:

Yeah, we do get similar locale-related feedback. It's known and planned to be improved in the future. See my original response to you: https://github.com/orgs/linuxdeepin/discussions/11838#discussioncomment-13635319

About my Chinese:

Please feel free to use either English or Chinese. We accept both of them.

About the Deepin group:

If you use Telegram, consider use this link https://deepin.org/to/tg to join the chat. Once joined, you can ping the admin (or me) to let us invite you to the internal testing group if preferred.

About LLM usage (Language Models):
Using AI to help with phrasing doesn’t mean the content isn’t my own.

I have to say I agree with you, and that's why I am responding to your issue because your feedback looks saner without extra contents that can cause confusion. Or simply put: I don't care if a post is written with or without the help of LLM. I only care if the content it described is valid.

And just to clarify: if needed, I could even remaster the Deepin 25 ISO myself.

I actually have good news for you if you can do so! For your own need, you can use https://github.com/chenchongbiao/iso-build-deepin to build a Calamares-based ISO, which doesn't use deepin's first-party installer. Be aware that that project is not officially supported, but it can be handy to build custom ISOs before the installer team fixes the issues you (and other international users) want us to be fixed :)