brisk-menu assert failure: brisk-menu: ../../src/xcb_io.c:259: poll_for_event: アサーション `!xcb_xlib_threads_sequence_lost' に失敗しました。

Bug #1769932 reported by ichro furuya
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
brisk-menu (Ubuntu)
New
Medium
Unassigned

Bug Description

Ubuntu MATE 18.04 (Japanese environment)

Kernel version: 4.15.0.20
Panel layout: Contemporary(Save Another Name: Delete the bottom bar)
Docky: 2.2.1.1-1

In advance,
"Menu" on the left of the top bar →System tools →Caja →Right click and select "Pin to favorites menu".

This time,
"Menu" on the left of the top bar →Favourites →Caja
→"Caja" (file manager) did not start, it crashed.

---

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: mate-applet-brisk-menu 0.5.0-7ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
AssertionMessage: brisk-menu: ../../src/xcb_io.c:259: poll_for_event: アサーション `!xcb_xlib_threads_sequence_lost' に失敗しました。
CurrentDesktop: MATE
Date: Wed May 9 00:12:11 2018
ExecutablePath: /usr/lib/x86_64-linux-gnu/brisk-menu/brisk-menu
InstallationDate: Installed on 2018-05-07 (1 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcCmdline: /usr/lib/x86_64-linux-gnu/brisk-menu//brisk-menu
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=ja
 PATH=(custom, no user)
 LANG=ja_JP.UTF-8
Signal: 6
SourcePackage: brisk-menu
StacktraceTop:
 __assert_fail_base (fmt=0x7f57c98daa32 <error: Cannot access memory at address 0x7f57c98daa32>, assertion=assertion@entry=0x7f57c896e660 "!xcb_xlib_threads_sequence_lost", file=file@entry=0x7f57c896e4cb "../../src/xcb_io.c", line=line@entry=259, function=function@entry=0x7f57c896e908 "poll_for_event") at assert.c:92
 __GI___assert_fail (assertion=0x7f57c896e660 "!xcb_xlib_threads_sequence_lost", file=0x7f57c896e4cb "../../src/xcb_io.c", line=259, function=0x7f57c896e908 "poll_for_event") at assert.c:101
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
Title: brisk-menu assert failure: brisk-menu: ../../src/xcb_io.c:259: poll_for_event: アサーション `!xcb_xlib_threads_sequence_lost' に失敗しました。
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
ichro furuya (furuya) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __assert_fail_base (fmt=0x7f57c98daa32 <error: Cannot access memory at address 0x7f57c98daa32>, assertion=assertion@entry=0x7f57c896e660 "!xcb_xlib_threads_sequence_lost", file=file@entry=0x7f57c896e4cb "../../src/xcb_io.c", line=line@entry=259, function=function@entry=0x7f57c896e908 <__PRETTY_FUNCTION__.14350> "poll_for_event") at assert.c:92
 __GI___assert_fail (assertion=assertion@entry=0x7f57c896e660 "!xcb_xlib_threads_sequence_lost", file=file@entry=0x7f57c896e4cb "../../src/xcb_io.c", line=line@entry=259, function=function@entry=0x7f57c896e908 <__PRETTY_FUNCTION__.14350> "poll_for_event") at assert.c:101
 poll_for_event (dpy=dpy@entry=0x55dc59183d60) at ../../src/xcb_io.c:256
 poll_for_response (dpy=dpy@entry=0x55dc59183d60) at ../../src/xcb_io.c:274
 _XEventsQueued (dpy=dpy@entry=0x55dc59183d60, mode=mode@entry=2) at ../../src/xcb_io.c:349

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in brisk-menu (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
ichro furuya (furuya)
description: updated
information type: Private → Public
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.