| 2015-08-05 00:57:09 |
Brian Knoll |
bug |
|
|
added bug |
| 2015-08-06 20:53:01 |
Brian Knoll |
summary |
cryptsetup unknown fs type or options error decrypting LUKS volume at boot |
"cryptsetup: unknown fstype, bad password or options?" error decrypting LUKS volume at boot |
|
| 2015-08-06 21:00:45 |
Brian Knoll |
summary |
"cryptsetup: unknown fstype, bad password or options?" error decrypting LUKS volume at boot |
"cryptsetup: unknown fstype, bad password or options?" error unlocking / decrypting LUKS volume at boot |
|
| 2015-09-14 11:03:11 |
Launchpad Janitor |
cryptsetup (Ubuntu): status |
New |
Confirmed |
|
| 2015-09-18 00:36:04 |
Alberto Salvia Novella |
description |
Since upgrading to cryptsetup-1.6.6-5ubuntu1 to replace cryptsetup-1.6.1-1ubuntu7 today on my Ubuntu Wily 15.10 installation, I have been receiving an error message at boot time after entering my passphrase to unlock the LUKS partition. I noticed that at the same time the verbiage of the prompt to enter the passphrase also changed, to something like "Please unlock <devicename>", which is a little different than before, so I'm guessing something in this change may have caused the error message. Interestingly, the error message does not impede successful system boot, so my suspicion is that the error is maybe not real, but just being incorrectly displayed. In other words, if I successfully enter the passphrase, this error will appear but the system will then proceed to boot successfully and have the encrypted volume successfully mounted.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: cryptsetup 2:1.6.6-5ubuntu1
ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
Uname: Linux 4.1.0-3-generic x86_64
ApportVersion: 2.18-0ubuntu5
Architecture: amd64
Date: Tue Aug 4 20:46:55 2015
InstallationDate: Installed on 2015-05-28 (68 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: cryptsetup
UpgradeStatus: No upgrade log present (probably fresh install)
crypttab: sda3_crypt UUID=fe4c1c1f-252e-4bcc-904c-07896f9b1361 none luks,discard |
Since upgrading to cryptsetup-1.6.6-5ubuntu1 to replace cryptsetup-1.6.1-1ubuntu7 today on my Ubuntu Wily 15.10 installation, I have been receiving an error message at boot time after entering my passphrase to unlock the LUKS partition. I noticed that at the same time the verbiage of the prompt to enter the passphrase also changed, to something like "Please unlock <devicename>", which is a little different than before, so I'm guessing something in this change may have caused the error message.
Interestingly, the error message does not impede successful system boot, so my suspicion is that the error is maybe not real, but just being incorrectly displayed. In other words, if I successfully enter the passphrase, this error will appear but the system will then proceed to boot successfully and have the encrypted volume successfully mounted.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: cryptsetup 2:1.6.6-5ubuntu1
ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
Uname: Linux 4.1.0-3-generic x86_64
ApportVersion: 2.18-0ubuntu5
Architecture: amd64
Date: Tue Aug 4 20:46:55 2015
InstallationDate: Installed on 2015-05-28 (68 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: cryptsetup
UpgradeStatus: No upgrade log present (probably fresh install)
crypttab: sda3_crypt UUID=fe4c1c1f-252e-4bcc-904c-07896f9b1361 none luks,discard |
|
| 2015-09-18 00:36:21 |
Alberto Salvia Novella |
description |
Since upgrading to cryptsetup-1.6.6-5ubuntu1 to replace cryptsetup-1.6.1-1ubuntu7 today on my Ubuntu Wily 15.10 installation, I have been receiving an error message at boot time after entering my passphrase to unlock the LUKS partition. I noticed that at the same time the verbiage of the prompt to enter the passphrase also changed, to something like "Please unlock <devicename>", which is a little different than before, so I'm guessing something in this change may have caused the error message.
Interestingly, the error message does not impede successful system boot, so my suspicion is that the error is maybe not real, but just being incorrectly displayed. In other words, if I successfully enter the passphrase, this error will appear but the system will then proceed to boot successfully and have the encrypted volume successfully mounted.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: cryptsetup 2:1.6.6-5ubuntu1
ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
Uname: Linux 4.1.0-3-generic x86_64
ApportVersion: 2.18-0ubuntu5
Architecture: amd64
Date: Tue Aug 4 20:46:55 2015
InstallationDate: Installed on 2015-05-28 (68 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: cryptsetup
UpgradeStatus: No upgrade log present (probably fresh install)
crypttab: sda3_crypt UUID=fe4c1c1f-252e-4bcc-904c-07896f9b1361 none luks,discard |
Since upgrading to cryptsetup-1.6.6-5ubuntu1 to replace cryptsetup-1.6.1-1ubuntu7 today on my Ubuntu Wily 15.10 installation, I have been receiving an error message at boot time after entering my passphrase to unlock the LUKS partition.
I noticed that at the same time the verbiage of the prompt to enter the passphrase also changed, to something like "Please unlock <devicename>", which is a little different than before, so I'm guessing something in this change may have caused the error message.
Interestingly, the error message does not impede successful system boot, so my suspicion is that the error is maybe not real, but just being incorrectly displayed. In other words, if I successfully enter the passphrase, this error will appear but the system will then proceed to boot successfully and have the encrypted volume successfully mounted.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: cryptsetup 2:1.6.6-5ubuntu1
ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
Uname: Linux 4.1.0-3-generic x86_64
ApportVersion: 2.18-0ubuntu5
Architecture: amd64
Date: Tue Aug 4 20:46:55 2015
InstallationDate: Installed on 2015-05-28 (68 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: cryptsetup
UpgradeStatus: No upgrade log present (probably fresh install)
crypttab: sda3_crypt UUID=fe4c1c1f-252e-4bcc-904c-07896f9b1361 none luks,discard |
|
| 2015-09-18 00:37:01 |
Alberto Salvia Novella |
bug task added |
|
cryptsetup |
|
| 2015-09-18 00:37:10 |
Alberto Salvia Novella |
bug task added |
|
hundredpapercuts |
|
| 2015-09-18 00:37:18 |
Alberto Salvia Novella |
cryptsetup: status |
New |
Confirmed |
|
| 2015-09-18 00:37:21 |
Alberto Salvia Novella |
hundredpapercuts: status |
New |
Confirmed |
|
| 2015-09-18 00:37:25 |
Alberto Salvia Novella |
hundredpapercuts: importance |
Undecided |
High |
|
| 2015-09-18 00:37:26 |
Alberto Salvia Novella |
cryptsetup (Ubuntu): importance |
Undecided |
High |
|
| 2015-10-26 09:02:20 |
Tom Moorhouse |
bug |
|
|
added subscriber Tom Moorhouse |
| 2015-10-30 18:53:27 |
Richard Hansen |
bug |
|
|
added subscriber Richard Hansen |
| 2015-11-02 11:26:05 |
Raúl Martínez |
bug |
|
|
added subscriber Raúl Martínez |
| 2015-11-08 22:16:32 |
Moritz Baumann |
bug |
|
|
added subscriber Moritz Baumann |
| 2015-11-28 20:12:29 |
Alexander Geier |
attachment added |
|
Patch for /usr/share/initramfs-tools/scripts/local-top/cryptroot https://bugs.launchpad.net/cryptsetup/+bug/1481536/+attachment/4526849/+files/cryptroot.patch |
|
| 2015-11-28 20:17:23 |
Ubuntu Foundations Team Bug Bot |
tags |
amd64 apport-bug wily |
amd64 apport-bug patch wily |
|
| 2015-11-28 20:17:31 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Ubuntu Review Team |
| 2015-11-30 17:16:17 |
Brian Murray |
cryptsetup (Ubuntu): assignee |
|
Mathieu Trudel-Lapierre (mathieu-tl) |
|
| 2015-12-03 00:41:20 |
Richard Hansen |
attachment added |
|
call udev_settle() from activate_vg() https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1481536/+attachment/4528826/+files/do-udev-settle-after-activate-vg.patch |
|
| 2015-12-03 06:01:58 |
Steve Langasek |
attachment added |
|
cryptsetup-1481536.patch https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1481536/+attachment/4528850/+files/cryptsetup-1481536.patch |
|
| 2015-12-04 03:51:50 |
Richard Hansen |
attachment added |
|
cryptsetup-1481536-v2.patch https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1481536/+attachment/4529355/+files/cryptsetup-1481536-v2.patch |
|
| 2015-12-16 01:30:33 |
Christian Schrader |
bug |
|
|
added subscriber Christian Schrader |
| 2015-12-17 00:27:14 |
Richard Hansen |
attachment added |
|
cryptsetup-1481536-v3.patch https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1481536/+attachment/4535984/+files/cryptsetup-1481536-v3.patch |
|
| 2016-01-05 18:48:33 |
jpiesing |
bug |
|
|
added subscriber jpiesing |
| 2016-01-19 18:28:47 |
Jeff Foster |
bug |
|
|
added subscriber Jeff Foster |
| 2016-04-28 08:46:32 |
Richard Hansen |
attachment added |
|
cryptsetup-1481536-v4.patch https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1481536/+attachment/4649908/+files/cryptsetup-1481536-v4.patch |
|
| 2016-12-16 02:31:33 |
Mathieu Trudel-Lapierre |
cryptsetup (Ubuntu): milestone |
|
ubuntu-17.01 |
|
| 2017-02-01 20:28:24 |
Mathieu Trudel-Lapierre |
cryptsetup (Ubuntu): milestone |
ubuntu-17.01 |
ubuntu-17.02 |
|
| 2019-03-02 10:45:34 |
Albert |
summary |
"cryptsetup: unknown fstype, bad password or options?" error unlocking / decrypting LUKS volume at boot |
What is the street value of tramadol 100mg? |
|
| 2019-03-02 10:47:10 |
Albert |
description |
Since upgrading to cryptsetup-1.6.6-5ubuntu1 to replace cryptsetup-1.6.1-1ubuntu7 today on my Ubuntu Wily 15.10 installation, I have been receiving an error message at boot time after entering my passphrase to unlock the LUKS partition.
I noticed that at the same time the verbiage of the prompt to enter the passphrase also changed, to something like "Please unlock <devicename>", which is a little different than before, so I'm guessing something in this change may have caused the error message.
Interestingly, the error message does not impede successful system boot, so my suspicion is that the error is maybe not real, but just being incorrectly displayed. In other words, if I successfully enter the passphrase, this error will appear but the system will then proceed to boot successfully and have the encrypted volume successfully mounted.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: cryptsetup 2:1.6.6-5ubuntu1
ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
Uname: Linux 4.1.0-3-generic x86_64
ApportVersion: 2.18-0ubuntu5
Architecture: amd64
Date: Tue Aug 4 20:46:55 2015
InstallationDate: Installed on 2015-05-28 (68 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: cryptsetup
UpgradeStatus: No upgrade log present (probably fresh install)
crypttab: sda3_crypt UUID=fe4c1c1f-252e-4bcc-904c-07896f9b1361 none luks,discard |
Since upgrading to cryptsetup-1.6.6-5ubuntu1 to replace cryptsetup-1.6.1-1ubuntu7 today on my Ubuntu Wily 15.10 installation, I have been receiving an error message at boot time after entering my passphrase to unlock the LUKS partition.
https://usapillspharma.com/
I noticed that at the same time the verbiage of the prompt to enter the passphrase also changed, to something like "Please unlock <devicename>", which is a little different than before, so I'm guessing something in this change may have caused the error message.
https://yourrxpills.com/
Interestingly, the error message does not impede successful system boot, so my suspicion is that the error is maybe not real, but just being incorrectly displayed. In other words, if I successfully enter the passphrase, this error will appear but the system will then proceed to boot successfully and have the encrypted volume successfully mounted.
https://rxsecureweb.com
https://pharmacyonline247.com/
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: cryptsetup 2:1.6.6-5ubuntu1
ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
Uname: Linux 4.1.0-3-generic x86_64
ApportVersion: 2.18-0ubuntu5
Architecture: amd64
Date: Tue Aug 4 20:46:55 2015
InstallationDate: Installed on 2015-05-28 (68 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: cryptsetup
UpgradeStatus: No upgrade log present (probably fresh install)
crypttab: sda3_crypt UUID=fe4c1c1f-252e-4bcc-904c-07896f9b1361 none luks,discard |
|
| 2019-03-02 13:22:41 |
Steve Langasek |
summary |
What is the street value of tramadol 100mg? |
"cryptsetup: unknown fstype, bad password or options?" error unlocking / decrypting LUKS volume at boot |
|
| 2019-03-02 13:23:30 |
Steve Langasek |
description |
Since upgrading to cryptsetup-1.6.6-5ubuntu1 to replace cryptsetup-1.6.1-1ubuntu7 today on my Ubuntu Wily 15.10 installation, I have been receiving an error message at boot time after entering my passphrase to unlock the LUKS partition.
https://usapillspharma.com/
I noticed that at the same time the verbiage of the prompt to enter the passphrase also changed, to something like "Please unlock <devicename>", which is a little different than before, so I'm guessing something in this change may have caused the error message.
https://yourrxpills.com/
Interestingly, the error message does not impede successful system boot, so my suspicion is that the error is maybe not real, but just being incorrectly displayed. In other words, if I successfully enter the passphrase, this error will appear but the system will then proceed to boot successfully and have the encrypted volume successfully mounted.
https://rxsecureweb.com
https://pharmacyonline247.com/
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: cryptsetup 2:1.6.6-5ubuntu1
ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
Uname: Linux 4.1.0-3-generic x86_64
ApportVersion: 2.18-0ubuntu5
Architecture: amd64
Date: Tue Aug 4 20:46:55 2015
InstallationDate: Installed on 2015-05-28 (68 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: cryptsetup
UpgradeStatus: No upgrade log present (probably fresh install)
crypttab: sda3_crypt UUID=fe4c1c1f-252e-4bcc-904c-07896f9b1361 none luks,discard |
Since upgrading to cryptsetup-1.6.6-5ubuntu1 to replace cryptsetup-1.6.1-1ubuntu7 today on my Ubuntu Wily 15.10 installation, I have been receiving an error message at boot time after entering my passphrase to unlock the LUKS partition.
I noticed that at the same time the verbiage of the prompt to enter the passphrase also changed, to something like "Please unlock <devicename>", which is a little different than before, so I'm guessing something in this change may have caused the error message.
Interestingly, the error message does not impede successful system boot, so my suspicion is that the error is maybe not real, but just being incorrectly displayed. In other words, if I successfully enter the passphrase, this error will appear but the system will then proceed to boot successfully and have the encrypted volume successfully mounted.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: cryptsetup 2:1.6.6-5ubuntu1
ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
Uname: Linux 4.1.0-3-generic x86_64
ApportVersion: 2.18-0ubuntu5
Architecture: amd64
Date: Tue Aug 4 20:46:55 2015
InstallationDate: Installed on 2015-05-28 (68 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: cryptsetup
UpgradeStatus: No upgrade log present (probably fresh install)
crypttab: sda3_crypt UUID=fe4c1c1f-252e-4bcc-904c-07896f9b1361 none luks,discard |
|
