On Monday 09 August 2004 12:30 pm, Charlie Mahan wrote:
> On Sunday 08 August 2004 21:52:09, Julie Sloan wrote:
>
>
> That was my fault. When I install a system one of the first things
> I do is change the display manager from mdkkdm to kdm. 

don't tell me how - maybe I'll find it on my own  :)  (like I don't 
have enough "finding" to do already LOL)
 
>  At the login screen if there's no "menu"
> button just use the Ctrl+Alt+Back Space method to restart the X
> Server.
>
> If you find yourself at a black screen with text and a flashing
> cursor beside the word login type your user name, strike the Enter
> key and supply your user password at the next prompt then strike
> Enter again. That will place you in your home directory with a
> flashing cursor, type startx and strike the Enter key to resume
> graphical mode. Assuming X isn't broken of course.

Great! thanks.  wish I'd known about startx a month ago.  :P  
I found myself there and since I had never SET a pw I panicked & 
reinstalled.   And the installation discs wouldn't work the second 
time (wonder what thatwas about?) So I had to wait for new discs.  
Blah blah blah ancient history.  On to newer and better problems...

> > > Just for fun open a terminal when you're already in KDE and
> > > become super user then type
> > >
> > > kdeinit
> > >
> > > and strike the Enter key. Then try to open a directory.
> >
> > FUN?!?  I get this:
>
> <whack>
>
> You seem to have skipped the part of the instructions above that
> says; "..open a terminal when you're already in KDE and become
> super user.."
>
> It's difficult to know what terminology to use sometimes. I
> apologize.

no need

okay, here's:

# kdeinit
QPixmap: Cannot create a QPixmap when no GUI is being used
QPixmap: Cannot create a QPixmap when no GUI is being used
QPixmap: Cannot create a QPixmap when no GUI is being used
QPixmap: Cannot create a QPixmap when no GUI is being used
kbuildsycoca running...

> You seem to have either lost contact with the part of the display
> that manages the file management system or lost the connection
> that it's running on or lost permissions on those directories you
> are having trouble accessing. Did you do anything with any files
> or 'folders' in your user's space while running as super user?

it's possible but not likely.  I look in var logs to find out? 

> through you. But if I say you need to be in SU mode to run a
> command successfully it's because I know that method works.

okay okay lesson learned.  Don't be mad at me.    :)

> Good luck.
>
> Charlie

thanks for your help.    Right now I'm in command-line culture-shock, 
but luckily I don't have a deadline to get comfortable with it.

J
-- 




why linux?      because MS is to OS as AOL is to ISP.

____________________________________________________
Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com
____________________________________________________

Reply via email to