Ubuntu
nvidia-common package

Cannot adjust fonts after enabling Nvidia proprietary driver

Bug #658967 reported by albert fishnets
This bug report is a duplicate of:  Bug #500417: nautilus doesn't honor gnome theme. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nvidia-common (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: nvidia-common

To reproduce have Nvidia gtx-250 card, enable 3d drivers and restart, try to adjust font sizes to different size or try to adjust font resolution. I cannot make my fonts bigger or smaller at all. They are all rendering at 9point with the exception of my window tital and desktop font. When I disable nvidia proprietary drivers problem is fixed, but I have no 3-d support. When I enable them it's back. I tried upgrading to the latest beta nvidia drivers but the exact same thing happens. I cannot get fonts to render in anything but the "Ubuntu" font at 9points. All my apps and menus are they same way. I can't read any of it.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: nvidia-common (not installed)
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
CheckboxSubmission: c6f706b407fa9155748548a12cd5a198
CheckboxSystem: edda5d4f616ca792bf437989cb597002
Date: Mon Oct 11 22:44:31 2010
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: nvidia-common

Revision history for this message
albert fishnets (mateolingerhaus) wrote :
Revision history for this message
albert fishnets (mateolingerhaus) wrote :

I may have just fixed this. I installed the latest nvidia driver and mstt fonts and mathematica fonts. During installation, synaptic froze and I had to hard reboot. Now the fonts work and themes are rendering properly. I'm going to reboot to see if it's persistent.

Revision history for this message
albert fishnets (mateolingerhaus) wrote :

So the fix was not persistent. I tried another approach and added myself to the video group and GDM group and made sure I had full permissions on everything. This seems to have worked for now. I want to try a few more reboots to see if it's persistent. If one of you respond to this soon, can you let me know what groups I should belong to? This bug may cause you to lose permission to access GDM or desktop rendering because of a ownership change. i will post again soon if this fix is persistent.

Revision history for this message
albert fishnets (mateolingerhaus) wrote :

Fail. It was persistent for two reboots, but the bug came back. I also noticed that I am not displaying my panels with the correct theme. My system theme indicates they should be black, but they are not. Maybe that helps.

Revision history for this message
albert fishnets (mateolingerhaus) wrote :

Looking into this Bug #652731 as he seems to be having similar problems. Also trying Bug #629910 solution to see if that helps.

Revision history for this message
albert fishnets (mateolingerhaus) wrote :

No dice. I think bug #652731 might still be related, but updating the nvidia drivers and reinstalling gnome and nautilus and using the rc kernel have not proven to be persistent. Their is clearly a permissions on configuration error somewhere, but i can't figure it out.

Revision history for this message
albert fishnets (mateolingerhaus) wrote :

Alright. Turns out my bug is a duplicate of Bug #649809. They also have 200 series nvidia GPU's with core i-7 processors. Please mark this as a duplicate.

Revision history for this message
albert fishnets (mateolingerhaus) wrote : Re: [Bug 658967] Re: Cannot adjust fonts after enabling Nvidia proprietary driver

Bug 500417 does not describe the same conditions.

1.) It happens on 10.04. 10.04 does not have this bug, In fact I
re-installed 10.04 because of this bug.

2.)They get it when they close or open certain windows or themes. We get it
wth SSD, Nvidia driver, and mostly core i7 processors when we *enable the
Nvidia proprietary driver*. There is no mention of this at all.

3.)Deleting the conf file they spoke of does not fix our problem. Only the
solution in #68 comments has worked thus far as a temporary solution.

On Fri, Nov 12, 2010 at 5:56 AM, bastafidli <email address hidden> wrote:

> *** This bug is a duplicate of bug 500417 ***
> https://bugs.launchpad.net/bugs/500417
>

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.