Public bug reported:
While the dwarf-fortress python script is running, abruptly terminating
the script with SIGINT (for example, through pressing Ctrl+C in the
console) somehow causes the unionfs system to unleash nearly
irreparable(?) damage on the user's local game configuration files in
`~/.local/share/dwarf-fortress/`, in turn preventing the script from
successfully running again without deleting the local `dwarf-fortress`
directory.
Curiously, the issue doesn't seem to occur when using SIGTERM or
SIGKILL.
** Affects: dwarf-fortress (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Abruptly terminating dwarf-fortress startup causes major fun to user's local
configurations
+ Sending SIGINT to dwarf-fortress startup script wreaks major fun on user's
local configurations
--
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
