[Bug 1847919] Re: Adiantum cipher cannot be specified in the /etc/crypttab
Since 2:2.0.3-5 you can use ‘cipher=foo\054bar’ to set cryptsetup(8)'s cipher spec string to ‘foo,bar’. ** Changed in: cryptsetup (Ubuntu) Status: New => Fix Released ** Changed in: cryptsetup (Ubuntu) Assignee: (unassigned) => Kendek (nemh) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847919 Title: Adiantum cipher cannot be specified in the /etc/crypttab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1847919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847919] [NEW] Adiantum cipher cannot be specified in the /etc/crypttab
Public bug reported: In the /etc/crypttab file the fourth, options field separates each option with a comma. The xchacha12,aes-adiantum-plain64 xchacha20,aes-adiantum-plain64 valid ciphers cannot be specified in the options field, because the comma is misinterpreted. The error message is: > cryptdisks_start cryptsetup: WARNING: : ignoring unknown option 'aes-adiantum-plain64' ** Affects: cryptsetup (Ubuntu) Importance: Undecided Status: New ** Tags: adiantum cryptsetup ** Also affects: cryptsetup (Ubuntu) Importance: Undecided Status: New ** No longer affects: errors -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847919 Title: Adiantum cipher cannot be specified in the /etc/crypttab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1847919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1507002] Re: "boot error" due to gcc v5 transition
This problem is fixed in the version 6.03+dfsg-11ubuntu1, see the changelog: http://changelogs.ubuntu.com/changelogs/pool/main/s/syslinux/syslinux_6.03+dfsg-11ubuntu1/changelog The new version is working well on the Ubuntu 16.04 LTS, but the available version in the 15.10 (-8ubuntu2) is still broken: http://packages.ubuntu.com/wily/syslinux So the Syslinux on the Ubuntu 15.10 is not fixed! If you want just install the packages from here: http://packages.ubuntu.com/xenial/syslinux http://packages.ubuntu.com/xenial/syslinux-common sudo dpkg -i *.deb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507002 Title: "boot error" due to gcc v5 transition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/syslinux/+bug/1507002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1511988] [NEW] Boot error with Syslinux (Ubuntu 15.10)
Public bug reported: After I executing the following command on the Ubuntu 15.10 amd64, the Live system on the USB device does not boot with legacy BIOS: sudo syslinux -i /dev/sdXN I get this error message: SYSLINUX 6.03 EDD 20150813 Copyright (C) 1994-2014 H. Peter Anvin et al Boot error If I try the same command with 15.04 (without any file modifications on the USB device), the Syslinux boot menu appears. This issue affects the Systemback (bug #1511964). ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: syslinux 3:6.03+dfsg-8ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 31 18:59:23 2015 Dependencies: gcc-5-base 5.2.1-22ubuntu2 libc6 2.21-0ubuntu4 libgcc1 1:5.2.1-22ubuntu2 mtools 4.0.18-2 syslinux-common 3:6.03+dfsg-8ubuntu2 SourcePackage: syslinux UpgradeStatus: Upgraded to wily on 2015-03-29 (216 days ago) ** Affects: syslinux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1511988 Title: Boot error with Syslinux (Ubuntu 15.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/syslinux/+bug/1511988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1511988] Re: Boot error with Syslinux (Ubuntu 15.10)
Sorry, this bug is already reported: https://bugs.launchpad.net/ubuntu/+source/syslinux/+bug/1507002 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1511988 Title: Boot error with Syslinux (Ubuntu 15.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/syslinux/+bug/1511988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1511988] Re: Boot error with Syslinux (Ubuntu 15.10)
*** This bug is a duplicate of bug 1507002 *** https://bugs.launchpad.net/bugs/1507002 ** This bug has been marked a duplicate of bug 1507002 "boot error" is back! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1511988 Title: Boot error with Syslinux (Ubuntu 15.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/syslinux/+bug/1511988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1338706] Re: Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to set xfermode (err_mask=0x40) on upstream kernels = 3.12
So, I already use the proposed (3.19.0-22-generic) kernel on Vivid Vervet, I installed it days ago. The discard mount option and the fstrim command are works now, without any problem. Please do not drop the path, but move this kernel to the stable repository. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1338706 Title: Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to set xfermode (err_mask=0x40) on upstream kernels = 3.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1338706] Re: Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to set xfermode (err_mask=0x40) on upstream kernels = 3.12
** Tags removed: verification-needed-vivid ** Tags added: verification-done-vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1338706 Title: Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to set xfermode (err_mask=0x40) on upstream kernels = 3.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1449005] Re: trim does not work with Samsung 840 EVO after firmware update (EXT0DB6Q)
Yeah, just use -v option for print number of discarded bytes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1449005 Title: trim does not work with Samsung 840 EVO after firmware update (EXT0DB6Q) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fstrim/+bug/1449005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
