brisk-menu assert failure: brisk-menu: ../../src/xcb_io.c:259: poll_for_event: asserzione \"!xcb_xlib_threads_sequence_lost\" non riuscita.

Bug #1761173 reported by Marco Giannini
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
brisk-menu (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Crash on fresh install of Ubuntu MATE 18..04 daily 04/04/2018
No more information about crash

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: mate-applet-brisk-menu 0.5.0-6ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
AssertionMessage: brisk-menu: ../../src/xcb_io.c:259: poll_for_event: asserzione \"!xcb_xlib_threads_sequence_lost\" non riuscita.
CurrentDesktop: MATE
Date: Wed Apr 4 14:04:56 2018
ExecutablePath: /usr/lib/x86_64-linux-gnu/brisk-menu/brisk-menu
InstallationDate: Installed on 2018-04-04 (0 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
ProcCmdline: /usr/lib/x86_64-linux-gnu/brisk-menu//brisk-menu
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=it_IT
 LANG=it_IT.UTF-8
Signal: 6
SourcePackage: brisk-menu
StacktraceTop:
 __assert_fail_base (fmt=0x7f9ee9f04b03 <error: Cannot access memory at address 0x7f9ee9f04b03>, assertion=assertion@entry=0x7f9ee8f93660 "!xcb_xlib_threads_sequence_lost", file=file@entry=0x7f9ee8f934cb "../../src/xcb_io.c", line=line@entry=259, function=function@entry=0x7f9ee8f93908 "poll_for_event") at assert.c:92
 __GI___assert_fail (assertion=0x7f9ee8f93660 "!xcb_xlib_threads_sequence_lost", file=0x7f9ee8f934cb "../../src/xcb_io.c", line=259, function=0x7f9ee8f93908 "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: asserzione \"!xcb_xlib_threads_sequence_lost\" non riuscita.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Marco Giannini (marco-giannini) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __assert_fail_base (fmt=0x7f9ee9f04b03 <error: Cannot access memory at address 0x7f9ee9f04b03>, assertion=assertion@entry=0x7f9ee8f93660 "!xcb_xlib_threads_sequence_lost", file=file@entry=0x7f9ee8f934cb "../../src/xcb_io.c", line=line@entry=259, function=function@entry=0x7f9ee8f93908 <__PRETTY_FUNCTION__.14350> "poll_for_event") at assert.c:92
 __GI___assert_fail (assertion=assertion@entry=0x7f9ee8f93660 "!xcb_xlib_threads_sequence_lost", file=file@entry=0x7f9ee8f934cb "../../src/xcb_io.c", line=line@entry=259, function=function@entry=0x7f9ee8f93908 <__PRETTY_FUNCTION__.14350> "poll_for_event") at assert.c:101
 poll_for_event (dpy=dpy@entry=0x561bc9a54580) at ../../src/xcb_io.c:256
 poll_for_response (dpy=dpy@entry=0x561bc9a54580) at ../../src/xcb_io.c:274
 _XEventsQueued (dpy=dpy@entry=0x561bc9a54580, 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
Revision history for this message
Mike Gabriel (sunweaver) wrote : Re: [Bug 1761173] brisk-menu assert failure: brisk-menu: ../../src/xcb_io.c:259: poll_for_event: asserzione \"!xcb_xlib_threads_sequence_lost\" non riuscita.

Hi,

On Mi 04 Apr 2018 15:26:10 CEST, Apport retracing service wrote:

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

I am half sure that I have seen this (or a similar crash) on Debian,
too, yesterday...

Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31
mail: <email address hidden>, http://das-netzwerkteam.de

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

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in brisk-menu (Ubuntu):
status: New → Confirmed
Norbert (nrbrtx)
Changed in brisk-menu (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in brisk-menu (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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