Am 27.08.20 um 14:30 schrieb Thorsten Kukuk:
The problem is another one: why does nobody remember that he created the tmp.mount symlink? This got never created by an openSUSE package, if you have a tmp.mount symlink on your system, you created it yourself once in the past.
So reporting bugs about this is needless, there is nothing we can do as the symlink is not coming from an openSUSE package.
Thorsten
Are you 100% sure? As I wrote yesterday, I was surprised that I had the symlink and had to delete it. I remember visiting the wiki after the announcement on Aug 13 and migrating according of what I read. Now yesterday I assumed I had misread something. But because so many more users report the same problem, I just looked into my shell HISTFILE: - I see the commands which I used to backup and delete the btrfs /tmp subvol. - I see the commands editing and checking the fstab. - I see the systemctl commands to disable systemd-tmpfiles-clean.timer and .service. - I do NOT see any commands creating a symlink through ln or systemctl. And things worked fine with /tmp on tmpfs between Aug 13 and last Monday/Tuesday. *Something* must have changed on the system update last Monday. Regards, Ben -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org