./daedalus-5.3.1-66691-mainnet-f14275aa5-x86_64-linux.bin
Cannot bind mount /dev to /tmp/nixxdqYmx/dev: Permission denied
Cannot bind mount /proc to /tmp/nixxdqYmx/proc: Permission denied
Cannot bind mount /sys to /tmp/nixxdqYmx/sys: Permission denied
Cannot bind mount /run to /tmp/nixxdqYmx/run: Permission denied
Cannot bind mount /tmp to /tmp/nixxdqYmx/tmp: Permission denied
Cannot bind mount /var to /tmp/nixxdqYmx/var: Permission denied
Cannot bind mount /etc to /tmp/nixxdqYmx/etc: Permission denied
Cannot bind mount /usr to /tmp/nixxdqYmx/usr: Permission denied
Cannot bind mount /home to /tmp/nixxdqYmx/home: Permission denied
Cannot bind mount /home to /tmp/nixxdqYmx//home: Permission denied
mount(/tmp/tmpx-20240516T000407Z-dbb8da50/dat/nix, /tmp/nixxdqYmx/nix): Permission denied
I try to follow the solution from the post
with no success
This is a fresh installation before, I was using Manjaro with no problem.
Can you help me solve this?
I just upgraded my laptop to Ubuntu 24.04 and ran into this exact problem. For me, just stopping apparmor service did not help. If you search /var/log/syslog for DENIED you can find the apparmor profile that is causing the issue. This was in my log:
I do not yet know enough about apparmor to know if this causes some sort of security issue, but for now at least I can run daedalus.
I did try setting the daedalus program to just “complain” mode but received a python error. So it appears maybe the utility has some bugs in it. This is why I opted to just disable the problematic profile for now. sudo aa-complain <path-to-daedalus>
I feel like this is not likely a good solution but just a temporary workaround until somebody more knowledgeable of apparmor can suggest a better approach. I hope this helps somebody.