Your message dated Fri, 3 May 2024 13:29:51 -0400
with message-id <cd98c1fb-5cef-4f45-bd60-73611af51...@queued.net>
and subject line Re: Fails to start with undefined symbol
has caused the Debian Bug report #1070227,
regarding Fails to start with undefined symbol
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1070227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070227
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 124.0.6367.78-1
Severity: grave
The current package in debian unstable fails to start with the following
missing symbol:
$ chromium
grep: warning: stray \ before -
/usr/lib/chromium/chromium: symbol lookup error: /usr/lib/chromium/chromium:
undefined symbol: _ZN6snappy11RawCompressEPKcmPcPm
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.7.12-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages chromium depends on:
ii chromium-common 124.0.6367.78-1
ii libasound2t64 1.2.11-1+b1
ii libatk-bridge2.0-0t64 2.52.0-1
ii libatk1.0-0t64 2.52.0-1
ii libatomic1 14-20240429-1
ii libatspi2.0-0t64 2.52.0-1
ii libc6 2.38-6
ii libcairo2 1.18.0-3+b1
ii libcups2t64 2.4.7-1.2+b1
ii libdbus-1-3 1.14.10-4+b1
ii libdouble-conversion3 3.3.0-1+b1
ii libdrm2 2.4.120-2
ii libevent-2.1-7t64 2.1.12-stable-8.1+b3
ii libexpat1 2.6.2-1
ii libflac12t64 1.4.3+ds-2.1
ii libfontconfig1 2.15.0-1.1
ii libfreetype6 2.13.2+dfsg-1+b4
ii libgbm1 24.1.0~rc1-1
ii libgcc-s1 14-20240429-1
ii libglib2.0-0t64 2.78.4-7
ii libgtk-3-0t64 3.24.41-4
ii libjpeg62-turbo 1:2.1.5-3
ii libjsoncpp25 1.9.5-6+b2
ii liblcms2-2 2.14-2+b1
ii libminizip1t64 1:1.3.dfsg-3.1
ii libnspr4 2:4.35-1.1+b1
ii libnss3 2:3.99-1
ii libopenh264-7 2.4.1+dfsg-1
ii libopenjp2-7 2.5.0-2+b3
ii libopus0 1.4-1+b1
ii libpango-1.0-0 1.52.1+ds-1
ii libpng16-16t64 1.6.43-5
ii libpulse0 16.1+dfsg1-5
ii libsnappy1v5 1.2.0-1
ii libstdc++6 14-20240429-1
ii libwoff1 1.0.2-2+b1
ii libx11-6 2:1.8.7-1+b1
ii libxcb1 1.17.0-1
ii libxcomposite1 1:0.4.5-1+b1
ii libxdamage1 1:1.1.6-1+b1
ii libxext6 2:1.3.4-1+b1
ii libxfixes3 1:6.0.0-2+b1
ii libxkbcommon0 1.6.0-1+b1
ii libxml2 2.9.14+dfsg-1.3+b3
ii libxnvctrl0 535.171.04-1
ii libxrandr2 2:1.5.4-1
ii libxslt1.1 1.1.35-1+b1
ii zlib1g 1:1.3.dfsg-3.1
Versions of packages chromium recommends:
pn chromium-sandbox <none>
Versions of packages chromium suggests:
pn chromium-driver <none>
pn chromium-l10n <none>
pn chromium-shell <none>
Versions of packages chromium-common depends on:
ii libc6 2.38-6
ii libdrm2 2.4.120-2
ii libjsoncpp25 1.9.5-6+b2
ii libstdc++6 14-20240429-1
ii libx11-6 2:1.8.7-1+b1
ii libxnvctrl0 535.171.04-1
ii x11-utils 7.7+6+b1
ii xdg-utils 1.1.3-4.1
ii zlib1g 1:1.3.dfsg-3.1
Versions of packages chromium-common recommends:
pn chromium-sandbox <none>
ii dunst [notification-daemon] 1.11.0-1
ii fonts-liberation 1:2.1.5-3
ii libgl1-mesa-dri 24.1.0~rc1-1
pn libu2f-udev <none>
pn system-config-printer <none>
pn upower <none>
--- End Message ---
--- Begin Message ---
Safe to close now.
On Thu, 2 May 2024 13:56:52 -0400 Andres Salomon <dilin...@queued.net>
wrote:
Thanks. This is a duplicate (https://bugs.debian.org/1070217), but I'm
leaving it open to ensure that chromium doesn't accidentally migrate to
trixie while built against a broken libsnappy. And as a reminder that
we'll probably need a binNMU once snappy is fixed, unless upstream has a
new release
On Thu, 2 May 2024 10:57:25 +0200 Yuri D'Elia <wav...@thregr.org> wrote:
> Package: chromium
> Version: 124.0.6367.78-1
> Severity: grave
>
> The current package in debian unstable fails to start with the following
> missing symbol:
>
> $ chromium
> grep: warning: stray \ before -
> /usr/lib/chromium/chromium: symbol lookup error: /usr/lib/chromium/chromium:
undefined symbol: _ZN6snappy11RawCompressEPKcmPcPm
>
>
> -- System Information:
> Debian Release: trixie/sid
> APT prefers unstable
> APT policy: (900, 'unstable'), (800, 'experimental'), (500,
'unstable-debug')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 6.7.12-amd64 (SMP w/16 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
> Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages chromium depends on:
> ii chromium-common 124.0.6367.78-1
> ii libasound2t64 1.2.11-1+b1
> ii libatk-bridge2.0-0t64 2.52.0-1
> ii libatk1.0-0t64 2.52.0-1
> ii libatomic1 14-20240429-1
> ii libatspi2.0-0t64 2.52.0-1
> ii libc6 2.38-6
> ii libcairo2 1.18.0-3+b1
> ii libcups2t64 2.4.7-1.2+b1
> ii libdbus-1-3 1.14.10-4+b1
> ii libdouble-conversion3 3.3.0-1+b1
> ii libdrm2 2.4.120-2
> ii libevent-2.1-7t64 2.1.12-stable-8.1+b3
> ii libexpat1 2.6.2-1
> ii libflac12t64 1.4.3+ds-2.1
> ii libfontconfig1 2.15.0-1.1
> ii libfreetype6 2.13.2+dfsg-1+b4
> ii libgbm1 24.1.0~rc1-1
> ii libgcc-s1 14-20240429-1
> ii libglib2.0-0t64 2.78.4-7
> ii libgtk-3-0t64 3.24.41-4
> ii libjpeg62-turbo 1:2.1.5-3
> ii libjsoncpp25 1.9.5-6+b2
> ii liblcms2-2 2.14-2+b1
> ii libminizip1t64 1:1.3.dfsg-3.1
OpenPGP_0x645D0247C36E7637.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
