Bad Text Under KDE And C7

Home » CentOS » Bad Text Under KDE And C7
CentOS 26 Comments

I recently installed C7 from a C7+gnome CD. Gnome was awful enough that I promptly installed KDE.

KDE is not doing so well either. Text in text editors invoked by “opening” a file is flakey at best. E.g. pieces disappear and duplicate. Terminals seem ok, including vim invoked from the terminal. Firefox text seems ok. The sidebar text in file-browser windows often has “black tape” over it, usually completely covering text. The file names are ok.

Suggestions on how to dignose this?

26 thoughts on - Bad Text Under KDE And C7

  • I wrote too soon. Some of the file names are also getting the black tape treatment.

  • In other words, a video driver that almost works. I expect the first things to do are discover what video card and video driver I have. Is there a link to what to do next?

    BTW I probably will not be able to get back to this until tomorrow.

  • The i915 driver is fairly rock solid – virtually all desktop machines these days have on-board Intel video, it’s the lowest common denominator. And your chipset is not exactly cutting edge stuff.

    Are there any errors in the logs – either kernel logs or X logs?

    For some reason you say you disliked Gnome – but does Gnome show issues
    (they use the same video driver)?

    A long shot is the theme. Are you using some non-standard theme on your desktop?

    Finally, do you have a spare graphics card you could try in the machine? (This is just to make sure there’s no hardware problem.)

    P.

  • If it is to just get better font rendering (infinality freetype rendering);
    have a look at this gist:

    https://gist.github.com/sunnz/11cd72135a0d6a3ec6b6

    it requires the installation of some packages from non fedault repos such as nux-desktop and sets up a new fonts.conf file.

    However, once used, it is impossible to work on a RHEL 7 type system without this installed. Font rendering looks better than Windows and Ubuntu.

    —–Original Message—

  • I bought it used.

    I’m not seeing anything that seems very interesting. Xorg.0.log uses the phrase “falling back” a few times. I expect that just means I’ve not inerfered with defaults. boot.log-20180625 does not contain any of the sequences rap, RAP, ideo, IDEO. dmesg contains graphics and video, but nothing that seems interesting.

    I’ll try it.

    What is a theme?

    Only as a last resort. Having already lost a couple graphics cards (not in this machine), I open the case rarely and with fear and trepidation.

    When I hover over text, the black tape effect goes away. Do graphics cards know about text or hovering?

  • No, neither gnome nor gnome-classic. One of them, I think it was gnome-classic, did videos badly. It was a bit like a shutter came about a quarter way down at about once per second.

    Late for work.

  • It’s how the desktop looks – colours, icons, widgets that sort of thing. Complex themes have a “theme engine” underneath that does a lot of the hard work of drawing things on the screen

    Not really. But hardware issues may affect the rendering of some things.

    P.

  • Hmm, that is usually symptomatic of slow graphics card, but the Intel graphics chip set should be perfectly OK.

    It may be that your particular combination of chipset and driver is manifesting a bug – or it might be bad hardware.

    Try booting a live distro – such as Fedora (other distros are available). It won’t affect your installed data, but it will provide a different driver to try.

    P.

  • The black tape has gone away for KDE also. Apparently logging out and in again fixed or obscured the problem.

    I’ll try the live CD suggested elsewhere.

    Again.

  • I meant to use a live DVD from some other distro so that it had differently compiled drivers – the idea was to eliminate (or otherwise)
    the drivers from CentOS 7.

    That’s mainly because they are non-free codecs so aren’t included by default.

    P.

  • I’ve been looking. I keep finding claims that Fedora live CD’s exist, but not actual images.

    I did find a C6 live CD. No go. Without additional installs, it would not even try. After accepting its offers to install dragon and totem, it still would not play any videos.
    … not working falling back to default. The default was blank.

    To be clear:
    flv and avi caused it to complain about the lack of mp4 codecs.

    Is there something dragon or totem will play out of the box?

  • https://getfedora.org/

    specifically

    https://getfedora.org/en/workstation/download/

    What it actually does is to download Fedora Media Writer which when run downloads the correct image and writes it to a memory stick.

    Yes, because MPG codecs are not license free.

    Probably WebM and OGG video as they are both patent/license free. If you are looking for something try

    https://commons.wikimedia.org/wiki/File:Big_Buck_Bunny_Trailer_1080p.ogv

    (that’s an open source, royalty free movie using open codecs).

    P.

  • Won’t boot for me. I keep getting kernel panics and am real tired of the power button. I have to boot C6 with acpi=off, but that did not help.

    Something about sync, attempt to kill process 1, kernel panic.

    I’ll see whether I can find something else.

    I hadn’t realized flv and avi were synonyms for mpg.

    Thanks.

  • Check your hardware – all these things might well be symptomatic of an hardware issue.

    They’re not. flv and avi are containers, mpg is an encoding method that can be used in those containers.

    P.

  • Michael Hennebry wrote:

    They’re not. Those are two *different* vidao/audio file formats. Each one needs its own codec. I like mplayer.

    mark

  • I’m not at all sure how. If it means opening the case, hardware issues are likely to occur.

    Is there a way to tell whether the video player is even using video acceleration?

  • I don’t necessarily mean the video – kernel panics are rarely to do with something that far removed from the CPU. I mean test the hardware of your computer.

    First, check the memory – MemTest86+ is the tool most people use for this. Run it on your system and it will highlight memory problems. It can be found at http://www.memtest.org – the precompiled versions are tiny and will fit on a floppy (or memory stick or CD).

    If that doesn’t detect anything try running a hardware diagnostic –
    there’s a load on the UBCD (www.ultimatebootcd.com) or Hiren’s BootCD (
    http://www.hiren.info). You might want to download one of those anyway as they both contain MemTest86+.

    None of this needs you to open the case.

    P.

  • I’ll do the testing suggested. The machine is rather old. HP Compaq dc5800 sff (small form factor)
    I would not be surprised if the kernel just did not like my motherboard any more.

    Even after I figure out the kermal panics, the video will still be an issue.

    That is good.

    My suspicion is that this is a repeat of what sent me to CentOS from Fedora.
    (Yes I know the relationship). I’m told I couldn’t install Fedora on a machine because a kernel bug affected precisely one kind of motherboard, mine. I’m also told the bug was supposedly fixed, but I was never able to run any later Fedora on that machine.

  • It is very rare that old motherboards (or rather chipsets) stop being supported – I have CentOS 7 running on 10, 15 yr old kit. You get a lot more problems with new motherboards than you get with old ones.

    They may well be linked.

    You never mentioned that you had previously had issues with Fedora on the machine – not even when I suggested you run a Live version of Fedora to provide different drivers. Not even when you got kernel panics when booting the live Fedora did you mention this was a known issue.

    P.

  • A machine, a now-defuct DakTech machine that I bought new. My current machine is an HP that I bought used. Did not mean to confuse.

  • Ran MemTest86+. While I was deciding what to tell it, it started in upiprocesor mode.

    After reading about kernel option, tried C7 LIve again. Got panic again. Tried again with nosync. Gpt panic again. What got C7 to boot was acpi=off and nosmp.

    Tried to play the Big Bunny file. Got fullscreen mode, the first and last images and audio. No complaints. Eventaully figured out how to get it out of fullscreen mode. Big Bunny played without the shutter effect.

    The next thing on my list is to try MemTest86+ with SMP.