https://bugzilla.suse.com/show_bug.cgi?id=1206957 https://bugzilla.suse.com/show_bug.cgi?id=1206957#c6 --- Comment #6 from Alberto Planas Dominguez <aplanas@suse.com> --- (In reply to Ludwig Nussel from comment #5)

No it's not a duplicate.

Ah OK. My bad then, yes.

lmod is doing nasty things here and pollutes the shell environment via /etc/profile.d/lmod.sh.

This seems to be true. But there is a regressions somewhere in lmod, lesscode or apparmor, as this was not there until the last update.

My strong advice would be not do that. Instead there could be eg. only something like an "lmod-activate" or "lmod-enter" alias that sources /usr/share/lmod/8.7.15/init/bash *on demand* rather than for each and every shell of each and every user.

No idea here, but seems to be a core feature of lmod to enable / disable module without user interaction, nor logout / login routine. I guess that you get dragged here because one change in the apparmor spec that seems unrelated (usermerge). The other package the changed was lmod. Less did no change recently. -- You are receiving this mail because: You are on the CC list for the bug.