Pause and strange output when entering administrator console

When entering su - and then password there is a strange pause and output:

anixx@anixx-desktop:~> su -
Пароль:
-bash: export: found.': not a valid identifier -bash: export: found.’: not a valid identifier
-bash: export: found.': not a valid identifier -bash: alias: Command: not found -bash: alias: not: not found -bash: alias: found.: not found -bash: export: found.’: not a valid identifier
-bash: export: found.': not a valid identifier -bash: export: found.’: not a valid identifier
-bash: alias: Command: not found
-bash: alias: not: not found
-bash: alias: found.: not found

Ansus wrote:
> When entering su - and then password there is a strange pause and
> output:

this was not the case yesterday when you “successfully installed
Reduce from Alt dated by May 2008”, was it?


palladium

It looks as if your root’s .profile and/or .bashrc and/or* .alias *are damaged.

Guess you hit the nail once again…:wink:

To the OP: who told you you could just install any package from any distro? How did you install it? From some other posts of yours yesterday, I get the idea you pretty borked up your install. Reduce works, all other things don’t?

Reduce works, all other things don’t?

It is certainly not because of Reduce: after its installation all was OK and also I had Reduce installed for about 4 months before.

But the problem indeed may be because of some third-party package. Is it possible to restore the system?

Knurpht wrote:

>
> palladium;2133293 Wrote:
>> this was not the case yesterday when you “successfully installed
>> Reduce from Alt dated by May 2008”, was it?
>>
>> –
>> palladium
>
> Guess you hit the nail once again…:wink:
>
> To the OP: who told you you could just install any package from any
> distro? How did you install it? From some other posts of yours
> yesterday, I get the idea you pretty borked up your install. Reduce
> works, all other things don’t?
>
>
I still do not understand why it is necessary to mix distros, a binary (not
rpm) for Reduce for Opensuse is availble on sourceforge and it works with
11.2 (I downloaded and tested it so far before I posted my suggestion to
give the sourceforge binary a try in the other thread).
Mixing rpm’s from diverent distros is sometimes possible (if you know what
you are doing and if it is not a problem if the system is inconsistent
afterwards) but really the last thing on earth one should do with a
production system (even if the production system is only the private PC at
home).

beside that it seems to be that your bashrc or another related config file
in the root account is screwed (looks like there are invalid aliases
defined).

As we are not clairvoyant we can not tell.

But martin_helm and I suggested that you checked the startup files in root’s home. Did you do that? When yes, what is the outcome? When no, why not?

Martin Helm wrote:
> it seems to be that your bashrc or another related config file
> in the root account is screwed (looks like there are invalid aliases
> defined).

yep…

i just recall a story a kindly old lady told me when i was just a kid:

Bus driver stopped to at a bus stop and saw an old man waving his arms
to the driver while walking toward the bus, slowly…

the driver assumed the old man wanted to ride the bus, so waited…

when the old man finally got on the bus the bus driver asked: “Why
were you walking so slow?”

the old man replied: “The hurrier i go the behinder i get.”

and so it is with so many we get here who don’t have the time it
takes to learn how to do things the right/safe/correct way…

and they get so far behind they either slam the door on their way out
or spend three times as much time fixing or reinstalling . . .

there are easier ways than learning via The School of Hard Knocks…


palladium
ps: this outta be in chit-chat, so shoot me.

But martin_helm and I suggested that you checked the startup files in root’s home. Did you do that? When yes, what is the outcome?

How can I check them? I looked for them and they exist. They are by SUSE. They start and do not return error.

But the error output appears when executing either

su -l

or

su -l anixx

(anixx is the username)

When doing su or su -m no error reported.

@palladium:
That story is a really cool. :wink:

@Ansus:
I don’t want to bother you. But keep in mind the last thing you did (the
last thing we know about) is you installed a package from another distro.
And the next thing is you have weird problems. So I think it is not a bad
attitude to think it is possibly related (it may be or it may be not, who
knows).
Check what hcvv suggested.

@hcv:
Sorry for posting the same, did not see it your suggestion earlier.

Ansus wrote:
>> Reduce works, all other things don’t?
> It is certainly not because of Reduce: after its installation all was
> OK and also I had Reduce installed for about 4 months before.

maybe (probably?) not, but the point is it is a NEW problem…so,
what did you do between that successful install yesterday and when
this problem popped up (note: things like this don’t “just happen”,
something changed! what??)

> But the problem indeed may be because of some third-party package. Is
> it possible to restore the system?

sure, restore from your backup…


palladium

Nice they are there, but you should look inside them. I would do that using vi, but maybe youlike anothetr editor.

And of course there are no errors with the -m option, because it is the -l option that ‘sources’ them.

I tried(unsuccessfully) to install an old network scanner which asked for many dependencies which I found only in very old distros.

Did you check all of these files?

~/.profile
~/.bashrc
~/bash_login
~/.bash_profile

Well I found that this block leads to the error:


#
# Source profile extensions for certain packages, the super
# may disable some of them by setting the sticky bit.
#
if test -d /etc/profile.d -a -z "$PROFILEREAD" ; then
    for s in /etc/profile.d/*.sh ; do
	test -r $s -a ! -k $s && . $s
    done
    unset s
fi

With it deleted no errors reported.

Seems the problem is inside /etc/profile.d?

Ansus wrote:
> When doing su or su -m no error reported.

which means (i think) that root’s environment is polluted, but the
user’s is not…

which means (i think) that you did something (with root powers) to
root config files (probably those already mentioned by hcvv which
exist in /etc and maybe other places)

well, maybe you didn’t do it, maybe one of the installs you did
yesterday or today did it for you…


palladium

Well I located the file and the package that caused the problem.

It was /etc/profile.d/elektra-elektraenv.sh

Ansus wrote:
> I tried(unsuccessfully) to install an old network scanner which asked
> for many dependencies which I found only in very old distros.

uninstall the old network scanner and all the dependencies you
installed with it and see if you get your working system back…

or, restore from backup…


palladium

Ansus wrote:

>
> Seems the problem is inside /etc/profile.d?
>
>
I think the problem is not the profile.d itself but this

>I tried(unsuccessfully) to install an old network scanner which asked
>for many dependencies which I found only in very old distros.

Try to make your system consistent again by removing the “dependencies which
I found only in very old distros”.