ChromeOS This forum is for the discussion of ChromeOS. |
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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
10-14-2023, 03:35 PM
|
#1
|
LQ Newbie
Registered: Feb 2020
Location: East Moriches, NY
Distribution: debian
Posts: 16
Rep: 
|
two Chromebooks, one won't display old x11 apps properly
Hi,
I have two fairly recent Chromebooks both running crostini. Both are still in auto update stage. Almost everything works great on my HP a couple years old. The other is an Asus with a touchscreen. Both seem quite the same in ChromeOS. The problem is that the touchscreen model messes up widget fonts on many older x11 apps, including gv, xman, xgc. I tried disabling the touchscreen with flags, but that didn't change the issue. I prefer the simplicity of gv for postscript display, although evince and okular do work OK. But it is annoying since the Asus is so compact and puzzling since both machines seem quite identical in all other ways. Any thoughts?
Mike
|
|
|
10-15-2023, 08:33 AM
|
#2
|
LQ Guru
Registered: Sep 2011
Location: Upper Hale, Surrey/Hants Border, UK
Distribution: One main distro, & some smaller ones casually.
Posts: 5,936
Rep: 
|
I expect that your 2 machines use different graphics sub systems, which would explain the different characteristics.
|
|
1 members found this post helpful.
|
10-18-2023, 05:25 PM
|
#3
|
Senior Member
Registered: Dec 2009
Location: New Jersey, USA
Distribution: Fedora, OpenSUSE, FreeBSD, OpenBSD, macOS (hack). Past: Debian, Arch, RedHat (pre-RHEL).
Posts: 1,335
|
Could you give more detail on "messes up fonts"?
Touchscreen has nothing to do with it, so no need to disable it.
Are they both running the same version of ChromeOS? (Settings/About)
Auto updates are for ChromeOS itself and will do nothing for the crostini containers. Those you have to maintain yourself. Is the problematic container all up to date?
IIRC ChromeOS itself is Wayland based, so XWayland is used for those older X applications. Is one using a newer version of XWayland?
|
|
|
10-18-2023, 07:21 PM
|
#4
|
LQ Newbie
Registered: Feb 2020
Location: East Moriches, NY
Distribution: debian
Posts: 16
Original Poster
Rep: 
|
With gv, the main display on the asus is fine, but all the surrounding x widgets are totally scrambled, most letters are random blots. In presentation mode it is usable, although the
page widget is unreadable. Both machines are up to date as far as apt and google know.
Somallier is version 0.20 on each. Apt is version 2.2.4 (amd64) on the HP and
2.2.4 (arm64) on the asus; so there is a slight difference here.
On the chromebook side both machines behave identically.
Emacs works fine on both, but it doesn't use x widgets.
Xdvi is a disaster on the asus.
I can live fine with the older chromebook
and it is not to hard avoid the bad apps on the asus.
But this is all very perplexing and would like to understand what is happening.
What else should I check?
|
|
|
07-30-2024, 07:45 AM
|
#5
|
LQ Newbie
Registered: Feb 2020
Location: East Moriches, NY
Distribution: debian
Posts: 16
Original Poster
Rep: 
|
Samsung works, asus does not
Well I never did get the old linux programs working on the asus. Using okular instead of gv was my workaround. Just bought a Samsung non-touch chromebook and everything works perfectly. Somehow the asus touch screen does not interact properly with the linux development environment.
|
|
|
05-04-2025, 11:32 AM
|
#6
|
LQ Newbie
Registered: Feb 2020
Location: East Moriches, NY
Distribution: debian
Posts: 16
Original Poster
Rep: 
|
After not using the touchscreen Asus for many months, I updated it and the Linux touchscreen all works fine now. I did buy another Asus without touchscreen and it always worked, although the screen is a bit duller than the old one. Anyway, Chromebooks are great and all you ever need.
|
|
|
All times are GMT -5. The time now is 03:15 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|