Processed: affects 979590
Processing commands for cont...@bugs.debian.org: > affects 979590 chromium Bug #979590 [libx11] libx11 possible ABI break in libx11 breaks libx11-xcb1 and that breaks chromium Bug #979618 [libx11] libx11 possible ABI break in libx11 breaks libx11-xcb1 and that breaks chromium Added indication that 979590 affects chromium Added indication that 979618 affects chromium > thanks Stopping processing here. Please contact me if you need assistance. -- 979590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979590 979618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979618 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#979590: libx11-xcb1: Updating to 1.7.0-1 from 1.6.12-1 breaks chromium and google chrome
Re: Faidon Liambotis > It turned out that for me, the cause was a disparity between libx11-xcb1 > and libx11-6 -- the former was at 2:1.7.0-1, while the latter was at > 2:1.6.12-1 (don't ask why...). I had the same here on testing+unstable (the latter on lower pin priority), and upgrading libx11-6 fixed the problem. chromium depends on libx11-6 (>= 2:1.4.99.1), libx11-xcb1 (>= 2:1.7.0) which explains why only libx11-xcb1 got pulled from unstable. Christoph
[Git][xorg-team/lib/libx11][debian-unstable] 3 commits: Set a strict dependency of libx11-xcb1 on libx11-6
Julien Cristau pushed to branch debian-unstable at X Strike Force / lib / libx11
Commits:
2659e872 by Julien Cristau at 2021-01-11T12:26:19+01:00
Set a strict dependency of libx11-xcb1 on libx11-6
Internal ABI may change across releases - and indeed did change between
1.6.12 and 1.7.0 (closes: #979590)
- - - - -
46825070 by Julien Cristau at 2021-01-11T12:26:21+01:00
Update upstream git URL in package descriptions.
- - - - -
4e9fa0e9 by Julien Cristau at 2021-01-11T12:26:22+01:00
Upload to unstable
- - - - -
2 changed files:
- debian/changelog
- debian/control
Changes:
=
debian/changelog
=
@@ -1,3 +1,12 @@
+libx11 (2:1.7.0-2) unstable; urgency=medium
+
+ * Set a strict dependency of libx11-xcb1 on libx11-6, as internal ABI
+may change across releases - and indeed did change between 1.6.12 and
+1.7.0 (closes: #979590)
+ * Update upstream git URL in package descriptions.
+
+ -- Julien Cristau Mon, 11 Jan 2021 12:15:25 +0100
+
libx11 (2:1.7.0-1) unstable; urgency=medium
* New upstream release.
=
debian/control
=
@@ -38,7 +38,7 @@ Description: X11 client-side library
https://www.X.org>
.
This module can be found at
- git://anongit.freedesktop.org/git/xorg/lib/libX11
+ https://gitlab.freedesktop.org/xorg/lib/libX11
Package: libx11-6-udeb
XC-Package-Type: udeb
@@ -63,7 +63,7 @@ Description: X11 client-side library
https://www.X.org>
.
This module can be found at
- git://anongit.freedesktop.org/git/xorg/lib/libX11
+ https://gitlab.freedesktop.org/xorg/lib/libX11
Package: libx11-dev
Section: libdevel
@@ -92,7 +92,7 @@ Description: X11 client-side library (development headers)
https://www.X.org>
.
This module can be found at
- git://anongit.freedesktop.org/git/xorg/lib/libX11
+ https://gitlab.freedesktop.org/xorg/lib/libX11
Package: libx11-xcb1
Section: libs
@@ -100,6 +100,7 @@ Architecture: any
Depends:
${shlibs:Depends},
${misc:Depends},
+ libx11-6 (= ${binary:Version}),
Pre-Depends: ${misc:Pre-Depends}
Multi-Arch: same
Description: Xlib/XCB interface library
@@ -113,7 +114,7 @@ Description: Xlib/XCB interface library
https://xcb.freedesktop.org>
.
This module can be found at
- git://anongit.freedesktop.org/git/xorg/lib/libX11
+ https://gitlab.freedesktop.org/xorg/lib/libX11
Package: libx11-xcb-dev
Section: libdevel
@@ -139,7 +140,7 @@ Description: Xlib/XCB interface library (development
headers)
https://xcb.freedesktop.org>
.
This module can be found at
- git://anongit.freedesktop.org/git/xorg/lib/libX11
+ https://gitlab.freedesktop.org/xorg/lib/libX11
Package: libx11-doc
Section: doc
@@ -161,4 +162,4 @@ Description: X11 client-side library (development
documentation)
https://www.X.org>
.
This module can be found at
- git://anongit.freedesktop.org/git/xorg/lib/libX11
+ https://gitlab.freedesktop.org/xorg/lib/libX11
View it on GitLab:
https://salsa.debian.org/xorg-team/lib/libx11/-/compare/a650a288591048cf28b16bb80487b88ef27a7468...4e9fa0e9be249cf4bdf1a4e8b131519ada91afbb
--
View it on GitLab:
https://salsa.debian.org/xorg-team/lib/libx11/-/compare/a650a288591048cf28b16bb80487b88ef27a7468...4e9fa0e9be249cf4bdf1a4e8b131519ada91afbb
You're receiving this email because of your account on salsa.debian.org.
[Git][xorg-team/lib/libx11] Pushed new tag libx11-2_1.7.0-2
Julien Cristau pushed new tag libx11-2_1.7.0-2 at X Strike Force / lib / libx11 -- View it on GitLab: https://salsa.debian.org/xorg-team/lib/libx11/-/tree/libx11-2_1.7.0-2 You're receiving this email because of your account on salsa.debian.org.
Processing of libx11_1.7.0-2_source.changes
libx11_1.7.0-2_source.changes uploaded successfully to localhost along with the files: libx11_1.7.0-2.dsc libx11_1.7.0-2.diff.gz Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#979590: marked as done (libx11 possible ABI break in libx11 breaks libx11-xcb1 and that breaks chromium)
Your message dated Mon, 11 Jan 2021 11:54:20 + with message-id and subject line Bug#979590: fixed in libx11 2:1.7.0-2 has caused the Debian Bug report #979590, regarding libx11 possible ABI break in libx11 breaks libx11-xcb1 and that breaks chromium 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.) -- 979590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979590 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libx11-xcb1 Version: 2:1.7.0-1 Severity: normal X-Debbugs-Cc: mic...@lebihan.pl Dear Maintainer, After updating libx11-xcb1 chromium and google chrome UI is not responding to any input and clicking anywhere on the app window causes the GNOME app is not responding dialog to appear. The app actually is not frozen because if you pass a URL with dynamic web content as a parameter, it will be constantly updated. I didn't notice any other affected app, but I didn't test much. Michel Le Bihan -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (700, 'testing'), (650, 'unstable'), (600, 'experimental'), (500, 'unstable-debug'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-5-amd64 (SMP w/4 CPU threads) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- no debconf information --- End Message --- --- Begin Message --- Source: libx11 Source-Version: 2:1.7.0-2 Done: Julien Cristau We believe that the bug you reported is fixed in the latest version of libx11, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julien Cristau (supplier of updated libx11 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 11 Jan 2021 12:15:25 +0100 Source: libx11 Architecture: source Version: 2:1.7.0-2 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Julien Cristau Closes: 979590 Changes: libx11 (2:1.7.0-2) unstable; urgency=medium . * Set a strict dependency of libx11-xcb1 on libx11-6, as internal ABI may change across releases - and indeed did change between 1.6.12 and 1.7.0 (closes: #979590) * Update upstream git URL in package descriptions. Checksums-Sha1: 9d7689b4f621e72e48cc225a5986b123b5102b98 2564 libx11_1.7.0-2.dsc f0294ed61e0ce05da05d1f7ea3682536e0f5ae96 73844 libx11_1.7.0-2.diff.gz Checksums-Sha256: 1540dcbbbdf7e08405d133127ca6f63fe191a3946ae9c5afc95293bc12f784a1 2564 libx11_1.7.0-2.dsc 910d4a1527458ff020f0bab9df55bab44d63db8247543d2b2256c7b258ce439c 73844 libx11_1.7.0-2.diff.gz Files: e8781a3e2d7accd1f2057d91a5940570 2564 x11 optional libx11_1.7.0-2.dsc f8911845bfd953f82a3ef1ac0697e022 73844 x11 optional libx11_1.7.0-2.diff.gz -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEVXgdqzTmGgnvuIvhnbAjVVb4z60FAl/8NhYUHGpjcmlzdGF1 QGRlYmlhbi5vcmcACgkQnbAjVVb4z61cYg/5AeB5A0SF/qCS2fCCaADJOla4RJlH HZPna/MmPxIonahyZ3caCuhJ+7etZdq9vAyGLqoy4wLyYWp3Xbq4Htx0TFDxGBHD qA0OTW7QmhrlrIs3b+140UmXaehasc7PD8paAlLzaWkqC6A5de30VCoE/XDzufNo V5qeVh/ouXFGzBtbY0UaOA9nLM1IewzL2bqt48U++QbgYDcLu49rc5JEIdEAzcf2 twe+4BIk0tRTItfxswbu+wdUXam3uzYoUwcH92Q306IBoTT2Ls4cErPaiHmovfsP eWjKU7f8sKKBF7AdkVqd8roBtTEHsa23Je09vdB0JFF7+Dljuj/cmUoDg5JbracU aZIrHrVobVJqwGExof2lIXQe1uuBPcLGGuKXNQuUSXuN6Q/jX3mfxn9flCpiij+K +u1Iu5CFjuwo8dHluHk14ev5yZ/jSTx0WT6bvNQHnr6RYpAt4cat7ST6NJluS8U7 5OlL4AaoVw4nuxW8WzimWk/XtaDwI2/XIK4cdnb41l4MlT4Qt/iwtPyifZX9rvnZ WL3Y6T0ZqRi8o2qSPUVIpIrOcW+JBLL7maKCw1I/oonbs4leFRSV5KxZzWoV9ATy iUM0H0/OHAx/EanyrgGhLhu8bn+W9dXj6vmMXPOpujwxcfv1vQO7BOfLw4Mk78oe 8GNy4TAE57g/XCE= =jAIK -END PGP SIGNATURE End Message ---
Bug#979618: marked as done (libx11 possible ABI break in libx11 breaks libx11-xcb1 and that breaks chromium)
Your message dated Mon, 11 Jan 2021 11:54:20 + with message-id and subject line Bug#979590: fixed in libx11 2:1.7.0-2 has caused the Debian Bug report #979590, regarding libx11 possible ABI break in libx11 breaks libx11-xcb1 and that breaks chromium 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.) -- 979590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979590 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: chromium Version: 87.0.4280.88-0.4 Severity: grave X-Debbugs-Cc: deb...@rocketjump.eu Hi, starting chromium on bullseye will render a window (with various elements shifted down by half a screen), which is impossible to interact with, and causes gnome to offer a "force quit" prompt after a few seconds. Output from the CLI: ->8-->8-->8-->8-->8-->8-->8-->8-->8-->8-->8- $ chromium libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null) [9413:9413:0109/060426.733876:ERROR:vaapi_wrapper.cc(541)] vaInitialize failed: unknown libva error [9413:9413:0109/060426.735693:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process. [9413:9413:0109/060426.855283:ERROR:shared_context_state.cc(74)] Skia shader compilation error Errors: [9413:9413:0109/060426.858413:ERROR:shared_context_state.cc(74)] Skia shader compilation error Errors: [9413:9413:0109/060426.860282:ERROR:shared_context_state.cc(74)] Skia shader compilation error Errors: [9413:9413:0109/060426.867099:ERROR:shared_context_state.cc(74)] Skia shader compilation error Errors: [9413:9413:0109/060426.869489:ERROR:shared_context_state.cc(74)] Skia shader compilation error Errors: [9415:9428:0109/060426.876651:ERROR:nss_util.cc(283)] After loading Root Certs, loaded==false: NSS error code: -8018 [9413:9413:0109/060426.993836:ERROR:shared_context_state.cc(74)] Skia shader compilation error Errors: [9413:9413:0109/060430.833703:ERROR:gl_surface_presentation_helper.cc(259)] GetVSyncParametersIfAvailable() failed for 1 times! [9413:9413:0109/060430.839756:ERROR:gl_surface_presentation_helper.cc(259)] GetVSyncParametersIfAvailable() failed for 2 times! Killed ->8-->8-->8-->8-->8-->8-->8-->8-->8-->8-->8- Various things I've tried: - reverting to chromium(,-common,-sandbox) to 87.0.4280.88-0.3 -> same problem - reverting to chromium(,-common,-sandbox) to 87.0.4280.88-0.3 -> same problem - starting chromium with a fresh profile -> same problem Installing debug symbols and starting `chromium -g` will result in the same errors, except for chromium complaining about being started in single-process mode. One user on #debian-next IRC reported no such errors on sid and KDE, so it might not effect all users. I *think* about a week ago chromium still ran fine (I only use it for debugging purposes). Checking /var/log/apt/history.log, I don't see any libva* packages being updated in that timeframe. Regards, Lee -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-1-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_USER, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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 87.0.4280.88-0.4 ii libasound2 1.2.4-1.1 ii libatk-bridge2.0-0 2.38.0-1 ii libatk1.0-0 2.36.0-2 ii libatomic1 10.2.1-3 ii libatspi2.0-02.38.0-2 ii libavcodec58 7:4.3.1-5 ii libavformat587:4.3.1-5 ii libavutil56 7:4.3.1-5 ii libc62.31-6 ii libcairo21.16.0-5 ii libcups2 2.3.3op1-4 ii libdbus-1-3 1.12.20-1 ii libdrm2 2.4.103-2 ii libevent-2.1-7 2.1.12-stable-1 ii libexpat12.2.10-1 ii libflac8 1.3.3-2 ii libfontconfig1 2.13.1-4.2 ii libfreetype6 2.10.4+dfsg-1 ii libgbm1 20.3.2-1 ii libgcc-s110.2.1-3 ii libgdk-pixbuf-2.0-0 2.42.2+dfsg-1 ii libglib2.0-0 2.66.4-1 ii libgtk-3-0 3.24.24-1 ii
libx11_1.7.0-2_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 11 Jan 2021 12:15:25 +0100 Source: libx11 Architecture: source Version: 2:1.7.0-2 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Julien Cristau Closes: 979590 Changes: libx11 (2:1.7.0-2) unstable; urgency=medium . * Set a strict dependency of libx11-xcb1 on libx11-6, as internal ABI may change across releases - and indeed did change between 1.6.12 and 1.7.0 (closes: #979590) * Update upstream git URL in package descriptions. Checksums-Sha1: 9d7689b4f621e72e48cc225a5986b123b5102b98 2564 libx11_1.7.0-2.dsc f0294ed61e0ce05da05d1f7ea3682536e0f5ae96 73844 libx11_1.7.0-2.diff.gz Checksums-Sha256: 1540dcbbbdf7e08405d133127ca6f63fe191a3946ae9c5afc95293bc12f784a1 2564 libx11_1.7.0-2.dsc 910d4a1527458ff020f0bab9df55bab44d63db8247543d2b2256c7b258ce439c 73844 libx11_1.7.0-2.diff.gz Files: e8781a3e2d7accd1f2057d91a5940570 2564 x11 optional libx11_1.7.0-2.dsc f8911845bfd953f82a3ef1ac0697e022 73844 x11 optional libx11_1.7.0-2.diff.gz -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEVXgdqzTmGgnvuIvhnbAjVVb4z60FAl/8NhYUHGpjcmlzdGF1 QGRlYmlhbi5vcmcACgkQnbAjVVb4z61cYg/5AeB5A0SF/qCS2fCCaADJOla4RJlH HZPna/MmPxIonahyZ3caCuhJ+7etZdq9vAyGLqoy4wLyYWp3Xbq4Htx0TFDxGBHD qA0OTW7QmhrlrIs3b+140UmXaehasc7PD8paAlLzaWkqC6A5de30VCoE/XDzufNo V5qeVh/ouXFGzBtbY0UaOA9nLM1IewzL2bqt48U++QbgYDcLu49rc5JEIdEAzcf2 twe+4BIk0tRTItfxswbu+wdUXam3uzYoUwcH92Q306IBoTT2Ls4cErPaiHmovfsP eWjKU7f8sKKBF7AdkVqd8roBtTEHsa23Je09vdB0JFF7+Dljuj/cmUoDg5JbracU aZIrHrVobVJqwGExof2lIXQe1uuBPcLGGuKXNQuUSXuN6Q/jX3mfxn9flCpiij+K +u1Iu5CFjuwo8dHluHk14ev5yZ/jSTx0WT6bvNQHnr6RYpAt4cat7ST6NJluS8U7 5OlL4AaoVw4nuxW8WzimWk/XtaDwI2/XIK4cdnb41l4MlT4Qt/iwtPyifZX9rvnZ WL3Y6T0ZqRi8o2qSPUVIpIrOcW+JBLL7maKCw1I/oonbs4leFRSV5KxZzWoV9ATy iUM0H0/OHAx/EanyrgGhLhu8bn+W9dXj6vmMXPOpujwxcfv1vQO7BOfLw4Mk78oe 8GNy4TAE57g/XCE= =jAIK -END PGP SIGNATURE- Thank you for your contribution to Debian.
Bug#979618: Bug#979590: fixed in libx11 2:1.7.0-2
I can confirm that upgrading libx11-6 to match libx11-xcb1 fixed my issue with chromium. Thanks!
Processed: your mail
Processing commands for cont...@bugs.debian.org: > reassign 979825 libx11 Bug #979825 [chromium] chromium: Chromium freezes on startup Bug reassigned from package 'chromium' to 'libx11'. No longer marked as found in versions chromium/87.0.4280.141-0.1. Ignoring request to alter fixed versions of bug #979825 to the same values previously set > End of message, stopping processing here. Please contact me if you need assistance. -- 979825: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979825 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> forcemerge 979590 979825
Bug #979590 {Done: Julien Cristau } [libx11] libx11
possible ABI break in libx11 breaks libx11-xcb1 and that breaks chromium
Bug #979618 {Done: Julien Cristau } [libx11] libx11
possible ABI break in libx11 breaks libx11-xcb1 and that breaks chromium
Bug #979825 [libx11] chromium: Chromium freezes on startup
Marked Bug as done
Outlook recorded from message bug 979825 message
Added indication that 979825 affects chromium
Marked as fixed in versions libx11/2:1.7.0-2.
There is no source info for the package 'libx11' at version '2:1.7.0-1' with
architecture ''
Unable to make a source version for version '2:1.7.0-1'
Marked as found in versions 2:1.7.0-1.
Bug #979618 {Done: Julien Cristau } [libx11] libx11
possible ABI break in libx11 breaks libx11-xcb1 and that breaks chromium
Merged 979590 979618 979825
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
979590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979590
979618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979618
979825: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979825
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#979837: xserver-xorg-video-intel: Depth dropped to 16
Package: xserver-xorg-video-intel Severity: normal Dear Maintainer, Some applications don't work with Depth 16 and require 24. The last version where the support of Depth 24 was seen was 2:2.99.917+git20171229-1. All higher up to latest restricted to 16 only. So I compelled to downgrade and pin that working version. Please, return back the Depth 24 -- System Information: Debian Release: bullseye/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-1-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.utf8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xserver-xorg-video-intel depends on: ii libc6 2.31-9 ii libdrm-intel1 2.4.103-2 ii libdrm22.4.103-2 ii libpciaccess0 0.16-1 ii libpixman-1-0 0.40.0-1 ii libudev1 247.2-4 ii libx11-6 2:1.7.0-1 ii libx11-xcb12:1.7.0-1 ii libxcb-dri2-0 1.14-2.1 ii libxcb-util1 0.4.0-1+b1 ii libxcb11.14-2.1 ii libxcursor11:1.2.0-2 ii libxdamage11:1.1.5-2 ii libxext6 2:1.3.3-1.1 ii libxfixes3 1:5.0.3-2 ii libxinerama1 2:1.1.4-2 ii libxrandr2 2:1.5.1-1 ii libxrender11:0.9.10-1 ii libxss11:1.2.3-1 ii libxtst6 2:1.2.3-1 ii libxvmc1 2:1.0.12-2 ii xserver-xorg-core [xorg-video-abi-24] 2:1.20.10-2 xserver-xorg-video-intel recommends no packages. xserver-xorg-video-intel suggests no packages.
xdm is marked for autoremoval from testing
xdm 1:1.1.11-3 is marked for autoremoval from testing on 2021-01-25 It is affected by these RC bugs: 948346: xdm: xdm gets killed, but only on sunday, on the first startup (code=killed, signal=USR2) https://bugs.debian.org/948346 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
