xdm is marked for autoremoval from testing

2021-01-11 Thread Debian testing autoremoval watch
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-tea

Bug#979837: xserver-xorg-video-intel: Depth dropped to 16

2021-01-11 Thread Vladmimir Stavrinov
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 pi

Processed: your mail

2021-01-11 Thread Debian Bug Tracking System
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-

Processed: your mail

2021-01-11 Thread Debian Bug Tracking System
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 b

Bug#979618: Bug#979590: fixed in libx11 2:1.7.0-2

2021-01-11 Thread Lee Garrett
I can confirm that upgrading libx11-6 to match libx11-xcb1 fixed my issue with chromium. Thanks!

libx11_1.7.0-2_source.changes ACCEPTED into unstable

2021-01-11 Thread Debian FTP Masters
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: libx

Bug#979618: marked as done (libx11 possible ABI break in libx11 breaks libx11-xcb1 and that breaks chromium)

2021-01-11 Thread Debian Bug Tracking System
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

Bug#979590: marked as done (libx11 possible ABI break in libx11 breaks libx11-xcb1 and that breaks chromium)

2021-01-11 Thread Debian Bug Tracking System
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

Processing of libx11_1.7.0-2_source.changes

2021-01-11 Thread Debian FTP Masters
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)

[Git][xorg-team/lib/libx11] Pushed new tag libx11-2_1.7.0-2

2021-01-11 Thread Julien Cristau
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.

[Git][xorg-team/lib/libx11][debian-unstable] 3 commits: Set a strict dependency of libx11-xcb1 on libx11-6

2021-01-11 Thread Julien Cristau
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:

Bug#979590: libx11-xcb1: Updating to 1.7.0-1 from 1.6.12-1 breaks chromium and google chrome

2021-01-11 Thread Christoph Berg
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

Processed: affects 979590

2021-01-11 Thread Debian Bug Tracking System
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 th