Bug#1128905: libx11-6: 19-year-old NEWS.Debian file added

Vincent Lefevre <[email protected]>
Newsgroups gmane.linux.debian.devel.x
Message-ID <20260224112117.GA47924__18687.3830783711$1771932574$gmane$org@disset.lip.ens-lyon.fr>
Package: libx11-6
Version: 2:1.8.13-1
Severity: normal

A 19-year-old NEWS.Debian file has been added in this version:

  /usr/share/doc/libx11-6/NEWS.Debian.gz

which contains

libx11 (2:1.1-1) experimental; urgency=low

  [ Josh Triplett, Jamey Sharp ]
  libx11 1.1 includes our work on Xlib/XCB, which uses XCB as the Xlib
  transport layer, and allows a client to use both Xlib and XCB on the
  same connection. This allows clients to transition from Xlib to XCB
  incrementally.  libx11-6 1.1 is API- and ABI-compatible with previous
  versions, and does not require any software or package changes.

  Ideally, you will not notice any
  change at all.  However, Xlib/XCB includes some additional
  code to check for bugs in calling software.  If you encounter a problem, you
  will most likely just see an application disappear, due to having triggered
  an assertion and aborted.  If you ran the application from a terminal, you
  can look there to see error output and get more details; otherwise, look at
  ~/.xsession-errors.  These assertions look like one of these:

    xcb_xlib.c:41: xcb_xlib_lock: Assertion `!c->xlib.lock' failed.
    xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed.

  Both of these represent bugs in a caller of libX11, and *not* in
  libX11 or libxcb.  The first assertion means that a caller attempted
  to lock the display while already locked.  The second assertion means
  that a caller attempted to unlock the display without having it
  locked.  If you encounter such bugs, please report a bug against the
  offending software (*not* libx11-6 or libxcb), provide a backtrace,
  and X-Debbugs-CC: [email protected] if you need help tracking
  down the problem.  If the bug always consistently occurs when running
  the application (or in the case of a library, invoking the library),
  use severity "important", and raise to "grave" after the etch release.

 -- Josh Triplett <[email protected]>  Fri, 24 Nov 2006 17:36:55 -0800

This is confusing. It applied to libx11 1.1, but the current version
is 1.8.13.

-- System Information:
Debian Release: forky/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.18.12+deb14-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CPU_OUT_OF_SPEC
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libx11-6 depends on:
ii  libc6        2.42-13
ii  libx11-data  2:1.8.13-1
ii  libxcb1      1.17.0-2+b2

libx11-6 recommends no packages.

libx11-6 suggests no packages.

-- no debconf information
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.