duane staggered into the Black Sun and said: > I just moved my / partition. I also made the changes to fstab and the > grub boot loader. I thought everything was OK, but now cannot start X. > X will start for root. I figure there is some problem with file or > directory permissions that got screwed. I can't figure out what. Interesting. Are /etc/passwd and /etc/group the same? > X Error of failed request: BadValue (integer parameter out of range > for operation) > Major opcode of failed request: 158 (RANDR) > Minor opcode of failed request: 2 (RRSetScreenConfig) Why is xrandr being called? That error shouldn't be fatal, but I've seen plenty of Weird Things happen when xrandr is called. Which version of which distro are you using? > startkde: Starting up... > DCOP aborting call from 'anonymous-6230' to 'kded' > startkde: Shutting down... This makes it look like a problem with KDE, not a problem with X. What happens if you log in using the "failsafe" session? If that works, one thing to try is to move your ~/.kde to ~/.kde.old while you're not logged in to KDE. Then a fresh KDE config dir will be created (and you can copy your settings back individually from ~/.kde.old/ until you find the problem). > I've forced the reinstallation of the xorg rpm's. I ran a ptrace on > the root and user startx processes -- they were the same except for > addressing and path search differences of course. What could be the > problem? Has anyone seen something like this before? I have seen bizarre and stupid things like this happen once, but then I'm running compiz-fusion on a Radeon card. Beta software = glitches. It's improving, sure, but there's no way I'd use it on a system that had to be stable. -- "Oh bother," said the Borg, "We've assimilated Pooh." --MHR on alt.fan.pratchett Matt G|There is no Darkness in Eternity/But only Light too dim for us to see