I think I didn't quite know how to restart rsyslog :^(
I'm tired now but maybe I'll try just using "ubiquity -d" tomorrow.
Look, I'm no dev by any means, but I believe this bug is tagged wrong! It's much more likely a ubiquity bug than a kernel bug, and it is "critical"! Colin Watson would know how to properly assign this :^)
I fell on my face performing this:
https:/ /wiki.ubuntu. com/DebuggingUb iquity# Deeper_ debugging_ of_partman
I think I didn't quite know how to restart rsyslog :^(
I'm tired now but maybe I'll try just using "ubiquity -d" tomorrow.
Look, I'm no dev by any means, but I believe this bug is tagged wrong! It's much more likely a ubiquity bug than a kernel bug, and it is "critical"! Colin Watson would know how to properly assign this :^)