grub-customizer assert failure: grub-customizer: ../../src/xcb_io.c:260: poll_for_event: Předpoklad „!xcb_xlib_threads_sequence_lost“ nesplněn.

Bug #1872036 reported by Petr Kraus
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
grub-customizer (Ubuntu)
New
Medium
Unassigned

Bug Description

I think the error occurred while saving the topic

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: grub-customizer 5.1.0-2
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
AssertionMessage: grub-customizer: ../../src/xcb_io.c:260: poll_for_event: Předpoklad „!xcb_xlib_threads_sequence_lost“ nesplněn.
CasperMD5CheckResult: skip
Date: Fri Apr 10 11:04:19 2020
ExecutablePath: /usr/bin/grub-customizer
InstallationDate: Installed on 2019-10-13 (179 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
ProcCmdline: /usr/bin/grub-customizer no-fork
Signal: 6
SourcePackage: grub-customizer
StacktraceTop:
 __assert_fail_base (fmt=0x7f53e337c45a <error: Cannot access memory at address 0x7f53e337c45a>, assertion=0x7f53e6940858 "!xcb_xlib_threads_sequence_lost", file=0x7f53e69406c3 "../../src/xcb_io.c", line=260, function=<optimized out>) at assert.c:92
 __GI___assert_fail (assertion=0x7f53e6940858 "!xcb_xlib_threads_sequence_lost", file=0x7f53e69406c3 "../../src/xcb_io.c", line=260, function=0x7f53e6940b10 "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: grub-customizer assert failure: grub-customizer: ../../src/xcb_io.c:260: poll_for_event: Předpoklad „!xcb_xlib_threads_sequence_lost“ nesplněn.
UpgradeStatus: Upgraded to focal on 2020-04-10 (0 days ago)
UserGroups:

separator:

Revision history for this message
Petr Kraus (kraus.primda) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __assert_fail_base (fmt=0x7f53e337c45a <error: Cannot access memory at address 0x7f53e337c45a>, assertion=0x7f53e6940858 "!xcb_xlib_threads_sequence_lost", file=0x7f53e69406c3 "../../src/xcb_io.c", line=260, function=<optimized out>) at assert.c:92
 __GI___assert_fail (assertion=assertion@entry=0x7f53e6940858 "!xcb_xlib_threads_sequence_lost", file=file@entry=0x7f53e69406c3 "../../src/xcb_io.c", line=line@entry=260, function=function@entry=0x7f53e6940b10 <__PRETTY_FUNCTION__.14999> "poll_for_event") at assert.c:101
 poll_for_event (dpy=dpy@entry=0x555881287b50, queued_only=queued_only@entry=0) at ../../src/xcb_io.c:260
 poll_for_response (dpy=dpy@entry=0x555881287b50) at ../../src/xcb_io.c:278
 _XEventsQueued (mode=2, dpy=0x555881287b50) at ../../src/xcb_io.c:362

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 grub-customizer (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Steve Beattie (sbeattie)
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.