Do you have an idea what changed this behaviour?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1361124
Title:
Image is now writable by default in dual boot
To manage notifications about this bug go
** Summary changed:
- Image is now writable by default
+ Image is now writable by default in dual boot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1361124
Title:
Image is now writable by default
Yeah, unable to reproduce with krillin/mako when flashing with
bootstrap.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1361124
Title:
Image is now writable by default
To manage notifications about
This appears to happen only on dual-boot installs.
** Changed in: initramfs-tools-ubuntu-touch (Ubuntu)
Assignee: Jani Monoses (jani) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
** Changed in: initramfs-tools-ubuntu-touch (Ubuntu)
Assignee: (unassigned) => Jani Monoses (jani)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1361124
Title:
Image is now writable by default
** Description changed:
With recent images (tested 208), the root partition is now writable by
default:
phablet@ubuntu-phablet:~$ mount |grep '/ '
/dev/loop0 on / type ext2 (rw,relatime,errors=continue)
That's unexpeted and undesired. It also causes tests to actually install
test
