Strange journald entry

DooshPastesh

I have been running successfully Solus Budgie for some time. From time to time I check journald (which is clean usually). Some time ago strange entry occured:
maj 31 21:34:36 plasma [613]: failed to execute '/usr/bin/sh' '/usr/bin/sh -c '/usr/bin/setfacl -m g:lirc:rw /dev/bus/usb/002/001 2>/dev/null || :'': No such file or directory
So, I've decided to try Plasma. Fresh Install, update, and the same error occurs.

Justin

Package acl has file /bin/setfacl

From eopkg info: This package contains the libacl.so dynamic library containing the POSIX 1003.1e draft standard 17 functions for manipulating access control lists.

Looks like plasma is looking in the wrong location for the setfacl file, it's in /bin/ not /usr/bin/ @Girtablulu.

Girtablulu

Justin Mmmh question is why does it get installed via the package.yml into /bin and not /usr/bin ? @DataDrake @JoshStrobl do you know why?

DataDrake

Justin Wrong. It couldn't find /usr/bin/sh and should be calling /bin/sh

DooshPastesh

The same error I had on budgie. How to fix this?

johano

DooshPastesh Try creating a symbolic link to the file in/user/bin

sudo ln -s /bin/setfacl /use/bin/setfacl

JoshStrobl

Girtablulu Because it's required at boot and /bin is the standard location for binaries which are needed for booting. setfacl is required for setting ACLs (access controls) on files and directories. More information here and here.

Justin

DataDrake OK. Either way setfacl is also not being looked for the right location.

Girtablulu

@DooshPastesh are you using a different shell then bash?

DooshPastesh

I did on budgie but I thought it was the reason so, on fresh plasma installation I'm using bash. I've already did symlink but after reboot nothing changed.
ln: nie udało się utworzyć dowiązania symbolicznego '/use/bin/setfacl': Nie ma takiego pliku ani katalogu
That means it couldn't make symlink because there is no file or directory.

Girtablulu

DooshPastesh because it should be usr/bin and not use/bin

DataDrake

Justin You're missing my point. This is a prefix issue.

Solving it with symlinks is the wrong approach. We need to find out why it is trying to use the wrong prefix for /bin. @Girtablulu couldn't reproduce this on his install so we need to start looking for something in the environment that is causing this, not adding symlinks that aren't on a working system.

DooshPastesh

Any news about fixing this?

kyrios

DooshPastesh well was this reported on the dev tracker already?

DooshPastesh

kyrios I did not reported this anywhere, only here. Should I report this? If yes, then where?

kyrios

There is a link to the dev tracker on the top navigation bar or look there: https://getsol.us/articles/contributing/getting-involved/en/#report-bugs

DooshPastesh

Thank you. I will report immediately.