Public bug reported: as posted here . : https://answers.launchpad.net/ubuntu/+source/ubuntu-meta/+question/677407 https://askubuntu.com/questions/1061087/cryptsetup-warning-failed-to-detect-canonical-device-of or in 15 other places this bug has been around since 12.04 maybe it's time to do something about it?
no the fstab is clean : UUID=c013eec5-803b-11e8-ba28-7085c23e997f none swap sw 0 0 UUID=beb5eb23-803b-11e8-ba28-7085c23e997f / btrfs defaults 0 0 UUID=c013eec4-803b-11e8-ba28-7085c23e997f /srv xfs defaults 0 0 UUID=beb5eb22-803b-11e8-ba28-7085c23e997f /boot ext4 defaults 0 0 UUID=beb5eb24-803b-11e8-ba28-7085c23e997f /home ext4 defaults 0 0 UUID=78c4371d-5fc9-415f-a8a8-ba4a40cca1b6 /var/lib/docker btrfs defaults 0 1 UUID=b7cc90c8-d941-412c-bb51-e15b2a62e13b /media/stock ext4 defaults 0 2 and some NFS share the expected behavior should be that it doesn't read that any crypt is reported in fstab and so cryptsetup should stay silent like explained here https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671056 if the user need to say something to cryptsetup to tell it that it shouldn't be active for the moment or to give reference to cryptsetup to reassure it about where everything is but still doesn't need to act on anything... And yes I need overlayroot for testing and unfortunately it depends on cryptsetup. ** Affects: cryptsetup (Ubuntu) Importance: Undecided Status: New ** Also affects: cryptsetup (Ubuntu) Importance: Undecided Status: New ** No longer affects: ubuntu-meta (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1811064 Title: warning message of cryptsetup Status in cryptsetup package in Ubuntu: New Bug description: as posted here . : https://answers.launchpad.net/ubuntu/+source/ubuntu-meta/+question/677407 https://askubuntu.com/questions/1061087/cryptsetup-warning-failed-to-detect-canonical-device-of or in 15 other places this bug has been around since 12.04 maybe it's time to do something about it? no the fstab is clean : UUID=c013eec5-803b-11e8-ba28-7085c23e997f none swap sw 0 0 UUID=beb5eb23-803b-11e8-ba28-7085c23e997f / btrfs defaults 0 0 UUID=c013eec4-803b-11e8-ba28-7085c23e997f /srv xfs defaults 0 0 UUID=beb5eb22-803b-11e8-ba28-7085c23e997f /boot ext4 defaults 0 0 UUID=beb5eb24-803b-11e8-ba28-7085c23e997f /home ext4 defaults 0 0 UUID=78c4371d-5fc9-415f-a8a8-ba4a40cca1b6 /var/lib/docker btrfs defaults 0 1 UUID=b7cc90c8-d941-412c-bb51-e15b2a62e13b /media/stock ext4 defaults 0 2 and some NFS share the expected behavior should be that it doesn't read that any crypt is reported in fstab and so cryptsetup should stay silent like explained here https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671056 if the user need to say something to cryptsetup to tell it that it shouldn't be active for the moment or to give reference to cryptsetup to reassure it about where everything is but still doesn't need to act on anything... And yes I need overlayroot for testing and unfortunately it depends on cryptsetup. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1811064/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
