Subj : Re: Graphics driver quest To : Barry Martin From : Ky Moffet Date : Sun Sep 14 2025 14:38:00 BARRY MARTIN wrote: > Hi Ky! > > (I know: overquoting!) That can be fixed! *RRRRRRRRRRRRRRPPPPPP* -- sound of rampaging delete key > KM> Yeah, you can get artifacting in one program but not in another, > KM> so not a huge surprise that the terminal was different. > > Initially I was figuring along the lines of Terminal being old school > and without graphics, or at least minimal graphics. That sort of got > voided because while Terminals in the "overlay" (^*) options were noisy > Terminal in the primary screen were not. My guess is that's the right track, wrong culprit. Not exactly oldschool but using an old version of the GTK toolkit (the programming framework that produces the window decorations and such that the user sees onscreen), which responded less gracefully than its neighbors. On Gnome desktop, it's all pretty much GTK apps by default. (KDE desktop, Qt apps by default.) > *^ "Overlay" meaning using programmes like VirtualBox and Remmina to > obtain another machine screen over my main one. Oh. Yeah, I don't know what you'd properly call that. But the making-it-happen would be before it got to the display server (what actually sends data to the screen). And that may not be the same depending if you're using Wayland or X11. You can check in whatever Ubuntu uses to spit up such info (in KDE it's InfoCenter). https://news.itsfoss.com/ubuntu-25-10-wayland-only/ Everything had to be recompiled for Wayland, and some programs still haven't been, and may misbehave in new and different ways, and different ways again if you have an NVidia graphics card. > KM> Does sound like it's cuz one has halfbaked support. Sometimes all > KM> you can do is experiment til you find the combo that works. > > It was sort of fun experimenting what caused the noise. Found in one > e-mail an up_arrow graphic was a little noisy on the new 75 Hz screen > but not on the old 60 Hz screen. So much for that Terminal Theory! Ah, that arrow being the thing that's noisy does point to it being a toolkit deficiency, nothing directly to do with your setup. I'm guessing the problem is actually that the affected apps use an older version of GTK (the toolkit most often used for Gnome apps). If it's an old GTK, it's probably introducing a scaling error. https://openlib.io/toolkits-and-gnome-wayland-gtk-qt-in-linux/ https://unix.stackexchange.com/questions/433040/how-to-tell-what-gtk-and-qt-toolkits-your-applications-are-using > > LIS, switching the new monitor to 60 Hz resolved the noise issue. Yeah, makes the display server not have to work as hard. > > KM> I just tried two monitors on the Fedora box, works fine, after > KM> some thrashing around to figure out that you really do have to > KM> designate a primary or it'll just put up a random login screen > KM> background and nothing else. > > I've not done that: here the computer desk is a corner-style and has a > hutch on it (used to house a CRT). One monitor in there, the other > monitor is on the wall to the right. I can't do the usual side-by-side > but do slide off to it the documents and projects on hold. I have Silver (XP64) set up that way. I need to figure out how to get both monitors to be available to Zombie too (Win11). The linux side of the room already had two monitors because the KVM liked the PCs on the table but wasn't speaking to the PCs on the floor, so they got their own. But I hadn't tried dual monitors on a single linux box before. Unless you count the Huion display tablet, which is basically a touchscreen repeater that can be plugged into a USB port. > > Duuuude! When I scroll my messages I don't want smearing! > > Yes, using the 60 Hz refresh rate seems more than adequate. > KM> Modern monitors are more than equal to a BBS's scrolling text!! > > Probably always have been. ...I don't recall the model number but was > part of the Sanders Associates 720; the text character was written out > sort of like cursive as one continous line. Think how a neon sign has > its glass tube bent to create the letters. (Usual method is multiple > straight traces to create the letter.) Woah, that is cool. Not very practical, but cool. þ RNET 2.10U: ILink: Techware BBS þ Hollywood, Ca þ www.techware2k.com --- QScan/PCB v1.20a / 01-0462 * Origin: ILink: CFBBS | cfbbs.no-ip.com (454:1/1) .