This isn't caused by ubiquity if it's at startup, since ubiquity would
only care about it w/r/t partitioning, and that hasn't been the case
since somewhere during the development cycle of 16.04 -- when we updated
partman-base to stop trying to partition rpmb devices.
Closing the ubiquity task as I
** Changed in: udisks (Ubuntu Precise)
Importance: Undecided => Low
** Changed in: udisks (Ubuntu Trusty)
Importance: Undecided => Low
** Changed in: systemd (Ubuntu Trusty)
Importance: Undecided => High
** Changed in: systemd (Ubuntu Trusty)
Assignee: (unassigned) => Martin Pitt (
** Also affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1333140
Title:
Fix udev rules to consider mmc rpmb par
This bug was fixed in the package systemd - 204-5ubuntu20.11
---
systemd (204-5ubuntu20.11) trusty; urgency=medium
[ Ben Howard ]
* Add debian/extra/rules/62-google-cloudimg.rules: Use "noop" scheduler for
Google virtio drives. (LP: #1420544)
[ Martin Pitt ]
* Add upstrea
No, this won't be backported. This is a classic bug fix for stable-
updates, I'll prepare uploads soon.
** Also affects: udev (Ubuntu)
Importance: Undecided
Status: New
** Also affects: udev (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: udisks (Ubuntu Pr
This bug was fixed in the package systemd - 218-10ubuntu1
---
systemd (218-10ubuntu1) vivid; urgency=medium
[ Martin Pitt ]
* Merge with Debian unstable. Remaining Ubuntu changes:
- Hack to support system-image read-only /etc, and modify files in
/etc/writable/ instead.
@Patrick: That's why:
IMPORT 'udisks-part-id /dev/mmcblk0rpmb' /lib/udev/rules.d/80-udisks.rules:84
starting 'udisks-part-id /dev/mmcblk0rpmb'
'udisks-part-id /dev/mmcblk0rpmb' [10806] exit with return code 0
Apparently you still have the old udisks 1.x installed; can you try
"sudo dpkg -P udisks
Which Ubuntu release and kernel version does that apply to? Please send
the uname -a output. Testing this under the current vivid kernel (3.18)
would be very much appreciated. Thanks!
** Package changed: udev (Ubuntu) => systemd (Ubuntu)
--
You received this bug notification because you are a me
