Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1130342 > unrolled thread

Bug#1027068: cryptsetup: syntax error, unexpected ERROR, expecting CCHAR or UNUMBER or AS

Back to article view | Back to linux.debian.bugs.dist

Contents

  Bug#1027068: cryptsetup: syntax error, unexpected ERROR, expecting CCHAR or UNUMBER or AS Konomi Kitten <konomikitten@gmail.com> - 2022-12-27 14:50 +0100
    Bug#1027068: cryptsetup: syntax error, unexpected ERROR, expecting CCHAR or UNUMBER or AS Guilhem Moulin <guilhem@debian.org> - 2022-12-27 15:10 +0100
    Bug#1027068: cryptsetup: syntax error, unexpected ERROR, expecting CCHAR or UNUMBER or AS Konomi <konomikitten@gmail.com> - 2022-12-27 16:00 +0100
    Bug#1027068: cryptsetup: syntax error, unexpected ERROR, expecting CCHAR or UNUMBER or AS Yuri D'Elia <wavexx@thregr.org> - 2022-12-29 12:20 +0100
      Bug#1027068: cryptsetup: syntax error, unexpected ERROR, expecting CCHAR or UNUMBER or AS Konomi <konomikitten@gmail.com> - 2022-12-30 03:10 +0100
        Bug#1027068: cryptsetup: syntax error, unexpected ERROR, expecting CCHAR or UNUMBER or AS Konomi <konomikitten@gmail.com> - 2022-12-30 04:30 +0100
          Bug#1027068: cryptsetup: syntax error, unexpected ERROR, expecting CCHAR or UNUMBER or AS Yuri D'Elia <wavexx@thregr.org> - 2022-12-30 11:40 +0100

#1130342 — 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: konomikitten@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  dmsetup                2:1.02.185-2
ii  libc6                  2.36-7

cryptsetup recommends no packages.

Versions of packages cryptsetup suggests:
pn  cryptsetup-initramfs    <none>
ii  dosfstools              4.2-1
pn  keyutils                <none>
ii  liblocale-gettext-perl  1.07-5

-- debconf information:
  cryptsetup/prerm_active_mappings: true

[toc] | [next] | [standalone]

#1130345

[Multipart message — attachments visible in raw view] — view raw

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.

[toc] | [prev] | [next] | [standalone]

#1130352

> 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.

[toc] | [prev] | [next] | [standalone]

#1130645

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?

[toc] | [prev] | [next] | [standalone]

#1130733

> 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.

[toc] | [prev] | [next] | [standalone]

#1130738

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.

[toc] | [prev] | [next] | [standalone]

#1130751

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

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web