On Thu, Nov 04, 2021 at 05:44:31PM +0100, deloptes wrote:
> obexd[4068]: open(/home/user/Downloads/20020011.jpg): Operation not
> permitted (1)
That's an interesting message for that operation.
The open(2) man page shows only two possible sources for EPERM on an open:
EPERM The O_NOATIME flag was specified, but the effective user ID of
the caller did not match the owner of the file and the caller
was not privileged.
EPERM The operation was prevented by a file seal; see fcntl(2).
I don't know whether this is truly a comprehensive list of causes. I'm
wondering about things like FUSE-mounted file systems. What kind of
file system is /home/user/Downloads/ part of?
I also have no idea what an obexd is, but I was wondering about AppArmor
(even though I think AppArmor causes EACCES not EPERM). So:
unicorn:~$ apt-cache search obexd
bluez-obexd - bluez obex daemon
Then I looked at
<https://packages.debian.org/bullseye/amd64/bluez-obexd/filelist> but
I don't see any AppArmor profiles in that package. Oh well.
