On 12/18/07, Che Guevara <email address hidden> wrote:
> Setting back to confirmed as this bug is back for hardy
If you can confirm this bug, then you have an obligation to provide a
lot more information. Many quite different problems were reported in
this Launchpad bug, and many things have changed since they were
originally reported. I still consider this particular report resolved,
until proven otherwise.
0) Are all your packages fully up to date?
1) What did you test?
2) How did it break?
3) Provide a backtrace from the assertion failing. (libxcb1.1 now
automatically generates one for you, on glibc systems like Linux.)
You may need to install debug packages to get a complete backtrace.
4) What version do you have installed of any libraries in the backtrace?
(I don't have an Ubuntu install handy, so don't just tell me "the
newest ones"--I don't know if that's current from upstream.)
5) Does your test work when LIBXCB_ALLOW_SLOPPY_LOCK is set?
In other words, *please* read the history of this bug report and answer
the questions already given. :-)
On 12/18/07, Che Guevara <email address hidden> wrote:
> Setting back to confirmed as this bug is back for hardy
If you can confirm this bug, then you have an obligation to provide a
lot more information. Many quite different problems were reported in
this Launchpad bug, and many things have changed since they were
originally reported. I still consider this particular report resolved,
until proven otherwise.
0) Are all your packages fully up to date? ALLOW_SLOPPY_ LOCK is set?
1) What did you test?
2) How did it break?
3) Provide a backtrace from the assertion failing. (libxcb1.1 now
automatically generates one for you, on glibc systems like Linux.)
You may need to install debug packages to get a complete backtrace.
4) What version do you have installed of any libraries in the backtrace?
(I don't have an Ubuntu install handy, so don't just tell me "the
newest ones"--I don't know if that's current from upstream.)
5) Does your test work when LIBXCB_
In other words, *please* read the history of this bug report and answer
the questions already given. :-)