Bug#1027068: cryptsetup: syntax error, unexpected ERROR, expecting CCHAR or UNUMBER or AS
On Fri, Dec 30 2022, Konomi wrote: > I just did another round of updates and rebooted and could not > reproduce the bug so I leave it to more experienced users to determine > what should be done. Looks like this was fixed by console-setup 1.214 for #1027247
Bug#1027068: cryptsetup: syntax error, unexpected ERROR, expecting CCHAR or UNUMBER or AS
I just did another round of updates and rebooted and could not reproduce the bug so I leave it to more experienced users to determine what should be done.
Bug#1027068: cryptsetup: syntax error, unexpected ERROR, expecting CCHAR or UNUMBER or AS
> I wonder if Konomi can reproduce this? I haven't been able to reproduce it so far, but I haven't rebooted my computer yet. I still have the video of the error though so it's definitely an issue. > Is this possible to reassign this report to console-setup? I think this would be a good idea to investigate further, who knows if this bug will cause actual problems later.
Bug#1027068: cryptsetup: syntax error, unexpected ERROR, expecting CCHAR or UNUMBER or AS
Package: cryptsetup Version: 2:2.6.0-2 Followup-For: Bug #1027068 > There is no occurrence of ‘CCHAR’ or ‘UNUMBER’ in the source, so I > suspect this might be orthogonal to src:cryptsetup. Just FIY I was hit by the same. This happens before the vg password prompt, clearly something I would expect to find in initrd somewhere and sure enough CCHAR/UNUMBER are found inside "loadkeys" from the kbd package. This is run by setupcon: # loadkeys '/etc/console-setup/cached_UTF-8_del.kmap' syntax error, unexpected ERROR, expecting CCHAR or UNUMBER or AS even removing and regenerating the cached keymap results in the same. I wonder if Konomi can reproduce this? Is this possible to reassign this report to console-setup?
Bug#1027068: cryptsetup: syntax error, unexpected ERROR, expecting CCHAR or UNUMBER or AS
> There is no occurrence of ‘CCHAR’ or ‘UNUMBER’ in the source, so I > suspect this might be orthogonal to src:cryptsetup. You're right I'm not sure what's going on. I allowed the packages to update again and now there's no error, it just seems to have gone away on its own. I really hate when that happens. I'll open another bug report with no specific package if I see the error again. Sorry for the false report.
Bug#1027068: cryptsetup: syntax error, unexpected ERROR, expecting CCHAR or UNUMBER or AS
Control: tag -1 unreproducible moreinfo Hi, On Wed, 28 Dec 2022 at 00:41:05 +1100, Konomi Kitten wrote: > After doing the following updates: > > [UPGRADE] cryptsetup:amd64 2:2.6.0-1 -> 2:2.6.0-2 > [UPGRADE] cryptsetup-bin:amd64 2:2.6.0-1 -> 2:2.6.0-2 > [UPGRADE] cryptsetup-initramfs:amd64 2:2.6.0-1 -> 2:2.6.0-2 > [UPGRADE] libcryptsetup12:amd64 2:2.6.0-1 -> 2:2.6.0-2 Are you sure it was 2:2.6.0-1 → 2:2.6.0-2? The only change here is in the metadata (namely libcryptsetup-dev's Depends plus d/changelog). > I see the following error when my system starts just after the GRUB splash > screen: > > syntax error, unexpected ERROR, expecting CCHAR or UNUMBER or AS There is no occurrence of ‘CCHAR’ or ‘UNUMBER’ in the source, so I suspect this might be orthogonal to src:cryptsetup. Cheers, -- Guilhem. signature.asc Description: PGP signature
Bug#1027068: cryptsetup: syntax error, unexpected ERROR, expecting CCHAR or UNUMBER or AS
Package: cryptsetup Version: 2:2.6.0-2 Severity: normal X-Debbugs-Cc: konomikit...@gmail.com Dear Maintainer, After doing the following updates: [UPGRADE] cryptsetup:amd64 2:2.6.0-1 -> 2:2.6.0-2 [UPGRADE] cryptsetup-bin:amd64 2:2.6.0-1 -> 2:2.6.0-2 [UPGRADE] cryptsetup-initramfs:amd64 2:2.6.0-1 -> 2:2.6.0-2 [UPGRADE] libcryptsetup12:amd64 2:2.6.0-1 -> 2:2.6.0-2 I see the following error when my system starts just after the GRUB splash screen: syntax error, unexpected ERROR, expecting CCHAR or UNUMBER or AS Please note that it's hard to read this error and I only could take a video of it so I'm not sure of the exact message. After downgrading the packages the error message no longer appears. -- Package-specific info: -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-4-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cryptsetup depends on: ii cryptsetup-bin 2:2.6.0-1 ii debconf [debconf-2.0] 1.5.80 ii dmsetup2:1.02.185-2 ii libc6 2.36-7 cryptsetup recommends no packages. Versions of packages cryptsetup suggests: pn cryptsetup-initramfs ii dosfstools 4.2-1 pn keyutils ii liblocale-gettext-perl 1.07-5 -- debconf information: cryptsetup/prerm_active_mappings: true
