HAs anyone else had problems with the KDE packages that came with 7?

Its seems quite shitty in the stability aspect compared to the LDE in
6.0.  I originally started using KDE 'cause gnome was instable back
then...  I never had a problem with KDE in 6.0

KFM can no longer go into .tgz's and display contents.  It just has a
bunch of folders that don't really exist.  I really miss being able to
read a text file inside a .tgz with only a few mouse clicks.  Even the
Archiver program sucks for this now too.  It'l display the contents of
the archive, but you can't read a file...it just gives an error saying
the file doesn't exist.

aKtion doesn't play all the same movies that the previous version.  KPM
doesn't display my swap.  Kpackage doesn't prompt for the root passwd
anymore when needed, but this is prob just a security thing and may be
possible to set it up that way still.


***** REAL PROBLEM STARTS HERE! *****

I've also had serious problems with windows not being able to connect to
the display.  I don't think this is the server, 'cause I've tried 3
different ones!  The bundled 3.3.6, the bundled 3.3.5 for 3dfx, and the
slightly-newer 3.3.5 on the 3dfx website.  I went back to 3.3.6 SVGA
because the server on 3dfx's site was SVGA too...

Left screen locked overnight, came back today to kpanel gone. Started
kpanel in terminal and logged into internet. Tried to start netscape
couldnt connect to display.  Trying to open other windows told me KFM
wasn't running.  I decided to start keeping track of all this to help
find the problem.  I tried starting it at the prompt, as you can see
here:

ERROR: KFM is not running
KFM NOT READY
ERROR: KFM is not running
KFM NOT READY
ERROR: KFM is not running
KFM NOT READY
 
[jeremy@fdialup185 jeremy]$ kfm&
[2] 6801
[jeremy@fdialup185 jeremy]$ Xlib: connection to ":0.0" refused by server
Xlib: Client is not authorized to connect to Server
kfm: cannot connect to X server :0
 
[2]+  Exit 1                  kfm
[jeremy@fdialup185 jeremy]$ cat
>xerrorlog                                      
---------------------------------------------

These are the errors displayed in the virtual console window where I
started x windows in:

AUDIT: Wed Mar 15 18:29:21 2000: 1709 X: client 17 rejected from local
host
Xlib: connection to ":0.0" refused by server
Xlib: Client is not authorized to connect to Server
Error: Can't open display: :0
AUDIT: Wed Mar 15 18:29:55 2000: 1709 X: client 17 rejected from local
host


[1]+  Stopped                 startx
[jeremy@localhost jeremy]$ cat >>xerrorlog
 ----------------------------------

I had to restart xwindows.  I shouldn't be having to do this.

I've had this probelm a few times now, usually when trying to open
netscape.  But not always is it netscape that screws everything up.  I
hate having to restart x.

WTF is going on here?  Is this a KDE thing or what?  SOMEONE PLEASE HELP
BECAUSE THIS REALLY SUCKS!!!!!!!!!!!!!!!!

~Jeremy





One last gripe:

Why the @#$%$ is the .kderc created by default w/ root ownership in the
user's home directory AND NO WRITE ACCESS FOR THAT RESPECTIVE USER?!?! 
Now, I can see that if it were the system-wide one, but come on!  It
took a while to figure out why I couldn't change my @#$%@#$% colors! 
That was pure stupidity on someone at Mandrake's part...

Reply via email to