https://bugzilla.suse.com/show_bug.cgi?id=1219979 https://bugzilla.suse.com/show_bug.cgi?id=1219979#c1 Dirk Weber changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |d_werner@gmx.net --- Comment #1 from Dirk Weber --- Just for information: this is basically the same problem as described by bug 1203617. Short summary: such functions should not be defined in the profile (/etc/profile.d or ~/.profile ) but in bashrc (/etc/bash.bashrc.local, ~/.bashrc) which are intended for interactive shells. In your case with local adaptations you can just move the definitions there. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1219979 https://bugzilla.suse.com/show_bug.cgi?id=1219979#c3 --- Comment #3 from Jean-Claude Dole --- Following comment 1 I put initialization in /etc/bash.bashrc.local There is a problem. Any times user open a new konsole from the application launcher, function definition are lost in the new konsole. Function definitions seems not inherited from the parent environnement. But Env var still be defined. Any advices are welcome. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1219979 https://bugzilla.suse.com/show_bug.cgi?id=1219979#c5 --- Comment #5 from Jean-Claude Dole --- Thank you very much for taking the time to answer me. Rightly or wrongly, for years I have been using the following piece of code (or somethings similar) to make variables and function definitions accessible to everyone: ----> if test -z "$SOURCED_SYS_COMMON_VAR" ; then test -s /backup_sys/VAR/MY_ENV_VAR/zzzz2_system_common_general_env_var_full.sh && . /backup_sys/VAR/MY_ENV_VAR/zzzz2_system_common_general_env_var_full.sh if [[ "$E_FILES_DIFFER" -ne 109 ]] ; then MY_LOGGER2_bash_bashrc_local "E_FILES_DIFFER -ne 109 --- COMMON VAR NOT SOURCED : zzzz2_system_common_general_env_var_full.sh" "0" else readonly SOURCED_SYS_COMMON_VAR=true export SOURCED_SYS_COMMON_VAR fi else MY_LOGGER2_bash_bashrc_local "COMMON VAR ALREADY SOURCED : zzzz2_system_common_general_env_var_full.sh" "5" fi if test -z "$SOURCED_SYS_COMMON_FUNC" ; then test -s /backup_sys/VAR/MY_ENV_VAR/zzzz1_system_common_function_full.sh && . /backup_sys/VAR/MY_ENV_VAR/zzzz1_system_common_function_full.sh if [[ -z "$(LC_ALL=C type stop_or_continue 2>/dev/null)" ]] ; then MY_LOGGER2_bash_bashrc_local "COMMON FUNC NOT SOURCED : zzzz1_system_common_function_full.sh" "0" else readonly SOURCED_SYS_COMMON_FUNC=true export SOURCED_SYS_COMMON_FUNC fi else MY_LOGGER2_bash_bashrc_local "COMMON FUNC ALREADY SOURCED : zzzz1_system_common_function_full.sh" "5" fi <---- That has worked for me from the old days up to 15.4 See screenshots : 15.1 https://paste.opensuse.org/pastes/d0119db2c2fa 15.4 https://paste.opensuse.org/pastes/c8b8584b73fd 15.5 and 15.6 same behaviour : Function definitions does not survive. https://paste.opensuse.org/pastes/86e970296d2c Konsole Opensuse for each test : Command : konsole Configuration : builtin So somethings has change since 15.5 You will notice that this only concerns function definitions. Of course if I remove the one-shot read >>> if test -z "$SOURCED_SYS_COMMON_FUNC" ; then <<< there is no problem but the files definitions are reread indefinitely. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1219979 https://bugzilla.suse.com/show_bug.cgi?id=1219979#c7 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WORKSFORME Status|NEW |RESOLVED --- Comment #7 from Dr. Werner Fink --- Just created on TW (should also work on Leap) a file localhost:~/Desktop # cat /etc/profile.d/testt.sh function xyz () { true } export -f xyz export testt=testt localhost:~/Desktop # then log out and log in again open a konsole and see localhost:~/Desktop # printenv | grep testt testt=testt localhost:~/Desktop # printenv | grep xyz BASH_FUNC_xyz%%=() { true and it works localhost:~/Desktop # set -x; xyz ; set +x + xyz + true + set +x it should be noted that I use the display-manager.service on that TW -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1219979 https://bugzilla.suse.com/show_bug.cgi?id=1219979#c9 --- Comment #9 from Jean-Claude Dole --- (In reply to Dr. Werner Fink from comment #6)

Exporting functions is a bash special feature* and not supported by any other shell or program like systemd and as all exported variables this belongs to /etc/profile, /etc/profile.local, and /etc/profile.d/*.sh

Can we please stop misusing ~/.bashrc, /etc/bash.bashrc, and /etc/bash.bashrc.local for environment? Those are for interacive invocation only. As the the profile is sourced at login via e.g. (/usr)/etc/X11/xdm/Xsession in the exec_login() function to have the environmnet only once for the full login session.

* werner@boole:~> xyz() { true; } werner@boole:~> export -f xyz werner@boole:~> printenv | grep xyz printenv | grep -A1 xyz BASH_FUNC_xyz%%=() { true }

only bash knows about `export -f' and `BASH_FUNC_*%%=()' but not systemd

Following your comment I sourced my files definitions in : /etc/profile.d/*.sh --> that does not work /etc/profile.local/*.sh --> that does not work In each case same error : Apr 11 18:57:40 localhost.localdomain startplasma-x11[1537]: org.kde.plasma.libkworkspace: Skipping syncing of environment variable "BASH_FUNC_stop_or_continue%%" as name contains unsupported characters Apr 11 18:57:40 localhost.localdomain startplasma-x11[1537]: org.kde.plasma.libkworkspace: Skipping syncing of environment variable "MY_LIGHT_CYAN" as value contains unsupported characters -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1219979 https://bugzilla.suse.com/show_bug.cgi?id=1219979#c11 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Assignee|werner@suse.com |screening-team-bugs@suse.de Resolution|WORKSFORME |--- Summary|Bash exported function are |KDE plasma workspace |renamed internally then are |ignores special environment |ignored by Systemd - Kde |variables (Was: Bash |desktop |exported function are | |renamed internally then are | |ignored by Systemd - Kde | |desktop) CC| |alarrosa@suse.com, | |christophe@krop.fr, | |fabian@ritter-vogt.de, | |lbeltrame@kde.org, | |werner@suse.com --- Comment #11 from Dr. Werner Fink --- (In reply to Jean-Claude Dole from comment #8)

That does not work on a fresh install of leap 15.5 nor leap 15.6 Apr 11 18:57:40 localhost.localdomain startplasma-x11[1537]: org.kde.plasma.libkworkspace: Skipping syncing of environment variable "BASH_FUNC_stop_or_continue%%" as name contains unsupported characters

Remark : None of my functions have a %% in their name.

Yep ... this what bash does to detect exported function names and this is nonnegotiable as a security feature. And this is what export -f <function> does, it prefixes any exported function with BASH_FUNC_ and also suffixes it with `%%' ... see https://unix.stackexchange.com/questions/609739/bash-exported-function-not-v...

Same kind error for environment variables :

Apr 11 18:57:40 localhost.localdomain startplasma-x11[1537]: org.kde.plasma.libkworkspace: Skipping syncing of environment variable "MY_LIGHT_CYAN" as value contains unsupported characters

MY_LIGHT_CYAN is defined like this MY_LIGHT_CYAN=$'\e[1;36m' or defined like this MY_LIGHT_CYAN=$'\e[1;36m'

That is an other building yard, means not bash. As I'm using systemd but not KDE not GNOME as desktop the subject of this bug seems to be misleading one. This is not a bug of systemd nor of bash. But it could be that this is a security feature to protect against malicious escape sequences in variables names as well as variable values. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1219979 https://bugzilla.suse.com/show_bug.cgi?id=1219979#c13 --- Comment #13 from Dr. Werner Fink --- (In reply to Jean-Claude Dole from comment #10)

I would like to point out that you did not answer my question: "What changes Opensuse have made after version leap 15.4"

On the other hand, in your remarks you refer to systemd. What systemd has to do with the Bash program.

Regards

Guess ... new plasma workspace version with tighten security filters in the environment handling, but this is a guess. As I'm sill using fvwm (+ lxsession + xfce4-panel) I do not face this problem. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1219979 https://bugzilla.suse.com/show_bug.cgi?id=1219979#c16 --- Comment #16 from Jean-Claude Dole --- (In reply to Fabian Vogt from comment #15)

Resetting severity - this is not critical by any means.

(In reply to Dirk Weber from comment #1)

...

Just for information: this is basically the same problem as described by bug 1203617.

Short summary: such functions should not be defined in the profile (/etc/profile.d or ~/.profile ) but in bashrc (/etc/bash.bashrc.local, ~/.bashrc) which are intended for interactive shells.

In your case with local adaptations you can just move the definitions there.

^

IMO RESOLVED INVALID or WONTFIX.

That "%" is not a valid environment variable for "dbus-update-activation-environment --systemd" is a systemd topic: https://github.com/systemd/systemd/pull/25235

Stop that. I am not using any "%" in name. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1219979 https://bugzilla.suse.com/show_bug.cgi?id=1219979#c18 --- Comment #18 from Jean-Claude Dole --- Just tell me how can I define an environment variable for some colors ? Just tell me how can I defined bash functions that are not available in the binaries. For any kind of shell session ( interactive, non interactive, login or non login , .....) -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1219979 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #874405|text/plain |image/png mime type| | -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1219979 https://bugzilla.suse.com/show_bug.cgi?id=1219979#c21 --- Comment #21 from Dr. Werner Fink --- Maybe an executable bash script ~/.config/plasma-workspace/env/kwin_env.sh but only for a local user user is also a way (older system have ~/.kde/env/ or ~/.kde4/env/ for the location of kwin_env.sh) -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1219979 https://bugzilla.suse.com/show_bug.cgi?id=1219979#c23 --- Comment #23 from Jean-Claude Dole --- Please compare https://doc.opensuse.org/documentation/leap/startup/html/book-startup/cha-ad... Table 14.1.1 Bash configuration files and Table 14.2: Bash configuration files for non-login shells There is ambiguity about the choice of '/etc/profile.d' or '/etc/profile.local' The use of '/etc/profile.d' is not prohibited for BASH. This was the source of my troubles. More complete explanations would be welcome. -- You are receiving this mail because: You are on the CC list for the bug.