| AJackson 2007-11-21, 1:16 am |
| On Nov 19, 8:50 pm, Ant <ANT...@zimage.com> wrote:
> On 11/19/2007 11:41 AM PT, J.O. Aho typed:
>
>
> Thanks for trying. It's a crazy issue. I wonder if it is something
> really stupid and minor that causes this madness.
It usally are.
Some late sugestions...
You can try to reinstall packages. ( 'L' in aptitude interactive
mode)
aptitude reinstall kde
You can really clean out all files, even config files with purge ('_'
in aptitude interactive mode)
aptitude purge kde
If you try remove, you don't remove configuration files, and next time
you install the package, you get same configuration as last time. ('-'
in aptitude interactive mode)
aptitude remove kde
Two more usefull commands is 'M', which mark a package as a
dependensie on another package in interactive mode.
And '+' which install the package.
Commands reinstall/purge don't touch package that kde are dependent
on. You have to handle them one at a time. Easiest to do is by
running aptitude without any arguments. (aptitude has "window" stack
when running interactive, which you can 'pop away' or close the top
window with 'q')
Look at the hash-bang '#!' first line in scripted commands. It tells
you which shell that reads the commandos in the file.
If it is a line like '#! /bin/bash', it is bash. You could try this
command then.
bash -x startx
It will give you a trace of what the shell script is doing.
If you want to start a second graphical X11 server on another console,
try this.
startx -- :1
Then you will have on X11 session at Ctrl-Alt-F8 instead on Ctrl-Alt-
F7
> You can see thi issue discussions on KDE's mailing list with a KDE
> developer:http://lists.kde.org/?t=119527809700002&r=1&w=2(pretty
> long). Maybe you will get more ideas on what we tried so far. 
>
> I will keep following up in this newsgroup thread as well.
Please do, and good luck.
|