[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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 +0000
with message-id <E1kyvm8-000C0U-HU@fasolo.debian.org>
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 owner@bugs.debian.org
immediately.)


-- 
979590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979590
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: libx11-xcb1
Version: 2:1.7.0-1
Severity: normal
X-Debbugs-Cc: michel@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 <jcristau@debian.org>

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 979590@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Julien Cristau <jcristau@debian.org> (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 ftpmaster@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 <debian-x@lists.debian.org>
Changed-By: Julien Cristau <jcristau@debian.org>
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 ---
Reply to: