Slink upgrade messed up X configs
I recently pointed dselect to slink in order to upgrade. I picked through
all the packages and everything and got it all to install properly, but
when I was done, X would not work properly. It would start the server and
an xterm fine, but it stopped there and refused to start KDE. However, it
would start kde fine if I went to the xterm and started it by hand. So I
went to /etc/X11 and started checking things out. It turns out that
/etc/X11/xinit contained three things: a symlink called xinitrc which
pointed to /etc/X11/xinit/xinitrc (which doesn't exist), another symlink
called xserverrc which pointed to /etc/X11/xinit/xserverrc, and a file
called xinitrc.dpkg-new. So I changed the xinitrc symlink to point to
xinitrc.dpkg-new and that fixed the KDE not starting problem. I also had
to fix a similar situation in /etc/X11/xserver with the file
SecurityPolicy. My questions are these: Why did dpkg do this? It didn't
ask me if I wanted to overwrite files or anything, it just left it like
this automatically. What is /etc/X11/xinit/xserverrc supposed to point
to?
I also have another problem which is unrelated. For a long time now,
every once in a while when I exit X my virtual consoles get all messed up.
They have dots all over the place. Anyone have any idea why this happens?
I use the SVGA X Server with my Diamond Stealth 2000 4MB video card and
the K Desktop Environment.
Thanks,
Eric.
_____ _
| ____|(_) http://www.iit.edu/~jenseri
| _| | | Page me via ICQ at
| |___ | | http://wwp.mirabilis.com/19022931
|______/ | or by mailing 19022931@pager.mirabilis.com
|__/
Reply to: