Sorry to chime in again, but I have discovered that I have given wrong information, and I want to correct it. I have thought that prepending "sudo" to your commands has solved the problem, but I have gained that impression after logging out from a session where I have sourced .profile manually, and then logged back back in. The mounts seem to survive the log-out-log-in cycle, regardless of the presence of "sudo", but after rebooting, the commands don't work. Without "sudo" there is nothing to be seen in the boot log, but with it, the following message can be seen for each mounting command:I could not find any way to have sddm extend the sudo privilege to .profile, so your polkit method seems mandatory here.
But until I will be ready to "mess" with polkit, I have reached the same effect (may be global though, but on a single-user machine, I think it's acceptable) by adding the following lines to /etc/fstab:
Code:
Nov 04 16:14:58 di7 sudo[2404]: pam_unix(sudo:auth): conversation failed Nov 04 16:14:58 di7 sudo[2404]: pam_unix(sudo:auth): auth could not identify password for [tiberius]But until I will be ready to "mess" with polkit, I have reached the same effect (may be global though, but on a single-user machine, I think it's acceptable) by adding the following lines to /etc/fstab:
Code:
tmpfs /home/tiberius/.cache/mozilla tmpfs defaults,size=100M 0 0tmpfs /home/tiberius/.cache/gdb tmpfs defaults,size=50M 0 0Statistics: Posted by TiberiusKG — 2024-11-04 14:39