You are not logged in.
Do you think they will ever find a way out to get nvidia-304xx and xorg-server working together?
Two things: One, the new pixman glyph cache is an experimental feature no one but Arch is using yet. The Arch devs backported a patch from git to enable it, kinda going against the Arch philosophy of sticking to upstream and not patching stuff. And two, has anyone made nvidia aware of this? Looking at the forums, it doesn't appear that way.
Offline
Bad news.
Seems like nvidia-310.19 fixed the problem only partially, f.e.:
- gajim: fixed
- linuxdcpp: fixed AFAIR
- deluge: problem persisted for column names in the main window's list of torrents, but gone for torrent info
- xchat: problem persisted
Downgraded xorg-server package.
Offline
no one but Arch is using yet.
I think it's in the Mageia 3 alphas also - it's been in Mageia Cauldron (e.g. x11-server-1.13.0-7.mga3.src.rpm) for a while, as use-new-pixman-api.diff.
Edit: It may be relevant that Mageia's cairo is not compiled with --disable-xlib-xcb
Last edited by brebs (2012-11-22 17:18:31)
Offline
I had an issue with gnome-terminal where characters were being replaced with other characters. So for example if I typed 'n' it would appear as an 'l'. If I maximized then minimized the terminal it would correct itself, but then if I typed anything it would revert back to the wrong characters. Since updating yesterday I haven't seen it happen again. Using nvidia on a GTX460.
Offline
I was puzzled by this weird problem until I found that moving to nouveau fixes this for me.
(7600GS, not for gaming)
Offline
Some things to try, for people with random chars:
1. Upgrade to harfbuzz 0.9.7, pango 1.32.3
2. Recreate the fontconfig cache:
fc-cache -r
(Will take a couple of minutes, to scan the fonts.)
Offline
I tried nouveau for a while (and it seems pretty good, enemy-territory still playable), but then X is unusable after resuming from suspend, so I just switched back to nvidia-304xx. So far (one, maybe two hours) I have not had any glyph issues, so I am hopeful. Pacman log shows that harfbuzz was upgraded in the meantime (0.9.5-2 -> 0.9.6-1, so not version 0.9.7 suggested by brebs).
Edit: issues not completely gone.
Last edited by Raynman (2012-11-25 13:43:31)
Offline
I had an issue with gnome-terminal where characters were being replaced with other characters. So for example if I typed 'n' it would appear as an 'l'. If I maximized then minimized the terminal it would correct itself, but then if I typed anything it would revert back to the wrong characters. Since updating yesterday I haven't seen it happen again. Using nvidia on a GTX460.
Nevermind, just had the issue again. Bold characters in my terminal are garbled and as I type this there are weird characters in firefox. http://i.imgur.com/wkWfx.png (down at the bottom)
Offline
harfbuzz 0.9.7 & pango 1.32.3 are in [extra].
After upgrade I ran
fc-cache -r
(which took mere seconds, btw) and the problem seems to be solved.
Offline
Disabling xrender might be a suitable workaround:
Section "Extensions"
Option "RENDER" "Disable"
EndSection
Offline
Hopefully that patch is safe to use again, with nvidia 313.18
Fixed font rendering performance and corruption problems on X servers with backported support for the new glyph cache functionality added to Pixman 0.27.
Offline
Am I the only one still suffering with this?
using:
extra/nvidia 313.30-5
extra/pixman 0.28.2-1
extra/xorg-server 1.14.1-1
Offline