As you can see I dont get that error, you have to go to each of the directories the xorg.conf.new puts in and check that they are actually font directories and also check to see that you arent missing any directories that should be listed, this takes a little while but needs to be done, if you are getting an error message about a font directory that should actually be listed delete the font.dir in that folder and then run mkfontdir "name of folder" to regenerate it._________________Billy DeVincentis

@VinzC
That's the same problem i had. I could be logged in into kde for the whole day and nothing happens (as long as i didn't do anything). But when i tried to start k3b or only wanted to open the kde menu my whole system locked up and cpu was at 100%. But i also could watch my superkaramba updating it's display. I also could work in the kde-console but i couldn't start a program or do anything else (by the way the console was open so i think it doesn't need a lot of cpu)

The interesting part was that when i tried to enter the console (CTRL+ALT+1) i got a lot of strange symbols and icons like there was the rest of a buffer. i could "repair" it by restarting the consolefonts. So i thought the problem was with my graphics configuration because the console of linux doesn't have to something with kde or any other displaymanager.

Depends on how the screen looked like on your side but if you mean strange *text* symbols, I already had that thing when I had text and graphics terminals overlap; e.g. I had selected 6 TTYs but had forced X to start on the fifth console. I got garbage on TTY5 as soon as I closed my session IIRC; these were produced by keystrokes I made while attempting to logon again when I got to XDM logon window... The keystrokes were actually sent to the text console and I wondered why I couldn't log on the graphical terminal ..._________________Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
GNU/Linux user #369763

@billydv
Thanks for the reply.
But how can you see when a dir has to be listed?

I installed fluxbox this afternoon. It starts with the nvidia logo, and everything works fine until I close it. Then I get a lot of errors again, incl the one about the fonts.
I installed the full kde-meta, can I use these programs in fluxbox? Otherwise I use fluxbox instead of kde so I can use internet...
(really difficult to solve this for me. I started the gui instal of gentoo 2007 but it didn't function. A lot of people advised me to do the commandline install. So now here I am... )
Thanks for helping me!

I am having similar problems, so will add my 'this didn't fix it' list

Recompiled nvidia-drivers (arch and ~arch), mesa, xorg-*, kde-base/* (yes all of it)
Turned of any GLX apps, turned off any experimental options in xorg.conf, turned off any DPMS settings
Switched to GDM, then back to KDM

I keep getting literally hundreds of lines of

Code:

SetClientVersion: 0 9

in my /var/log/Xorg.0.log

I am just about to mask xorg-x11-7.2 and build a new kernel, if it works I'll get back to you.....

Edit: no it didn't, I'll give it till Monday for some updates to 3.5.7, then I'll drop back to 3.5.5, it isn't that much more bling._________________Current Project Thread (myth2avi)

Edit: no it didn't, I'll give it till Monday for some updates to 3.5.7, then I'll drop back to 3.5.5, it isn't that much more bling.

If you have the same problem as me, you don't need to revert. I've used the new KDE 3.5.7 with a new user (blank profile) and it works. So the problem is "just" about KDE config files... The trick is to find which one(s)!_________________Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
GNU/Linux user #369763

@VinzC
I don't think that it is a tty problem as you described because i only have the strange symbols and letters after my xorg locked up. So the only way to read and kill kde was to run a ssh session from another pc. In the ssh session everything was alright so i knew that it was the graphic card.

I think that in kde 3.5.6 and 3.5.7 there are changes with the xorg connection. A friend of mine updated his computer and doesn't have the problems so i think there are only problems with the xorg.conf and perhaps some kde config files but if you delete .kde folder in your home directory and the problem still occurs than i think it has to be the xorg.conf.

If you have the same problem as me, you don't need to revert. I've used the new KDE 3.5.7 with a new user (blank profile) and it works.

I tried a blank profile and it still locked up. I did also try a new xorg.conf, only very small changes to the original, but it seems good so far. I have just switched back to 'eselect opengl set nvidia' from xorg, I'll know by the AM. . . ._________________Current Project Thread (myth2avi)

I tried a blank profile this morning but after trying it I went into control center to customize a bit, low and behold it works and when I got back this afternoon I sis not have any kind of lockup at all, its too soon to tell but this may be the answer because when I started out on my abit I had the same problem, small freezing issues and I remember my profile got screwed up and I had to start a new one, I remember that that was the time that the problem seemed to go away._________________Billy DeVincentis

Now I went a step further, having seen that the new profile didnt cause any delays getting back to my desktop, I went ahead and reset everything to where it was befor with the new profile, I am going to test it overnight but it looks real promising so far since there is a huge chnage for the better in the time it takes kde to login and logout._________________Billy DeVincentis

Vinzc, are you telling me that a blank kde profile stopped the freezing problem coming back from screensaver?

In my case, yes, it did. But it was not quite a freezing problem, just X eating up CPU - my system was still reactive. This could mean my problem might not be the same as the one you have, I don't know. It looks like X locking can have many causes and not necessarily the same ones for everybody._________________Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
GNU/Linux user #369763

Vinzc, I just let kde run allnight with compiz fusion with a new profile completely configured to the same settings I had before, it worked, kde came right back after going out of the screensaver, I am now testing this same theory on my debian amd64 to see if this will be the same_________________Billy DeVincentis

i will try that since the problem happens when coming back from a sleep (suspend)

ps:currently im using nvidia 100.14.11

I'm currently using these drivers on a stable machine. So the problem might be somewhere else. Please give more info about your hardware/config files._________________Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
GNU/Linux user #369763

I have had the same problem for some time and tried all the suggestions in the thread but to no avail.

However, I changed my window decoration from Plastik to Keramic earlier today and so far everything seems to be back to its usual snappy, stable self. Early days yet and I'll update if anything changes.

I really need to get things going. I use my machine for work, and I'm afraid I'm gonna have to switch to Ubuntu if this isn't resolved before the weekend is up._________________"What stands in the way becomes the way." -- Marcus Aurelius

Right, my problems (highlighted earlier in this thread) that were unsolved by using a blank .kde template (that seemed to help some people) seem to now be resolved.

The last 3 things I did that have solved the problem were:
revert to arch from ~arch (left over from beryl testing) on media-libs/mesa
stopped running SuperKaramba (I'll start this again soon, but 7 days isn't 'stable' yet)
updated some overlays and rebuilt the qtcurve and the 'Crystal window decoration' themes << for some reason, in my mind this was the prime suspect, but that doesn't fit with the new ~/.kde not working so...

I post this in the vain hope it may save someone else some time, and in 14 days if it still works 3.5.7 will go on the rest of the machines in the house._________________Current Project Thread (myth2avi)

Problem definitely solved for me but what's causing the problem is still unknown. Here's what I did:

Backed up my .kde/ directory

Erased ~/.kde/ directory (plus the symlink) and ~/.kderc.

Opened a KDE session as usual then closed it (doing that creates a new KDE profile directory, .kde/)

Restored config files from backed up kde/share/config and program data from backed up kde/share/apps, e.g. kicker, ksysguard, superkaramba, kmail. I only restored kdesktoprc from the config directory, leaving everything from Konqueror.

Hope this helps.

EDIT: After all, problem definitely UNSOLVED with my profile !

The problem is back after I copied several config files. Sure it's *not* because of rdesktop configuration file because I still got X consume 100% CPU without. Still investigating. Step by step this time.

That sucks..._________________Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
GNU/Linux user #369763

Last edited by VinzC on Sat Sep 01, 2007 4:14 pm; edited 1 time in total

in your /usr/local/bin create a text file called compiz-fusion and make it executable, insert the following text

#!/bin/bash
# Compiz manager
# Copyright (c) 2007 Kristian LyngstÃ¸l <kristian@bohemians.org>
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
#
#
# Much of this code is based on Beryl code, also licensed under the GPL.
# This script will detect what options we need to pass to compiz to get it
# started, read a simple configuration file, and start a default
# plugin and possibly window decorator.
# All of this should be possible to override in a configuration file.

#########################################################################
# You should NOT edit this, edit the configuration file instead. #
# This is left for completness and if you need to modify the script. #
# The generated configuration file should be equally documented. #
#########################################################################

# Defaults
# Configuration file is based on XDG base dir. Set this to override the
# defaults. Leave empty if in doubt. Use -v to see exactly what
# configuration files compiz-manager looks for on your system.
#CONFIG="./compiz-managerrc"

# Set to yes to enable verbose (-v) by default.
VERBOSE="no"

# Default arguments. Others are added to this, and the configuration can
# override ALL arguments.
ARGS="--sm-disable --replace"

####
# Configuration handeling
# We attempt to follow the XDG basedir spec here;
# We can read both a global config, and a local one.
# The configuration file is extremly simple, as it's just a bash script.
# It might be a good idea to improve that a bit, specially with security
# in mind, an general errors.

And now unmerge nvidia-drivers, YES UNMERGE it first and then emerge the newest drivers

As for your compiz-settings, dont change anything, I have only changed a couple of things as far as effects and random animations, dont change the sync to vblank or unredirect full screen windows as this seemed to cause problems

as far as a screensaver, dont use kde, use xscreensaver and set it to electric sheep, for whatever reason electric sheep doesnt create problems when returning to desktop after screensaver mode, you should read about electric sheep and download sheep packs to get it working right away otherwise you may have problems.

I will inform if this continues to work in a couple of days_________________Billy DeVincentis