http://bugzilla.opensuse.org/show_bug.cgi?id=1052182 http://bugzilla.opensuse.org/show_bug.cgi?id=1052182#c1 Ron Lovell changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ron163264@gmail.com --- Comment #1 from Ron Lovell --- ron163264@gmail.com: I tried submitting a bug against this one myself, unsuccessfully. I think the problem did come with the aaa_base update in snapshot 20170802. The problem is that /etc/profile sources /etc/bash.bashrc, which unsets 'is', so that a test in /etc/profile fails because "$is" is empty. My workaround, replacing /etc/profile:342: _is_save=$is test -r /etc/bash.bashrc && . /etc/bash.bashrc is=$_is_save unset _is_save -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1052182 Felix Miata changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mrmazda@earthlink.net -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1052182 http://bugzilla.opensuse.org/show_bug.cgi?id=1052182#c4 Lucifer Watson changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |opensuse@the-systems-common | |wealth.net --- Comment #4 from Lucifer Watson --- (In reply to Kriton Kyrimis from comment #2)

Wouldn't it be simpler to remove the line "unset is" in /etc/bash.bashrc (line 365), which was introduced in the latest update, as this seems to be the source of the problem? I commented it out, and my .bashrc is being read again, without having to source it in my .profile.

Thank you. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1052182 http://bugzilla.opensuse.org/show_bug.cgi?id=1052182#c6 --- Comment #6 from Ron Lovell --- (In reply to Ron Lovell from comment #5)

(In reply to Kriton Kyrimis from comment #2)

...

Wouldn't it be simpler to remove the line "unset is" in /etc/bash.bashrc ...

Yes, that seems simplest. So if the 'unset is' is uncommented, then $is will be set in the new shell. Example, starting with a login interactive shell:

$ echo $is

$ bash $ echo $is bash

It's hard to imagine how this could cause a problem, but I just wanted to mention it for the maintainer to consider.

Correction: Meant to say: So if the 'unset is' is COMMENTED OUT, then ... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1052182 http://bugzilla.opensuse.org/show_bug.cgi?id=1052182#c8 --- Comment #8 from Ron Lovell --- (In reply to Ron Lovell from comment #7)

BTW, I tracked down how bash.bashrc is getting sourced for non-login shells.

Another correction: I meant to say: ... uncomment this line: /* #define SYS_BASHRC "/etc/bash.bashrc" */ I apologize for these mistakes. I'll try to do better. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1052182 http://bugzilla.opensuse.org/show_bug.cgi?id=1052182#c10 --- Comment #10 from Ron Lovell --- (In reply to Kriton Kyrimis from comment #9)

(In reply to Ron Lovell from comment #5)

...

So if the 'unset is' is commented out, then $is will be set in the new shell.

Perhaps this is what they wanted to correct by unsetting is, except that they did it too early, while the variable was still needed.

Agreed. Here's an idea for a minimalist change to bash.bashrc. At top, before the 'test -z "$is"; then' statement, save 'is' if it is set (not just non-null), otherwise save 'unset': _is_save=${is-"unset"} if test -z "$is" ; then ... as before ... At the end, where 'is' is unset, substitute: if test "$_is_save" = "unset" ; then unset is fi unset _is_save -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1052182 Andreas Schneider changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |asn@cryptomilk.org -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1052182 http://bugzilla.opensuse.org/show_bug.cgi?id=1052182#c17 --- Comment #17 from Ron Lovell --- (In reply to Ron Lovell from comment #16)

(In reply to Dr. Werner Fink from comment #13)

...

Created attachment 735703 [details] Collect the ideas in one commit for aaa_base ...

any suggestions, criticism, and/or comments one this one?

This should work. It's a different design, with changes to both /etc/profile and /etc/bash.bashrc. (I was proposing a change to bash.bashrc only.) The patch seems to correctly handle sourcing bash.bashrc from profile, as well as bash.bashrc read directly by bash for non-login shells.

Actually, with the change to /etc/profile, is the change to bash.bashrc even needed? I should have made it clearer that the proposed change to bash.bashrc in comment #10 was an ALTERNATIVE to the change to profile in comment #1, not a supplement to it. If you tried to use them both, that wouldn't have worked. With the change to profile, it's fine that bash.bashrc unsets 's', and that would be expected action if, for example, bash.bashrc is sourced by a user from her ~/.bashrc (as is done in Fedora). I'm still staring at the patch, but unless I'm missing something, the change to bash.bashrc looks redundant. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1052182 Arvin Schnell changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aschnell@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1052182 http://bugzilla.opensuse.org/show_bug.cgi?id=1052182#c21 --- Comment #21 from Ron Lovell --- (In reply to Dr. Werner Fink from comment #20)

(In reply to Jacob W from comment #19)

...

There have been multiple solutions presented. Personally, I think it's imperative that the solution works where .bashrc is sourced by both login and non-login shells, like comment #11

Why hasn't this (or similar) solution been committed already? This bug is driving me crazy - especially when generating new servers.

AFAICS from Base:System/aaa_base it is committed ... here I have in /etc/profile in line 341ff

if test "$is" != ksh -a "$is" != zsh ; then _is_save=$is test -r /etc/bash.bashrc && . /etc/bash.bashrc is=$_is_save unset _is_save fi

that should help the lines below to source $HOME/.bashrc

Yes, on my Tumbleweed system the fix came with aaa_base 13.2+git20170814.cc9e34e-1.1 in snapshot 20170830. Don't know status in Leaps. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1052182 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(werner@suse.com) | -- You are receiving this mail because: You are on the CC list for the bug.