Page 1 of 1

How to fix the serious charset display corruption with Fresh

Posted: 30 December 2012, 20:56
by NicCo
This problem was reported here, for the first time, by Akiro >>> viewtopic.php?p=20550#p20550

I copy here his example screenshot
Image

Uploaded with ImageShack.us

The issue is the screenshot is shown in an intermediate phase, into my laptop installation, I could not read anything more... :evil: :twisted:

I have noticed the issue and I started to test everything in my installation, then I decided to install again Fresh in my laptop.
the problem after few hours started happening again...
This time my suspicts were all in the Xorg side or the Nvidia drivers, so I decided to do google search to find some confirms

The problem exists also in ArchiLinux > https://bbs.archlinux.org/viewtopic.php?pid=1195028
"If you see see some serious charset display corruption, generally this may be happen only with Nvidia proprietary drivers.
Often starts in firefox, where your have normal text and random larger letter that were not the correct letter for the word.
Other letters would be garbled or some other type of visually wrong display
But this affects Chromium, Skype, and also all GTK and QT programs, with time passing the issue become even more hard

and so:
It's the new pixman glyph cache, rebuilding the fontconfig cache seems solving the problem!

I've informed immediately ROSA devel, now in holidays, Kazancev answered me he'll try pushing ASAP
the solution in the fixed "pixman" rpm, adding in the his %post a little script executing this root command

Code: Select all

fc-cache -f -v
If you're suffering the problem, and you can not wait for the fix, I suggest You to do the same I did

I tried the first time by "user mode", then by "root user"

Code: Select all

[nicco@localhost ~]$ fc-cache -f -v

Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated.
/usr/share/fonts: caching, new cache contents: 0 fonts, 11 dirs
/usr/share/fonts/100dpi: caching, new cache contents: 332 fonts, 0 dirs
/usr/share/fonts/75dpi: caching, new cache contents: 358 fonts, 0 dirs
/usr/share/fonts/OTF: caching, new cache contents: 0 fonts, 0 dirs
/usr/share/fonts/Speedo: caching, new cache contents: 0 fonts, 0 dirs
/usr/share/fonts/TTF: caching, new cache contents: 0 fonts, 3 dirs
/usr/share/fonts/TTF/dejavu: caching, new cache contents: 21 fonts, 0 dirs
/usr/share/fonts/TTF/droid: caching, new cache contents: 8 fonts, 0 dirs
/usr/share/fonts/TTF/liberation: caching, new cache contents: 12 fonts, 0 dirs
/usr/share/fonts/Type1: caching, new cache contents: 9 fonts, 0 dirs
/usr/share/fonts/cyrillic: caching, new cache contents: 0 fonts, 0 dirs
/usr/share/fonts/default: caching, new cache contents: 0 fonts, 2 dirs
/usr/share/fonts/default/Type1: caching, new cache contents: 35 fonts, 1 dirs
/usr/share/fonts/default/Type1/adobestd35: caching, new cache contents: 35 fonts, 0 dirs
/usr/share/fonts/default/ghostscript: caching, new cache contents: 17 fonts, 0 dirs
/usr/share/fonts/encodings: caching, new cache contents: 0 fonts, 1 dirs
/usr/share/fonts/encodings/large: caching, new cache contents: 0 fonts, 0 dirs
/usr/share/fonts/misc: caching, new cache contents: 59 fonts, 0 dirs
/usr/share/fonts/ttf: caching, new cache contents: 0 fonts, 2 dirs
/usr/share/fonts/ttf/decoratives: caching, new cache contents: 29 fonts, 0 dirs
/usr/share/fonts/ttf/western: caching, new cache contents: 9 fonts, 0 dirs
/usr/lib/X11/fonts: skipping, no such directory
/usr/X11R6/lib/X11/fonts: skipping, no such directory
/opt/ttfonts: skipping, no such directory
/home/nicco/.local/share/fonts: skipping, no such directory
/home/nicco/.fonts: skipping, no such directory
/var/cache/fontconfig: not cleaning unwritable cache directory
/home/nicco/.fontconfig: cleaning cache directory
/home/nicco/.cache/fontconfig: not cleaning non-existent cache directory
fc-cache: succeeded
[nicco@localhost ~]$

first warning suggested me that it's better to execute it from /root user, so I repeated

[root@localhost ~]# fc-cache -f -v

/usr/share/fonts: caching, new cache contents: 0 fonts, 11 dirs
/usr/share/fonts/100dpi: caching, new cache contents: 332 fonts, 0 dirs
/usr/share/fonts/75dpi: caching, new cache contents: 358 fonts, 0 dirs
/usr/share/fonts/OTF: caching, new cache contents: 0 fonts, 0 dirs
/usr/share/fonts/Speedo: caching, new cache contents: 0 fonts, 0 dirs
/usr/share/fonts/TTF: caching, new cache contents: 0 fonts, 3 dirs
/usr/share/fonts/TTF/dejavu: caching, new cache contents: 21 fonts, 0 dirs
/usr/share/fonts/TTF/droid: caching, new cache contents: 8 fonts, 0 dirs
/usr/share/fonts/TTF/liberation: caching, new cache contents: 12 fonts, 0 dirs
/usr/share/fonts/Type1: caching, new cache contents: 9 fonts, 0 dirs
/usr/share/fonts/cyrillic: caching, new cache contents: 0 fonts, 0 dirs
/usr/share/fonts/default: caching, new cache contents: 0 fonts, 2 dirs
/usr/share/fonts/default/Type1: caching, new cache contents: 35 fonts, 1 dirs
/usr/share/fonts/default/Type1/adobestd35: caching, new cache contents: 35 fonts, 0 dirs
/usr/share/fonts/default/ghostscript: caching, new cache contents: 17 fonts, 0 dirs
/usr/share/fonts/encodings: caching, new cache contents: 0 fonts, 1 dirs
/usr/share/fonts/encodings/large: caching, new cache contents: 0 fonts, 0 dirs
/usr/share/fonts/misc: caching, new cache contents: 59 fonts, 0 dirs
/usr/share/fonts/ttf: caching, new cache contents: 0 fonts, 2 dirs
/usr/share/fonts/ttf/decoratives: caching, new cache contents: 29 fonts, 0 dirs
/usr/share/fonts/ttf/western: caching, new cache contents: 9 fonts, 0 dirs
/usr/lib/X11/fonts: skipping, no such directory
/usr/X11R6/lib/X11/fonts: skipping, no such directory
/opt/ttfonts: skipping, no such directory
/root/.local/share/fonts: skipping, no such directory
/root/.fonts: skipping, no such directory
/var/cache/fontconfig: cleaning cache directory
/root/.fontconfig: not cleaning non-existent cache directory
/root/.cache/fontconfig: not cleaning non-existent cache directory
fc-cache: succeeded
[root@localhost ~]# 
Now the problem in my Laptop has disappeared, so this seems really solving, so long so far ;) :D

bye, NicCo

Re: How to fix the serious charset display corruption with F

Posted: 31 December 2012, 10:52
by NicCo
Yesterday, after many hours of continuous use of the PC, including some reboots, everything worked fine,
this morning after about one hour of browsing with Firefox, reading around a bit, the nightmare returns...

immagine ridotta %

therefore, it seems that the error is still here, and although it is now much more rare and does not happen in the title of windows,
and occurs only in rare and limited tab, whereas before it was very frequent and omnipresent, unfortunately the error is still here

Certainly needed to review something in Xorg, Nvidia or pixman


Hello, Nicco

Re: How to fix the serious charset display corruption with F

Posted: 31 December 2012, 11:27
by azioga
maybe Depardieu is the culprit ;-)

why don't you try a nvidia driver downgrade to exclude latest driver responsibility?

Re: How to fix the serious charset display corruption with F

Posted: 31 December 2012, 11:40
by NicCo
Depardieu started the first wrong page I saw :lol:

In the Archilinux forum, someone is saying
304.64 is the worst driver ever released by nvidia.
I started fearing he's right

I dont find anymore previous nvidia long-lived rpms (304.60?) in ABF


I've found some Archilinux discussions about the issue

Problem with font rendering: Random characters or font styles.
https://bbs.archlinux.org/viewtopic.php?id=152837

[Solved] NVIDIA artefacts on text while browsing web
https://bbs.archlinux.org/viewtopic.php?id=153890

Re: How to fix the serious charset display corruption with F

Posted: 31 December 2012, 14:45
by rjadot
It seems to be working for me, thanks a lot !! Maybe Depardieu should go to Italia rather than Belgium :mrgreen:

Re: How to fix the serious charset display corruption with F

Posted: 3 January 2013, 1:44
by benbullard79
Which solution did Y'all use? Downgrading xorg packages or rebuilding xserver?

Re: How to fix the serious charset display corruption with F

Posted: 3 January 2013, 10:46
by NicCo
Now we are waiting ROSA developers to come back from Holidays:
we verified these problems that are very widespread and important...

- Nuveau are not usable, for the reasons the most times the display resolution are wrong detected and can't be overrided
- Nvidia proprietary drivers, the long lived R300 but also the -current R310, suffer the problem with severe text corruption

In the meanwhile:

MIB started a different and full optimized X13 port
did not see the topic?

Xorg 13 port, full enabled, for ROSA Desktop.Fresh 2012
viewtopic.php?f=38&t=3691


if you want know some more about, description text now is only in italian, but you can use an online translator

The porting is not complete, now are ready the core parts:
drm, mesa, pixman, ecc
This will be an advanced port with all features full enabled

You can use that Topic for your feedback about the project,
we need help with testing and suggestions


bye, NicCo

Re: How to fix the serious charset display corruption with F

Posted: 4 January 2013, 0:30
by benbullard79
Thanks for the information. I had missed that thread and it is something I've been looking for.