It is not an Ubuntu thing: other distros have already done that before, like Fedora or Arch. There are several reasons for it, including security ones. Anyway, even if you are using a removable media to store binaries or scripts, probably you should mount them at a fixed point by modifying your fstab file, instead of relying on the dynamically created paths by udisks2. By adding the "nofail" option, it won't return an error if the media isn't connected during boot and startup. Since you are using SATA disks, you can just add an entry for the specific partition you need (but use the partition UUID, not the device path), setting the "/media/$USER/$PARTIDION_UUID" folder as the mount point. That should solve your problem while retaining the advantages of using /run/media for the rest of dynamically mounted devices.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2153531 Title: Ubuntu 26.04 After upgrade desktop items do not launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-ubuntu-extensions/+bug/2153531/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
