Please ensure your application is calling XInitThreads before commenting
here. If it's not calling XInitThreads then that's probably an
application bug.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11 in Ubuntu.
The same error when executing UIO tests in eclipse under docker
environment
[xcb] Unknown sequence number while processing reply
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been
called
[xcb] Aborting, sorry about that.
java: ../../src/xcb_io.c:702: _XReply:
I still see this issue even after the suggested change
[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been
called
[xcb] Aborting, sorry about that.
java: ../../src/xcb_io.c:260: poll_for_event: Assertion
I am not installing all updates my docker file is as follows
RUN echo 'deb http://archive.ubuntu.com/ubuntu/ focal-proposed main restricted'
>> /etc/apt/sources.list && \
apt-get update -q -y && \
apt-get install -y --fix-missing --no-install-recommends \
libx11-6 \
That'll install all updates from proposed? Don't do that. Just use a
clean image and then install the required updates as mentioned in #106
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11 in Ubuntu.
https://bugs.launchpad.net/bugs/1782984
My DockerFile looks like
RUN echo 'deb http://archive.ubuntu.com/ubuntu/ focal-proposed main restricted'
>> /etc/apt/sources.list && \
apt-get update -q -y && \
apt-get install -y --fix-missing --no-install-recommends \
--
You received this bug notification because you are a member of
So I added the lines from comment 132 in my docker file and I now I am
not able to build my docker image I get the following error
10:23:39 xg++: fatal error: Killed signal terminated program cc1plus
10:23:39 compilation terminated.
10:23:39 make[3]: *** [Makefile:1117: insn-emit.o] Error 1
or do as advised in comment #106
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11 in Ubuntu.
https://bugs.launchpad.net/bugs/1782984
Title:
Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple
applications
To manage
echo 'deb http://archive.ubuntu.com/ubuntu/ focal-proposed main restricted' >>
/etc/apt/sources.list
apt update
apt install libx11-6
verify with 'apt-cache policy libx11-6' that you have the correct
version (from proposed), and run your tests.
--
You received this bug notification because you
I am using docker file to get ubuntu 20.04 and install packages. How can
I enable focal-proposed insider docker?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11 in Ubuntu.
https://bugs.launchpad.net/bugs/1782984
Title:
Assertion
did you enable focal-proposed?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11 in Ubuntu.
https://bugs.launchpad.net/bugs/1782984
Title:
Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple
applications
To manage
I have updated my docker image to use ubuntu 20.04 and I still see this
error with eclipse when running UI SWTBot tests. I get the following
error
[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been
called
[xcb]
Interactively, after you have found the 'Ubuntu on Wayland' option on
the login screen once, it will then become the default in future*
* Unless 'Ubuntu on Wayland' crashes in which case the option gets disabled and
it reverts to 'Ubuntu' which is a Xorg session.
--
You received this bug
I am updating my ubuntu docker file to use ubuntu 20.04 will it resolve
this issue ? any idea how can I achieve logging into ubuntu on wayland
in docker environment?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11 in Ubuntu.
Logging into 'Ubuntu on Wayland' is probably a good workaround because
it should avoid this problem completely. Although we would recommend
using Ubuntu 20.04 over 18.04.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11 in Ubuntu.
I am using ubuntu 18.04 in docker environment and running swtbot tests using
eclipse. I get the same error.
I updated my docker file to install libx11-6 but the problem still exists. The
tests execution is aborted with the following error message
[xcb] Unknown sequence number while processing
Ok. So it seems that the bug *exists* in Focal, so now we just need to
verify that the bug is *fixed* by the proposed package.
@angie78 - as you seem to suffer from the bug, can you try to verify
that the proposed packages (from
Any update on this bug and the status of focal?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11 in Ubuntu.
https://bugs.launchpad.net/bugs/1782984
Title:
Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple
applications
Has anyone tried PCManFM or Inkscape on focal? It seems that this update
doesn't fix GNOME Shell on focal, but *maybe* that's because Shell is
hitting a different bug?
If this can be verified to fix PCManFM, Inkscape, or something on focal
we can release it and open a new bug for GNOME Shell on
** Tags removed: lubuntu
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11 in Ubuntu.
https://bugs.launchpad.net/bugs/1782984
Title:
Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple
applications
To manage notifications
comment #113 still holds, focal needs to be verified first
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11 in Ubuntu.
https://bugs.launchpad.net/bugs/1782984
Title:
Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple
> N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days
I've seen that the `verification-done-bionic` tag has been added on
September 4th, which was 19 days ago. Could someone
It looks like I was wrong, and the crash is still occurring with
libx11-6 2:1.7.0-2ubuntu0.1 in hirsute, for example:
https://errors.ubuntu.com/oops/91f6b2d4-1353-11ec-a828-fa163e102db1
The fact that the crash frequency dropped way off after 20.04 could just
be explained by:
* Most people
If you want evidence that the libx11 1.7.0 fix works then the error
reports linked from bug 1886059 are convincing enough to me.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11 in Ubuntu.
https://bugs.launchpad.net/bugs/1782984
Title:
Re comment #110, Cinnamon might just be missing the obvious:
> [xcb] Most likely this is a multi-threaded client and XInitThreads has
not been called
We added XInitThreads to mutter in 3.36.2-2 and it is upstreamed in
3.36.3
--
You received this bug notification because you are a member of
That seems like we should be able to extract a verification from the
errors.ubuntu.com results. Is it possible to query crashes with a
specific dependency version? Seeing no crash reports with libx11
2:1.6.9-2ubuntu1.3 would suggest this is fixed.
On the other hand,
It's the top crasher of gnome-shell in focal, but I don't know a test
case...
https://errors.ubuntu.com/?release=Ubuntu%2020.04=gnome-
shell=month
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11 in Ubuntu.
Thank you for the verification. Can someone also verify the focal
version? This needs to be released for the newer series first before we
can accept bionic.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11 in Ubuntu.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11 in Ubuntu.
https://bugs.launchpad.net/bugs/1782984
Title:
Assertion
I have finally tested with Inkscape. No more freezes. For my computer
this new package has solved the problem, a very annoying one. A lot of
thanks.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11 in Ubuntu.
I have just installed the package libx11 2:1.6.4-3ubuntu0.5.
I have made several tests with PCManFM, a program that used to freeze quite
easily.
IT WORKS, no more annoying freezing.
I have to test with inkscape, another program that used to freeze
easily, but I can't do it now. I'll make the
I am also affected by this bug. I am running Linuxmint and Cinnamon just
keeps crashing. Most of the times it is the result of clicking a few
things and opening / closing guake at the same time.
Installing the proposed packages does not fix the problem though, I am
still encountering frequent
Hello Stephen, or anyone else affected,
Accepted libx11 into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libx11/2:1.6.4-3ubuntu0.5 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Stephen, or anyone else affected,
Accepted libx11 into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libx11/2:1.6.9-2ubuntu1.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
+ [Impact]
+
+ There is a race in libx11 causing applications to randomly abort. It's
+ not trivial to reproduce, but there are enough duplicates that this
+ deserves an SRU to bionic & focal.
+
+ [Fix]
+
+ Backport a commit from upstream:
+
+ From
** Changed in: libx11 (Ubuntu Focal)
Status: Confirmed => In Progress
** Changed in: libx11 (Ubuntu Bionic)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11 in Ubuntu.
The Groovy Gorilla has reached end of life, so this bug will not be
fixed for that release
** Changed in: libx11 (Ubuntu Groovy)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11 in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libx11 (Ubuntu Groovy)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11 in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libx11 (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11 in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libx11 (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11 in Ubuntu.
https://bugs.launchpad.net/bugs/1782984
** Changed in: libx11 (Ubuntu Bionic)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
** Changed in: libx11 (Ubuntu Groovy)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11
** Changed in: libx11 (Ubuntu)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
** Changed in: libx11 (Ubuntu Focal)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11 in
libx11 (2:1.7.0-1) unstable; urgency=medium
* New upstream release.
* patches: Refreshed.
* signing-key: Added key from Keith Packard.
* symbols: Updated.
-- Timo Aaltonen Wed, 06 Jan 2021 20:47:58 +0200
** Also affects: libx11 (Ubuntu Bionic)
Importance: Undecided
Status:
Does anyone know if an update of the libx11 package for lubuntu 18.04
will be released?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11 in Ubuntu.
https://bugs.launchpad.net/bugs/1782984
Title:
Assertion
Fixed in libx11 version 1.7.0 with
https://gitlab.freedesktop.org/xorg/lib/libx11/-/commit/dbb55e1a5e82870466b095097d9e46046680ec25
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11 in Ubuntu.
https://bugs.launchpad.net/bugs/1782984
Title:
** No longer affects: pcmanfm (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11 in Ubuntu.
https://bugs.launchpad.net/bugs/1782984
Title:
Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple
applications
To manage
I think i got it right this time.
I managed to apply the proposed libx11 patch, installed the right libx11 deb
and it worked so far.
If anyone willing to test the fix i pushed it to
https://github.com/avafinger/libx11_1.6.4
Mind that if ubuntu team release a new version of the libx11 you might
The attachment "This patch is not the fix. WARNING" seems to be a patch.
If it isn't, please remove the "patch" flag from the attachment, remove
the "patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user
I applied the patch attached (libX11) but the crash still occurs with less
frequency.
Maybe i missed some additional patch required to fix this.
For the record:
I am running LUbuntu in this PC box (upgraded from 16.04 to 18.04) and i
have another one with Ubuntu 18.04 + LXDE installed from
Ouch, I missed this commit:
https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34/diffs?commit_id=8b45f9589b3eb1ff46d16c774b017794e553db8e
I Will try again.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11 in Ubuntu.
I would like to add some info that may help to narrow the problem.
I have had this crash in PCManFM since i upgraded ubuntu from 16.04 to 18.04
but the same bug manifest in Geany and Chromium as well. The bug could hit
PCManFM within a few clicks opening directories and then clicking on a file
** Summary changed:
- PCManFM freezes with Assertion `!xcb_xlib_threads_sequence_lost' failed when
clicking on a file or folder in 18.04
+ Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications
--
You received this bug notification because you are a member of Ubuntu-X,
52 matches
Mail list logo
