Package: xserver-xorg-video-intel
Version: 2:2.15.0-3
Severity: grave
(Flagged as grave because, as a user-triggered segfault in an
application running as root, it's a potential security hole; and, since
the crash abruptly ends the user's session, it may cause the loss of
unsaved data.)
I ran `xs
On Thu, Apr 21, 2011 at 04:22:17PM +0200, Julien Danjou wrote:
> On Thu, Apr 21 2011, Drew Parsons wrote:
> > cc: xcb maintainers: should you keep libxcb-xprint0 ? Do we need to talk
> > about this? libxcb-xprint0 has no relation (in a packaging sense) to
> > xprint.
>
> I see no harm providing it
package libx11-6
retitle 486507 libx11-6: VMWare Server sees X responses out of order
thanks
Hi folks,
The locking assertion failures and their associated backtraces should be
looked into, but may be unrelated to the assertion failure that's
actually causing VMWare Server to abort():
vmware: ../
On Sat, Mar 15, 2008 at 09:36:37PM -0700, Jamey Sharp wrote:
> Please review and provide comments. We hope to commit these patches and
> release new versions of XCB and Xlib/XCB soon.
Here are the bugs we currently know about that are keeping us from
committing these patches as-is. We
On Sat, Mar 15, 2008 at 09:36:37PM -0700, Jamey Sharp wrote:
> The attached patch to Xlib/XCB converts it to use the new handoff
> mechanism. Previously, Xlib/XCB used XCB's Xlib lock to prevent XCB from
> sending requests between calls to Xlib's LockDisplay and UnlockDisplay
simplified implementation in both Xlib and
XCB.
- Jamey Sharp and Josh Triplett
signature.asc
Description: Digital signature
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/2/07, Mateusz Kaduk <[EMAIL PROTECTED]> wrote:
> However screen is still black current git does better job. I am
> attaching log file. No more errors about sil164, ivch and tfp410
> submodule and one new error connected with ch7017 submodule. (
On Fri, Apr 13, 2007 at 03:18:34AM +0200, Brice Goglin wrote:
> Also, you could try the new libx11* packages currently in experimental
> (2:1.1.1-1 instead the 2:1.1-2 you had when reporting this bug) in case
> something got fixed.
Even better, please try 2:1.1.2-1, which fixes an event-handling s
On Mon, Dec 18, 2006 at 10:34:49PM +0900, Gin wrote:
> libX11 has bug in function XFilterEvent.
> It cannot hadle thread when XIM is using.
Josh Triplett and I recreated part of the fix you cite recently because
Xlib/XCB reveals the same problem, even for single-threaded apps.
However, we weren't
natives/x-terminal-emulator.1.gz, but the latter still does
not exist. Changing the alternative to something else and back repairs
it; another fix might work as well.
- Josh Triplett and Jamey Sharp
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (990, 'tes
On Thu, Dec 07, 2006 at 03:27:17AM +0300, Ilya Galushko wrote:
> Hey, dear maintainer!
>
> Did you need more information on this bug or not???
> I still want to help!
You're replying to a very old bug against the ancient XFree86 server,
and your symptoms don't sound quite the same to me. But if y
forwarded 401956 https://bugs.freedesktop.org/show_bug.cgi?id=8699
tags 401956 + upstream fixed-upstream fixed-in-experimental
thanks
This is upstream bug #8699, fixed in libX11 1.1-RC2 and later with this
commit:
http://gitweb.freedesktop.org/?p=xorg/lib/libX11.git;a=commitdiff_plain;h=6
tags 400654 + wontfix
forcemerge 334080 400654
thanks
On Mon, Nov 27, 2006 at 08:46:55PM +0100, Antonio Larrosa wrote:
> I think xserver-xorg should depend on xfonts-base.
The old xserver-common package had this note:
X servers either need fonts installed on the local host, or need
Package: libxcomposite1
Version: 1:0.3-2
Severity: important
Tags: upstream fixed-upstream patch
libXcomposite calls UnlockDisplay without calling LockDisplay. This
causes a locking correctness assertion failure with libX11 1.1 and
Xlib/XCB in experimental, and will become RC after the etch relea
Package: libx11-6
Version: 2:1.0.3-3
Severity: normal
Tags: upstream fixed-upstream patch
libX11's XKB and XIM support have several potential race conditions and
deadlocks for multi-threaded applications, due to missing or incorrectly
placed calls to UnlockDisplay or LockDisplay.
http://gitweb.fr
Package: libxdamage1
Version: 1:1.0.3-2
Severity: important
Tags: upstream fixed-upstream patch
libXdamage calls UnlockDisplay and SyncHandle without a matching
LockDisplay. This causes a locking correctness assertion failure with
libX11 1.1 and Xlib/XCB in experimental, and will become RC after
forwarded 278984 https://bugs.freedesktop.org/show_bug.cgi?id=9160
tags 278984 + upstream
thanks
Package: libx11-6
Version: 2:1.0.3-3
Followup-For: Bug #278984
I can reproduce this bug both with this Debian package and with a
current git checkout from X.org. It's an upstream bug: at most 65,533
c
17 matches
Mail list logo