On 03/06/2012 11:27 PM, jdow wrote: > Then he needs to look at the ROOT account's .bashrc file to see what has > changed. It should have this in it: Well, maybe you'll not see it due to the messy thread. But, in his case corrupted = deleted. All fixed now.

Then he needs to look at the ROOT account's .bashrc file to see what has changed. It should have this in it:

On 06/03/12 07:03, suvayu ali wrote: > On Tue, Mar 6, 2012 at 12:30, Ed Greshko<Ed.Greshko(a)greshko.com> wrote: >> You said you have this.... >> >> bash-4.2# ls /etc/bashrc* >> /etc/bashrc /etc/bashrc~ /etc/bashrc.wrkng >> >> I don't know what /etc/bashrc~ since I don't have one on my system. >> Maybe move that to /tmp or something and try again? >> > Those are backup files from some editor, most likely emacs. It suggests > the OP has edited the /etc/bashrc at some point in the past. > >> I also note that "ll" doesn't seem to work. That is also troublesome >> since it would seem to indicate a problem with sourcing the files in >> /etc/profile.d. You do have a /etc/profile file? >> >> Another thing to try.... >> >> Move /etc/bashrc.wrkng back to /etc/bashrc and then "su -". You'll have >> the "bad" prompt. But then type ". /etc/bashrc" and see if there are >> any error messages. > I think all these problems are still related to the SELinux issue the OP > had earlier. Probably the relabel did not work completely. I would > suggest the OP to take a look at the permissions and the SELinux context > of the profile directories and rc files. > > This is how it should be: > > $ ls -lhd /etc/bash* /etc/profile* > -rw-r--r--. 1 root root 57K Sep 4 2011 /etc/bash_completion > drwxr-xr-x. 2 root root 4.0K Feb 28 14:30 /etc/bash_completion.d > -rw-r--r--. 1 root root 2.6K Aug 16 2011 /etc/bashrc > -rw-r--r--. 1 root root 1.8K Aug 16 2011 /etc/profile > drwxr-xr-x. 2 root root 4.0K Feb 27 10:09 /etc/profile.d [root@box9 ~]# ls -lhd /etc/bash* /etc/profile* -rw-r--r--. 1 root root 57K Sep 4 2011 /etc/bash_completion drwxr-xr-x. 2 root root 4.0K Feb 3 10:35 /etc/bash_completion.d -rw-r--r--. 1 root root 2.6K Mar 6 07:10 /etc/bashrc -rw-r--r--. 1 root root 2.6K Aug 16 2011 /etc/bashrc~ -rw-r--r--. 1 root root 2.6K Mar 6 05:30 /etc/bashrc.wrkng -rw-r--r--. 1 root root 1.8K Aug 16 2011 /etc/profile drwxr-xr-x. 2 root root 4.0K Mar 3 12:09 /etc/profile.d > > > $ ls -Zd /etc/bash* /etc/profile* > -rw-r--r--. root root system_u:object_r:etc_t:s0 /etc/bash_completion > drwxr-xr-x. root root system_u:object_r:etc_t:s0 /etc/bash_completion.d > -rw-r--r--. root root system_u:object_r:etc_t:s0 /etc/bashrc > -rw-r--r--. root root system_u:object_r:etc_t:s0 /etc/profile > drwxr-xr-x. root root system_u:object_r:bin_t:s0 /etc/profile.d [root@box9 ~]# ls -Zd /etc/bash* /etc/profile* -rw-r--r--. root root system_u:object_r:etc_t:s0 /etc/bash_completion drwxr-xr-x. root root system_u:object_r:etc_t:s0 /etc/bash_completion.d -rw-r--r--. root root unconfined_u:object_r:etc_t:s0 /etc/bashrc -rw-r--r--. root root system_u:object_r:etc_t:s0 /etc/bashrc~ -rw-r--r--. root root unconfined_u:object_r:etc_t:s0 /etc/bashrc.wrkng -rw-r--r--. root root system_u:object_r:etc_t:s0 /etc/profile drwxr-xr-x. root root system_u:object_r:bin_t:s0 /etc/profile.d > > # ls -lh /root/.bash* > -rw-------. 1 root root 32K Mar 4 22:55 /root/.bash_history > -rw-r--r--. 1 root root 24 Aug 10 2011 /root/.bash_logout > -rw-r--r--. 1 root root 404 Feb 19 18:11 /root/.bash_profile > -rw-r--r--. 1 root root 2.1K Mar 4 22:57 /root/.bashrc [root@box9 ~]# ls -lh /root/.bash* -rw-------. 1 root root 927 Mar 6 07:13 /root/.bash_history > > # ls -Z /root/.bash* > -rw-------. root root system_u:object_r:admin_home_t:s0 /root/.bash_history > -rw-r--r--. root root system_u:object_r:admin_home_t:s0 /root/.bash_logout > -rw-r--r--. root root system_u:object_r:admin_home_t:s0 /root/.bash_profile > -rw-r--r--. root root system_u:object_r:admin_home_t:s0 /root/.bashrc [root@box9 ~]# ls -Z /root/.bash* -rw-------. root root system_u:object_r:admin_home_t:s0 /root/.bash_history > > GL > All I've done here is listed the files you suggested, not sure what the results mean ... Bob

On 2012/03/06 01:49, Bob Goodwin wrote: > [ "$PS1" = "\\s-\\v\\\$ " ] && PS1="[\u@\h \W]\\$ " Bob, it's this line. Find it by looking for the line below it: shopt -s checkwinsize Your /etc/bashrc file is not getting run in the case you cite, using an unadorned "su" to get to root privileges but not root configuration. So you've intentionally or unintentionally done something which prevents /etc/bashrc from getting run during the configuration phase just after entering the root password for "su". So far nobody else seems to be saying "me too". So my conclusion is that something you did messed it up. This is a maze of twisty little passages. It may be hard to figure it out.

The tentative obvious solution is to not use "su". Instead make it a proper login shell using "su -". (I'm not sure there's a good case to use "su" alone, ever. You generally use su to get a shell that behaves like a root shell with all the root utilities available without having to use full path names.)

{^_^}

[ "$PS1" = "\\s-\\v\\\$ " ] && PS1="[\u@\h \W]\\$ "

On Tue, Mar 6, 2012 at 12:30, Ed Greshko<Ed.Greshko(a)greshko.com> wrote: > You said you have this.... > > bash-4.2# ls /etc/bashrc* > /etc/bashrc /etc/bashrc~ /etc/bashrc.wrkng > > I don't know what /etc/bashrc~ since I don't have one on my system. > Maybe move that to /tmp or something and try again? > Those are backup files from some editor, most likely emacs. It suggests the OP has edited the /etc/bashrc at some point in the past. > I also note that "ll" doesn't seem to work. That is also troublesome > since it would seem to indicate a problem with sourcing the files in > /etc/profile.d. You do have a /etc/profile file? > > Another thing to try.... > > Move /etc/bashrc.wrkng back to /etc/bashrc and then "su -". You'll have > the "bad" prompt. But then type ". /etc/bashrc" and see if there are > any error messages. I think all these problems are still related to the SELinux issue the OP had earlier. Probably the relabel did not work completely. I would suggest the OP to take a look at the permissions and the SELinux context of the profile directories and rc files. This is how it should be: $ ls -lhd /etc/bash* /etc/profile* -rw-r--r--. 1 root root 57K Sep 4 2011 /etc/bash_completion drwxr-xr-x. 2 root root 4.0K Feb 28 14:30 /etc/bash_completion.d -rw-r--r--. 1 root root 2.6K Aug 16 2011 /etc/bashrc -rw-r--r--. 1 root root 1.8K Aug 16 2011 /etc/profile drwxr-xr-x. 2 root root 4.0K Feb 27 10:09 /etc/profile.d

$ ls -Zd /etc/bash* /etc/profile* -rw-r--r--. root root system_u:object_r:etc_t:s0 /etc/bash_completion drwxr-xr-x. root root system_u:object_r:etc_t:s0 /etc/bash_completion.d -rw-r--r--. root root system_u:object_r:etc_t:s0 /etc/bashrc -rw-r--r--. root root system_u:object_r:etc_t:s0 /etc/profile drwxr-xr-x. root root system_u:object_r:bin_t:s0 /etc/profile.d

# ls -lh /root/.bash* -rw-------. 1 root root 32K Mar 4 22:55 /root/.bash_history -rw-r--r--. 1 root root 24 Aug 10 2011 /root/.bash_logout -rw-r--r--. 1 root root 404 Feb 19 18:11 /root/.bash_profile -rw-r--r--. 1 root root 2.1K Mar 4 22:57 /root/.bashrc

# ls -Z /root/.bash* -rw-------. root root system_u:object_r:admin_home_t:s0 /root/.bash_history -rw-r--r--. root root system_u:object_r:admin_home_t:s0 /root/.bash_logout -rw-r--r--. root root system_u:object_r:admin_home_t:s0 /root/.bash_profile -rw-r--r--. root root system_u:object_r:admin_home_t:s0 /root/.bashrc

GL

You said you have this....       bash-4.2# ls /etc/bashrc*       /etc/bashrc  /etc/bashrc~  /etc/bashrc.wrkng I don't know what /etc/bashrc~ since I don't have one on my system. Maybe move that to /tmp or something and try again?

I also note that "ll" doesn't seem to work.  That is also troublesome since it would seem to indicate a problem with sourcing the files in /etc/profile.d.  You do have a /etc/profile file? Another thing to try.... Move /etc/bashrc.wrkng back to /etc/bashrc and then "su -".  You'll have the "bad" prompt.  But then type ". /etc/bashrc" and see if there are any error messages.

OK.... You have an unmodified ~/.bash_profile and a slightly different ~/.bashrc from my fresh install. The differences are not significant. The bottom line is that in ~/.bashrc you have if [ -f /etc/bashrc ]; then . /etc/bashrc Which should source the file. The place where the setting of PS1 takes place is here.... > # Turn on checkwinsize > shopt -s checkwinsize > [ "$PS1" = "\\s-\\v\\\$ " ]&& PS1="[\u@\h \W]\\$ " Basically it is saying.... if PS1 is set to '\s-\v\$ ' change it to '[\u@\h \W]\$ ' . So, it would seem, one of 2 things are going on. Either the file isn't being sourced or it isn't set as expected. What I would do is modify /etc/bashrc to .... shopt -s checkwinsize echo "PS1 is set to $PS1"> /tmp/huh [ "$PS1" = "\\s-\\v\\\$ " ]&& PS1="[\u@\h \W]\\$ " And then perform an su -.

On 03/06/2012 09:26 AM, Bob Goodwin wrote: > Why didn't I think of that? Because I'm trying to do too many > things at once, distractions here. > > "Bad" computer, "Good" prompt as user: > [bobg@box9 ~]$ set | grep ^PS > PS1='[\u@\h \W]\$ ' > PS2='> ' > PS4='+ ' > > Bad prompt as root: > [bobg@box9 ~]$ su > Password: > bash-4.2# set | grep ^PS > PS1='\s-\v\$ ' > PS2='> ' > PS4='+ ' > > It is different but where does it come from? The first question I would ask is do you have a .bash_profile or .bashrc file in root's home directory that has been modified?

Also, have you done anything to /etc/bashrc ?

I'm fairly certain that is where the change from PS1='\s-\v\$ ' to PS1='[\u@\h \W]\$ ' should take place. I wonder if it is even being sourced, based on the manner of other problems you've been reporting as of late.

On 2012/03/05 16:02, Bob Goodwin wrote: > On 05/03/12 18:55, Ed Greshko wrote: >> On 03/06/2012 07:50 AM, Bob Goodwin wrote: >>> "set|grep PS" Produces more data than I can deal with visually, >>> roughly two screens full ... >>> >> Then do >> >> set | grep ^PS >> > > From "good" computer ~ > > [bobg@box6 Downloads]$ set | grep ^PS > PS1='[\u@\h \W]\$ ' > PS2='> ' > PS4='+ ' > > > "Bad" computer ~ > > [bobg@box9 ~]$ set | grep ^PS > PS1='[\u@\h \W]\$ ' > PS2='> ' > PS4='+ ' Um, do it when you are getting that bash-4.2.5 prompt. It WILL be different or else it's time to scrub the hacker out of your system. {^_^}

On 05/03/12 17:07, jdow wrote: > What does "set|grep PS" return to you? PS1 is likely your ill component. When > you see the actual string it has you can search for that. The string probably > does not look like the default. I think the default is '[\u@\h \W]\$ ' with the > single quotes. > "set|grep PS" Produces more data than I can deal with visually, roughly two screens full ...

> Once you know the errant string you can look for it fairly easily if you > escape the backslashes. And with that in mind, bashrc has this string in it: > [ "$PS1" = "\\s-\\v\\\$ " ] && PS1="[\u@\h \W]\\$ " > > So it looks like you can expect to see that bash script under SOME conditions. > And reading that line leads me to suspect I need to look at "man bash". That > tells me this string is the default for a bash shell if nothing else sets the > prompt differently. > > Is your /etc/bashrc file still there? And if it is look for the reason it > skips that line. This is the context in my SL6.2 install. The significant > line is the third one up from the bottom of my clipping. > ===8<--- > if [ "$PS1" ]; then > case $TERM in > xterm*) > if [ -e /etc/sysconfig/bash-prompt-xterm ]; then > PROMPT_COMMAND=/etc/sysconfig/bash-prompt-xterm > else > PROMPT_COMMAND='echo -ne "\033]0;${USER}@${HOSTNAME%%.*}:${PWD/#$HOME/~}"; > echo -ne "\007"' > fi > ;; > screen) > if [ -e /etc/sysconfig/bash-prompt-screen ]; then > PROMPT_COMMAND=/etc/sysconfig/bash-prompt-screen > else > PROMPT_COMMAND='echo -ne "\033_${USER}@${HOSTNAME%%.*}:${PWD/#$HOME/~}"; echo > -ne "\033\\"' > fi > ;; > *) > [ -e /etc/sysconfig/bash-prompt-default ] && > PROMPT_COMMAND=/etc/sysconfig/bash-prompt-default > ;; > esac > # Turn on checkwinsize > shopt -s checkwinsize > [ "$PS1" = "\\s-\\v\\\$ " ] && PS1="[\u@\h \W]\\$ " > # setup mkd alias > alias mkd=". /usr/local/bin/mkd" > ===8<--- > > {^_^} These look identical to me ~ From box6 which works as expected: [ -e /etc/sysconfig/bash-prompt-default ] && PROMPT_COMMAND=/etc/sysconfig/bash-prompt-default From Box9 with the strange prompt: [ -e /etc/sysconfig/bash-prompt-default ] && PROMPT_COMMAND=/etc/sysconfig/bash-prompt-default

"set|grep PS" Produces more data than I can deal with visually, roughly two screens full ...

________________________________ From: Bob Goodwin <bobgoodwin(a)wildblue.net&gt; To: Fedora List <users(a)lists.fedoraproject.org&gt; Sent: Monday, March 5, 2012 9:39 AM Subject: Problem with su -       I have an F-16 computer that was working normally a couple of       days ago when run this morning has an unusual [to me] problem.       When I su and type in the root password form the XCFE desktop it       spends about 20 seconds before displaying a prompt and then       instead of:           [bobg@box6 ~]$ su           Password:           [root@box6 bobg]# exit       I get a prompt:  bash-4.2#       If instead of bringing up the desktop with startx I "su" it       changes to root quickly after entering the password, also with       the  prompt "bash-4.2#."       Other than that it apparently works? But obviously something has       changed and I can't guess what?       Bob -- users mailing list users(a)lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org

finally settled things seem to work normally except I still get that strange prompt "bash-4.2#" when it has always been "[root@box6 bobg]#."

On 05/03/12 10:49, David Quigley wrote: > On 03/05/2012 10:21, Bob Goodwin wrote: >> On 05/03/12 09:39, Bob Goodwin wrote: >>> I have an F-16 computer that was working normally a couple >>> of >>> days ago when run this morning has an unusual [to me] >>> problem. > > Would you mind running sealert -l > 90fc420a-dec9-47ce-afa5-6132c99ec61d and posting the output here so we > can see what the problem is? > [bobg@box9 ~]$ sealert -l 90fc420a-dec9-47ce-afa5-6132c99ec61d SELinux is preventing /usr/bin/xauth from write access on the None /root. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that xauth should be allowed write access on the root <Unknown> by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # grep xauth /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context unconfined_u:unconfined_r:xauth_t:s0-s0:c0.c1023 Target Context unconfined_u:object_r:default_t:s0 Target Objects /root [ None ] Source xauth Source Path /usr/bin/xauth Port <Unknown> Host box9 Source RPM Packages xorg-x11-xauth-1.0.6-1.fc16.x86_64 Target RPM Packages filesystem-2.4.44-1.fc16.x86_64 Policy RPM selinux-policy-3.10.0-75.fc16.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name box9 Platform Linux box9 3.2.2-1.fc16.x86_64 #1 SMP Thu Jan 26 03:21:58 UTC 2012 x86_64 x86_64 Alert Count 110 First Seen Mon 05 Mar 2012 08:19:02 AM EST Last Seen Mon 05 Mar 2012 10:55:37 AM EST Local ID 90fc420a-dec9-47ce-afa5-6132c99ec61d Raw Audit Messages type=AVC msg=audit(1330962937.294:98): avc: denied { write } for pid=1848 comm="xauth" name="root" dev=sda3 ino=1835009 scontext=unconfined_u:unconfined_r:xauth_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:default_t:s0 tclass=dirnode=box9 type=SYSCALL msg=audit(1330962937.294:98): arch=c000003e syscall=2 success=no exit=-13 a0=7fffea7afea0 a1=c1 a2=180 a3=8 items=0 ppid=1829 pid=1848 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=pts1 ses=1 comm="xauth" exe="/usr/bin/xauth" subj=unconfined_u:unconfined_r:xauth_t:s0-s0:c0.c1023 key=(null) Hash: xauth,xauth_t,default_t,None,write audit2allow audit2allow -R

The only way you can get a prompt containig root is by using su - . su will only produce a root prompt by starting as root. It it not posible to do this: [bobg@box6 ~]$ su Password: [root@box6 bobg]# So what are you really doing?

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAk9U4sMACgkQqbQrVW3JyMRS6ACeNKjnshZqXGuokzO/SgezwfH+ k14AnRw2m26afEXtnKhodkAEZK0SxPZE =6nNf -----END PGP SIGNATURE-----

On 05/03/12 09:39, Bob Goodwin wrote: > I have an F-16 computer that was working normally a couple of > days ago when run this morning has an unusual [to me] problem. > > When I su and type in the root password form the XCFE desktop it > spends about 20 seconds before displaying a prompt and then > instead of: > > [bobg@box6 ~]$ su > Password: > [root@box6 bobg]# exit > > > I get a prompt: bash-4.2# > > If instead of bringing up the desktop with startx I "su" it > changes to root quickly after entering the password, also with > the prompt "bash-4.2#." > > Other than that it apparently works? But obviously something has > changed and I can't guess what? > > Bob > > > > > If I ssh into box 9 from this computer [box6] I see the following which appears to indicate an SELinux problem? bash-4.2# cat /var/log/messages Mar 5 10:08:18 box9 setroubleshoot: SELinux is preventing /usr/bin/xauth from write access on the None /root. For complete SELinux messages. run sealert -l 90fc420a-dec9-47ce-afa5-6132c99ec61d Mar 5 10:08:22 box9 dbus-daemon[906]: ** Message: No devices in use, exit Not sure what to do ... Bob

On 05/03/12 09:39, Bob Goodwin wrote: > I have an F-16 computer that was working normally a couple of > days ago when run this morning has an unusual [to me] > problem. > > When I su and type in the root password form the XCFE desktop > it > spends about 20 seconds before displaying a prompt and then > instead of: > > [bobg@box6 ~]$ su > Password: > [root@box6 bobg]# exit > > > I get a prompt: bash-4.2# > > If instead of bringing up the desktop with startx I "su" it > changes to root quickly after entering the password, also > with > the prompt "bash-4.2#." > > Other than that it apparently works? But obviously something > has > changed and I can't guess what? > > Bob > > > > > If I ssh into box 9 from this computer [box6] I see the following which appears to indicate an SELinux problem? bash-4.2# cat /var/log/messages Mar 5 10:07:52 box9 dbus[906]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper) Mar 5 10:07:52 box9 dbus-daemon[906]: dbus[906]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper) Mar 5 10:07:52 box9 dbus-daemon[906]: Launching FprintObject Mar 5 10:07:52 box9 dbus[906]: [system] Successfully activated service 'net.reactivated.Fprint' Mar 5 10:07:52 box9 dbus-daemon[906]: dbus[906]: [system] Successfully activated service 'net.reactivated.Fprint' Mar 5 10:07:52 box9 dbus-daemon[906]: ** Message: D-Bus service launched with name: net.reactivated.Fprint Mar 5 10:07:52 box9 dbus-daemon[906]: ** Message: entering main loop Mar 5 10:08:00 box9 dbus[906]: [system] Activating service name='org.fedoraproject.Setroubleshootd' (using servicehelper) Mar 5 10:08:00 box9 dbus-daemon[906]: dbus[906]: [system] Activating service name='org.fedoraproject.Setroubleshootd' (using servicehelper) Mar 5 10:08:02 box9 dbus[906]: [system] Successfully activated service 'org.fedoraproject.Setroubleshootd' Mar 5 10:08:02 box9 dbus-daemon[906]: dbus[906]: [system] Successfully activated service 'org.fedoraproject.Setroubleshootd' Mar 5 10:08:04 box9 abrtd: Directory 'ccpp-2012-03-05-10:08:04-881' creation detected Mar 5 10:08:04 box9 abrt[1761]: Saved core dump of pid 881 (/usr/sbin/sedispatch) to /var/spool/abrt/ccpp-2012-03-05-10:08:04-881 (520192 bytes) Mar 5 10:08:05 box9 setroubleshoot: SELinux is preventing /usr/bin/xauth from write access on the None /root. For complete SELinux messages. run sealert -l 90fc420a-dec9-47ce-afa5-6132c99ec61d Mar 5 10:08:05 box9 abrtd: DUP_OF_DIR: /var/spool/abrt/ccpp-2012-03-05-08:19:06-878 Mar 5 10:08:05 box9 abrtd: Problem directory is a duplicate of /var/spool/abrt/ccpp-2012-03-05-08:19:06-878 Mar 5 10:08:05 box9 abrtd: Deleting problem directory ccpp-2012-03-05-10:08:04-881 (dup of ccpp-2012-03-05-08:19:06-878) Mar 5 10:08:06 box9 audispd: plugin /usr/sbin/sedispatch terminated unexpectedly Mar 5 10:08:06 box9 audispd: plugin /usr/sbin/sedispatch was restarted Mar 5 10:08:06 box9 setroubleshoot: SELinux is preventing /usr/bin/xauth from write access on the None /root. For complete SELinux messages. run sealert -l 90fc420a-dec9-47ce-afa5-6132c99ec61d Mar 5 10:08:08 box9 setroubleshoot: SELinux is preventing /usr/bin/xauth from write access on the None /root. For complete SELinux messages. run sealert -l 90fc420a-dec9-47ce-afa5-6132c99ec61d Mar 5 10:08:10 box9 setroubleshoot: SELinux is preventing /usr/bin/xauth from write access on the None /root. For complete SELinux messages. run sealert -l 90fc420a-dec9-47ce-afa5-6132c99ec61d Mar 5 10:08:12 box9 setroubleshoot: SELinux is preventing /usr/bin/xauth from write access on the None /root. For complete SELinux messages. run sealert -l 90fc420a-dec9-47ce-afa5-6132c99ec61d Mar 5 10:08:14 box9 setroubleshoot: SELinux is preventing /usr/bin/xauth from write access on the None /root. For complete SELinux messages. run sealert -l 90fc420a-dec9-47ce-afa5-6132c99ec61d Mar 5 10:08:16 box9 setroubleshoot: SELinux is preventing /usr/bin/xauth from write access on the None /root. For complete SELinux messages. run sealert -l 90fc420a-dec9-47ce-afa5-6132c99ec61d Mar 5 10:08:18 box9 setroubleshoot: SELinux is preventing /usr/bin/xauth from write access on the None /root. For complete SELinux messages. run sealert -l 90fc420a-dec9-47ce-afa5-6132c99ec61d Mar 5 10:08:22 box9 dbus-daemon[906]: ** Message: No devices in use, exit Not sure what to do ... Bob

I have an F-16 computer that was working normally a couple of days ago when run this morning has an unusual [to me] problem. When I su and type in the root password form the XCFE desktop it spends about 20 seconds before displaying a prompt and then instead of: [bobg@box6 ~]$ su Password: [root@box6 bobg]# exit I get a prompt: bash-4.2# If instead of bringing up the desktop with startx I "su" it changes to root quickly after entering the password, also with the prompt "bash-4.2#." Other than that it apparently works? But obviously something has changed and I can't guess what? Bob

On 03/06/2012 11:44 PM, jdow wrote: > Not all - there is a strong hint everything in the /root directory was > removed. The fix may be as simple as the copy he performed. If the > systems > differ in any material ways, different things installed, he may have some > lingering problems with missing files in /root. I think these days the > missing files will tend to get recreated. So it might not be as bad as > what > I faced in the late 90s from a corrupted /root directory in Hurricane. I > eventually solved it by reinstalling after incremental upgrades for a few > releases. Finally one didn't work and the reinstall made everything > happy. Well, things have changed since the 90's. There is nothing in /root other than anaconda-ks.cfg, install.log, and install.log.syslog on all of my systems plus a few other . files. Nothing of any importance that would cause things to fail.

On 06/03/12 01:09, Ed Greshko wrote: > I wonder if it is even being sourced, based on the manner > of other problems you've been reporting as of late. The other recent problems you refer to have been common to both computers, this one is a difference between them ... But they are different computers. Box9 has three drives, Box6 only one connected, etc. But I doubt those differences are the problem.

On 06/03/12 05:15, Ed Greshko wrote: > OK.... You have an unmodified ~/.bash_profile and a slightly > different ~/.bashrc from my fresh install. The differences are not > significant. The bottom line is that in ~/.bashrc you have if [ -f > /etc/bashrc ]; then . /etc/bashrc Which should source the file. The > place where the setting of PS1 takes place is here.... >> # Turn on checkwinsize >> shopt -s checkwinsize >> [ "$PS1" = "\\s-\\v\\\$ " ]&& PS1="[\u@\h \W]\\$ " > Basically it is saying.... if PS1 is set to '\s-\v\$ ' change it to > '[\u@\h \W]\$ ' . > > So, it would seem, one of 2 things are going on. Either the file isn't > being sourced or it isn't set as expected. > > What I would do is modify /etc/bashrc to .... > > shopt -s checkwinsize > echo "PS1 is set to $PS1"> /tmp/huh > [ "$PS1" = "\\s-\\v\\\$ " ]&& PS1="[\u@\h \W]\\$ " > > And then perform an su -. > Ok, is this what you are suggesting I do? shopt -s checkwinsize # [ "$PS1" = "\\s-\\v\\\$ " ] && PS1="[\u@\h \W]\\$ " echo "PS1 is set to $PS1" > /tmp/huh [ "$PS1" = "\\s-\\v\\\$ " ] && PS1="[\u@\h \W]\\$ "

Why didn't I think of that? Because I'm trying to do too many things at once, distractions here. "Bad" computer, "Good" prompt as user: [bobg@box9 ~]$ set | grep ^PS PS1='[\u@\h \W]\$ ' PS2='> ' PS4='+ ' Bad prompt as root: [bobg@box9 ~]$ su Password: bash-4.2# set | grep ^PS PS1='\s-\v\$ ' PS2='> ' PS4='+ ' It is different but where does it come from?

> finally settled things seem to work normally except I still get > that strange prompt "bash-4.2#" when it has always been > "[root@box6 bobg]#." I don't know if that helps but I have seen 'your strange prompt' doing this: [emilio@mipc]$ su password: [root@mipc]# su jhon bash-4.2# Emilio

On 2012/03/06 04:45, Bob Goodwin wrote: > On 06/03/12 07:03, suvayu ali wrote: >> On Tue, Mar 6, 2012 at 12:30, Ed Greshko&lt;Ed.Greshko(a)greshko.com&gt; wrote: >>> You said you have this.... >>> >>> bash-4.2# ls /etc/bashrc* >>> /etc/bashrc /etc/bashrc~ /etc/bashrc.wrkng >>> >>> I don't know what /etc/bashrc~ since I don't have one on my system. >>> Maybe move that to /tmp or something and try again? >>> >> Those are backup files from some editor, most likely emacs. It suggests >> the OP has edited the /etc/bashrc at some point in the past. >> >>> I also note that "ll" doesn't seem to work. That is also troublesome >>> since it would seem to indicate a problem with sourcing the files in >>> /etc/profile.d. You do have a /etc/profile file? >>> >>> Another thing to try.... >>> >>> Move /etc/bashrc.wrkng back to /etc/bashrc and then "su -". You'll >>> have >>> the "bad" prompt. But then type ". /etc/bashrc" and see if there are >>> any error messages. >> I think all these problems are still related to the SELinux issue >> the OP >> had earlier. Probably the relabel did not work completely. I would >> suggest the OP to take a look at the permissions and the SELinux >> context >> of the profile directories and rc files. >> >> This is how it should be: >> >> $ ls -lhd /etc/bash* /etc/profile* >> -rw-r--r--. 1 root root 57K Sep 4 2011 /etc/bash_completion >> drwxr-xr-x. 2 root root 4.0K Feb 28 14:30 /etc/bash_completion.d >> -rw-r--r--. 1 root root 2.6K Aug 16 2011 /etc/bashrc >> -rw-r--r--. 1 root root 1.8K Aug 16 2011 /etc/profile >> drwxr-xr-x. 2 root root 4.0K Feb 27 10:09 /etc/profile.d > > [root@box9 ~]# ls -lhd /etc/bash* /etc/profile* > -rw-r--r--. 1 root root 57K Sep 4 2011 /etc/bash_completion > drwxr-xr-x. 2 root root 4.0K Feb 3 10:35 /etc/bash_completion.d > -rw-r--r--. 1 root root 2.6K Mar 6 07:10 /etc/bashrc > -rw-r--r--. 1 root root 2.6K Aug 16 2011 /etc/bashrc~ > -rw-r--r--. 1 root root 2.6K Mar 6 05:30 /etc/bashrc.wrkng > -rw-r--r--. 1 root root 1.8K Aug 16 2011 /etc/profile > drwxr-xr-x. 2 root root 4.0K Mar 3 12:09 /etc/profile.d > > >> >> >> $ ls -Zd /etc/bash* /etc/profile* >> -rw-r--r--. root root system_u:object_r:etc_t:s0 /etc/bash_completion >> drwxr-xr-x. root root system_u:object_r:etc_t:s0 /etc/bash_completion.d >> -rw-r--r--. root root system_u:object_r:etc_t:s0 /etc/bashrc >> -rw-r--r--. root root system_u:object_r:etc_t:s0 /etc/profile >> drwxr-xr-x. root root system_u:object_r:bin_t:s0 /etc/profile.d > > [root@box9 ~]# ls -Zd /etc/bash* /etc/profile* > -rw-r--r--. root root system_u:object_r:etc_t:s0 /etc/bash_completion > drwxr-xr-x. root root system_u:object_r:etc_t:s0 /etc/bash_completion.d > -rw-r--r--. root root unconfined_u:object_r:etc_t:s0 /etc/bashrc > -rw-r--r--. root root system_u:object_r:etc_t:s0 /etc/bashrc~ > -rw-r--r--. root root unconfined_u:object_r:etc_t:s0 /etc/bashrc.wrkng > -rw-r--r--. root root system_u:object_r:etc_t:s0 /etc/profile > drwxr-xr-x. root root system_u:object_r:bin_t:s0 /etc/profile.d > > >> >> # ls -lh /root/.bash* >> -rw-------. 1 root root 32K Mar 4 22:55 /root/.bash_history >> -rw-r--r--. 1 root root 24 Aug 10 2011 /root/.bash_logout >> -rw-r--r--. 1 root root 404 Feb 19 18:11 /root/.bash_profile >> -rw-r--r--. 1 root root 2.1K Mar 4 22:57 /root/.bashrc > > [root@box9 ~]# ls -lh /root/.bash* > -rw-------. 1 root root 927 Mar 6 07:13 /root/.bash_history > > >> >> # ls -Z /root/.bash* >> -rw-------. root root system_u:object_r:admin_home_t:s0 >> /root/.bash_history >> -rw-r--r--. root root system_u:object_r:admin_home_t:s0 >> /root/.bash_logout >> -rw-r--r--. root root system_u:object_r:admin_home_t:s0 >> /root/.bash_profile >> -rw-r--r--. root root system_u:object_r:admin_home_t:s0 /root/.bashrc > > [root@box9 ~]# ls -Z /root/.bash* > -rw-------. root root system_u:object_r:admin_home_t:s0 > /root/.bash_history > > >> >> GL >> > > All I've done here is listed the files you suggested, not sure what > the results mean ... > > Bob You have cleared out your root directory is that that means. Whatever was in there is lost. You played with the "rm" command as root and were careless about the command formatting. "Oops".

Repair will be tedious at best - reinstall at worst depending on your level of expertise.

{^_^}