This issue has been fixed in 0.44.12-2. The problem was, that on SIGTERM
the dwarf-fortress wrapper script tried to unmount the temporary
unionfs-fuse mount point and then recursively delete it. When the
unmounting step failed the script would still try to delete the
directory afterwards and the unionfs-fuse mount propagated all deletes
into the user run directory. The new version doesn't use unionfs-fuse
anymore, so the problem doesn't occur anymore.
** Changed in: dwarf-fortress (Ubuntu)
Assignee: (unassigned) => Sven Bartscher (kritzefitz)
** Changed in: dwarf-fortress (Ubuntu)
Status: New => Confirmed
** Changed in: dwarf-fortress (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796602
Title:
Sending SIGINT to dwarf-fortress startup script wreaks major fun on
user's local configurations
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dwarf-fortress/+bug/1796602/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
