[SOLVED] after dist-upgrade, unicode font trouble on xterm (trixie, amd64)
DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
after dist-upgrade, unicode font trouble on xterm (trixie, amd64)
Dear experts:
I am delighted to seek for advice here.
What happened
After dist-upgrade, unicode goes wrong on xterm.
System
Debian trixie, amd64.
Troubleshooting process
1. Mixed up content piped into txt file. This txt file has correct content, (checked by libreoffice).
2. Checked locale, looks OK.
3. Font is good. (When mixed up content is selected by mouse, correct content shows.)
4. Check if uxterm works. No, situation is same.
5. Check changelog and bug report, which results nothing.
So far, I have not touched ".Xresources". Last update was May 2022, bookworm era.
Can experts direct me to next step?
cheers
Added on edit:
It looks like that
unicode content shows correct, when it follows "clear"
it goes wrong, after scroll.
Last edited by kaz2100; 07-19-2023 at 07:21 PM.
Reason: additional info
If you upgraded using standard procedure and the way text rendering occurs has gone from correct to incorrect, then you have encountered a bug.
Either it's a known bug or a unknown one.
If it is unknown, the sooner it gets reported, the sooner it can be addressed by those that know that package best, and the fewer people affected.
If it has already been reported, there may be a known fix/workaround, or there may be maintainers hoping for more diagnostic information to help them figure out where the issue is.
In all cases, there is no benefit to spending several more days before reporting it, and nothing stopping you doing further troubleshooting (if needed) after reporting it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.