dist-upgrade broke Opera

sinistra · External Since: Apr 26, 2007 Posts: 9

Eirik Byrkjeflot Anonsen <eirik.RemoveThis@opera.com> wrote in
news:87wszuwcib.fsf@opera.com:

> Ouch! This is a bug in xlib.

I received a letter today from Branden Robinson who was involved in X11
but less so now..he said:

As I understand it, the XCB-linked Xlib has not yet propagated into
unstable, so you must be running experimental libx11-6 packages.

Then I kindly received another letter from him saying:

I am informed by Michel Dänzer of the X Strike Force that there is a
workaround for this problem:

LIBXCB_SLOPPY_LOCK=1

This is a process environment setting, so you'll want to use "export" or
"setenv" or the appropriate command for your shell to get it into the
environment.

I post this should it help anyone on the edge with Debian Lenny.

--
S.

sinistra · External Since: Apr 26, 2007 Posts: 9

Forward from Josh Triplett for the record: Bug#421854: Not a bug in libx11

Hello,

Despite previous comments forwarded to this bug report from
Eirik Byrkjeflot Anonsen, this bug does not lie in libx11 or libxcb.

The reported assertion means that some caller of libx11 has broken locking;
specifically, it calls UnlockDisplay without calling LockDisplay. (Note that
the functions XLockDisplay and XUnlockDisplay nest, but LockDisplay and
UnlockDisplay do not.)

If opera does not call libx11 directly, the bug likely lies in a library
between opera and libx11, such as a toolkit or an X extension library.

Please try to reproduce this problem under gdb, and get a backtrace. This
will help us track down where the broken locking exists. In the meantime,
since no opera package exists in Debian to reassign to, I'll leave this bug
open on libx11 for lack of somewhere better to track it.

Please see
<http://lists.debian.org/debian-devel-announce/2006/11/msg00010.html> for more
information.

- Josh Triplett

--
s

Eirik Byrkjeflot Anonsen · External Since: Apr 02, 2004 Posts: 238

sinistra <sinistra.TakeThisOut@pochtamt.ru> writes:

> Forward from Josh Triplett for the record: Bug#421854: Not a bug in libx11
>
>
> Hello,
>
> Despite previous comments forwarded to this bug report from
> Eirik Byrkjeflot Anonsen, this bug does not lie in libx11 or libxcb.
>
> The reported assertion means that some caller of libx11 has broken locking;
> specifically, it calls UnlockDisplay without calling LockDisplay. (Note that
> the functions XLockDisplay and XUnlockDisplay nest, but LockDisplay and
> UnlockDisplay do not.)
>
> If opera does not call libx11 directly, the bug likely lies in a library
> between opera and libx11, such as a toolkit or an X extension library.
>
> Please try to reproduce this problem under gdb, and get a backtrace. This
> will help us track down where the broken locking exists. In the meantime,
> since no opera package exists in Debian to reassign to, I'll leave this bug
> open on libx11 for lack of somewhere better to track it.
>
> Please see
> <http://lists.debian.org/debian-devel-announce/2006/11/msg00010.html> for more
> information.
>
> - Josh Triplett
>
> --
> s

I was sure I'd read on the xorg list that these were typically errors
in xlib that got caught by xcb. Ah well, in that case, I would assume
it is qt that does it. While we do some direct X calls, I doubt we do
any locking ourselves.

I'll reply to the bug.

eirik

Eirik Byrkjeflot Anonsen · External Since: Apr 02, 2004 Posts: 238

sinistra <sinistra.RemoveThis@pochtamt.ru> writes:

> Forward from Josh Triplett for the record: Bug#421854: Not a bug in libx11
>
> Please try to reproduce this problem under gdb, and get a backtrace. This
> will help us track down where the broken locking exists.

Oh, and that would be a good idea. Any chance you can do that?

eirik

sinistra · External Since: Apr 26, 2007 Posts: 9

>Oh, and that would be a good idea. Any chance you can do that?

Highly unlikely Eirik right now everything on 9.21.641 with Debian Lenny is
the one stable thing in a changing universe.

--
s.