Skip to main content
17 events
when toggle format what by license comment
Dec 9, 2022 at 10:36 answer added Gordon timeline score: 0
Dec 6, 2020 at 3:27 vote accept wispi
Aug 16, 2020 at 17:31 answer added dturvene timeline score: 1
Dec 7, 2019 at 8:02 history bumped CommunityBot This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Aug 5, 2019 at 17:01 history bumped CommunityBot This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Jun 7, 2019 at 19:34 answer added alexcloud2 timeline score: 9
Feb 20, 2019 at 15:06 comment added Stonecraft I am having the same issue after installing qemu 3.1.
Sep 25, 2018 at 21:36 comment added wispi The output of namei -l [path to Qemu executable] is: f: /usr/local/bin/qemu-2.12.1/x86_64-softmmu/qemu-system-x86_64 drwxr-xr-x root root / drwxr-xr-x root root usr drwxrwsr-x root staff local drwxr-sr-x root staff bin drwxr-sr-x root staff qemu-2.12.1 drwxr-sr-x root staff x86_64-softmmu -rwxr-xr-x root staff qemu-system-x86_64 . I can still run the file by entering the path in terminal.
Sep 25, 2018 at 17:27 comment added Michael Hampton I said: "You need to check the permissions of the file and all of its containing directories. You may find namei -l <file> useful for this." You do not appear to have acted on this. If you have, then please edit your question and add its output.
Sep 25, 2018 at 17:26 comment added wispi @MichaelHampton which comment are you referring to?
Sep 25, 2018 at 17:14 comment added Michael Hampton @wispi Please see my previous comment.
Sep 25, 2018 at 17:13 comment added wispi @Michael Hampton I have already set the permissions to execute and tried setting the owner to root.
Sep 25, 2018 at 17:02 comment added wispi @KevinO I’m using Debian, so SELinux is not available. As far as I know, AppArmor is not restricting anything.
Sep 25, 2018 at 15:13 comment added Michael Hampton @roaima It's Linux-specific. I'm not aware of any other Unix that has anything like it.
Sep 25, 2018 at 14:41 comment added Michael Hampton You need to check the permissions of the file and all of its containing directories. You may find namei -l <file> useful for this.
Sep 25, 2018 at 14:31 comment added KevinO Just to verify, no SELinux is running? Or if it is, the context is set correctly on the file? The directory where the file is locatedis also set to allow traversal, yes?
Sep 25, 2018 at 14:26 history asked wispi CC BY-SA 4.0