Thank for the feedback. The package comes from https://www.scilab.org/download/scilab-6.1.1 I could not find a recent rpm package. I can get the source, but then I will need to build the rpm. This requires a spec file. I am not sure how easy to make one. This site https://scilab.gitlab.io/legacy_wiki/Scilab(20)Linux(2f)Unix(20)packages does not really help =========================================================================== Patrick DUPRÉ | | email: pdupre@xxxxxxx Laboratoire interdisciplinaire Carnot de Bourgogne 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE Tel: +33 (0)380395988 | | Room# D114A =========================================================================== > Sent: Tuesday, March 07, 2023 at 8:14 PM > From: "Todd Zullinger" <tmz@xxxxxxxxx> > To: users@xxxxxxxxxxxxxxxxxxxxxxx > Subject: Re: chcon > > Barry wrote: > >> On 7 Mar 2023, at 17:58, Patrick Dupre <pdupre@xxxxxxx> wrote: > >> > >> I can run scilab as root user, but as a standard user, I get: > >> > >> /usr/bin/chcon: failed to change context of '/usr/local/scilab/scilab-6.1.1/bin/scilab-bin' to ‘unconfined_u:object_r:execmem_exec_t:s0’: Operation not permitted > >> Error: Cannot chcon 'scilab-bin' > >> > >> Can I fix this issue? > > > > Are you running a setup/install script? > > I would not expect chcon in an app start script. > > And yet, the scilab command appears to do just that. :( > > The code looks to come from here: > > https://gitlab.com/search?search=chcon&nav_source=navbar&project_id=3330423&group_id=1609406&search_code=true&repository_ref=6.1 > > The chcon calls were added 11 years ago, in: > > https://gitlab.com/scilab/scilab/-/commit/fde269e73db4705fb19804fdd23f3185b54e2b7b > > This added a function named `check_and_disable_selinux()` > with the comment "If enabled, disable se_linux." > > That's just software which has not kept up with the times. > > > Is scilab from a Fedora RPM? > > The /usr/local prefix makes that highly unlikely. > > And `dnf provides /usr/local/scilab` doesn't return > anything. > > I think this is an upstream issue and would be better asked > in their forums and/or bug tracker. > > It shouldn't need to run chcon at all. If it must, it ought > to check that the file doesn't already have the desired > SELinux type, which would avoid the issue. Or you could > install it somewhere within your home directory instead of > in a root-owned location like /usr/local. > > -- > Todd > _______________________________________________ > users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue > _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
