On Mon, 2003-02-17 at 11:43, John Noll wrote: > > > > You must be root to install/remove rpms. You can read the rpm db as a > > normal user, but you can't write to it. > > > > Thanks for the quick response. One more question. What does the > following mean and why I am I getting this output. Can I fix it?
That should probably be response_s_ since a number of people jumped on this one. ;-) > [root@localhost apt]# gedit > > (gedit:1131): GnomeUI-WARNING **: While connecting to session manager: > Authentication Rejected, reason : None of the authentication protocols > specified are supported and host-based authentication failed. > [root@localhost apt]# Let me guess, you did an "su" instead of an "su -". That's generally a bad habit. When you leave off the dash you don't read root's .profile, leaving you with the incorrect environment for that users. There are reasons to leave of the dash, but most of the time you should include it. Simply including the dash should work. However, on systems that are more tightly locked down that will prevent you from running X applications. X includes support for "sessions," ie. when you log out you can save your session and restore it when you log back in. For example, if you like to always have three terminal windows open when you log in, open three terminals, logout (check save session), and when you log back in those three terminals will be open again. This must be supported by the application. More advanced programs can even restore state like open files, etc. To make supporting sessions easier, gnome includes an abstraction and services to compliant applications. To prevent other users from modifying your environment, it must include security checks. When gedit, a compliant application, starts it notices a running gnome session manager and kindly tries contact it for you. Because you didn't change roots environment, however, its seeing a session manager that doesn't want to talk to it. You're running session manager is only interested in recieving request from user "john" so gedit reports that the session manager refuses to talk to it. No big deal, generally you can just ignore the message. -- Stuart Jansen <[EMAIL PROTECTED]> #define FALSE 0 /* This is the naked Truth */ #define TRUE 1 /* and this is the Light */ -- mailto.c _______________________________________________ newbies mailing list [EMAIL PROTECTED] http://phantom.byu.edu/cgi-bin/mailman/listinfo/newbies
