soffice.bin: ../../src/xcb_io.c:263: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.

Bug #1801161 reported by Chris Hermansen
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
libreoffice (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Using LibreOffice Calc I was editing a filter on a pivot table and all LibreOffice windows hung. What appeared in /var/log/syslog was:

Nov 1 13:31:57 santiago org.gnome.Shell.desktop[8288]: [xcb] Unknown sequence number while processing queue
Nov 1 13:31:57 santiago org.gnome.Shell.desktop[8288]: [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
Nov 1 13:31:57 santiago org.gnome.Shell.desktop[8288]: [xcb] Aborting, sorry about that.
Nov 1 13:31:57 santiago org.gnome.Shell.desktop[8288]: soffice.bin: ../../src/xcb_io.c:263: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
Nov 1 13:32:27 santiago gnome-shell[8288]: Some code accessed the property 'WindowPreviewMenuItem' on the module 'windowPreview'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: libreoffice-calc 1:6.1.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 1 13:39:03 2018
InstallationDate: Installed on 2018-10-29 (3 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Chris Hermansen (c-hermansen) wrote :
Revision history for this message
Olivier Tilloy (osomon) wrote :

Thank you for the report Chris.

From your report it sounds like this is a one-off issue. Have you observed that problem more than once? Are there specific steps to take to make it happen? Maybe a specific document?

Changed in libreoffice (Ubuntu):
status: New → Incomplete
Revision history for this message
Ilya Kotov (forkotov02) wrote :

I have similar bug with several applications: https://bugs.launchpad.net/ubuntu/+source/freecad/+bug/1808710

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for libreoffice (Ubuntu) because there has been no activity for 60 days.]

Changed in libreoffice (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Ilya Kotov (forkotov02) wrote :

Solution: remove libreoffice-gtk2 and install libreoffice-gtk3

Revision history for this message
Gérald Sédrati-Dinet (Gibus) (gerald-sedrati-dinet) wrote :

I have a similar bug with LibreOffice Writer. Application freezes with following traces in .xsession-errors:

[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.
soffice.bin: ../../src/xcb_io.c :259 : poll_for_event: l'assertion « !xcb_xlib_threads_sequence_lost » a échoué.

It seemed to happen randomly (not doing anything special, on time while typing, another time while selecting text), but already 2 times in a week since upgrade to LibreOffice 6.0.7.3.

Revision history for this message
Gérald Sédrati-Dinet (Gibus) (gerald-sedrati-dinet) wrote :

Sorry, forgot to tell in #6 that libreoffice-gtk2 is already removed and libreoffice-gtk3 already installed.

Changed in libreoffice (Ubuntu):
status: Expired → Confirmed
Revision history for this message
ԜаӀtеr Ⅼарсһуnѕkі (wxl) wrote :

Oliver: there's a bug for pcmanfm (https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1782984) with the same end result. This seems to somehow related to GTK2, as there are several other applications that show the same behavior (https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710). There's a file manager called SpaceFM one user tried and it showed the problems with the GTK2 version but not with the GTK3 version. This, coupled with Ilya's suggestion, leads me to believe GTK2 is indeed the result. With pcmanfm, though there are specific behaviors that cause the bug, it's not 100% reproducible. Sometimes those behaviors cause the error and sometimes they do not.

However, Gérald's comment comes as something of a shock.

Revision history for this message
Gérald Sédrati-Dinet (Gibus) (gerald-sedrati-dinet) wrote :

If that helps, here are all gtk2 related packages installed:

~$ dpkg --get-selections |grep gtk2
gtk2-engines-murrine:amd64 install
gtk2-engines-pixbuf:amd64 install
gtk2-engines-xfce install
gtk2-ex-formfactory-perl install
libcheese-gtk25:amd64 install
libgtk2-ex-formfactory-perl install
libgtk2-perl install
libgtk2.0-0:amd64 install
libgtk2.0-common install
python-gtk2 install

(I've uninstalled everyhting else, but these ones have too much dependencies on Xubuntu)

Revision history for this message
Gérald Sédrati-Dinet (Gibus) (gerald-sedrati-dinet) wrote :

Also, the bug still happens, but apparently less frequently, when libreoffice is launched with env variable LIBGL_DRI3_DISABLE is true (i.e: LIBGL_DRI3_DISABLE=true /usr/bin/libreoffice) as advised in https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1782984

It's really hard to reproduce, it seems that most often the bug is triggered when text is selected (to be copy/cut) in libre-office writer.

Revision history for this message
Vier Eck (viereck) wrote :

I currently have it from time to time in Artix/ Arch Linux (libreoffice-still 6.1.6-2), only using lcalc. It is triggered when I do some action, but too seldomly that I can really test what in detail triggers it.

And it happens with SAL_USE_VCLPLUGIN=gtk3, as well.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.