Bug 2223629

Summary:	virt-manager crashes: python3 xcb_io.c:263: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
Product:	Red Hat Enterprise Linux 7	Reporter:	Paulo Andrade <pandrade>
Component:	libX11	Assignee:	José Expósito <jexposit>
Status:	CLOSED MIGRATED	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.9	CC:	sbarcomb
Target Milestone:	rc	Keywords:	MigratedToJIRA
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-11 17:00:44 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Paulo Andrade 2023-07-18 12:36:09 UTC

Same backtrace as bz#1792576

#1  0x00007f3efe796a78 in __GI_abort () at abort.c:90
#2  0x00007f3efe78e1a6 in __assert_fail_base (fmt=0x7f3efe8e9d80 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", 
    assertion=assertion@entry=0x7f3ee68ac580 "!xcb_xlib_threads_sequence_lost", file=file@entry=0x7f3ee68ac3f3 "xcb_io.c", line=line@entry=263, 
    function=function@entry=0x7f3ee68ac827 <__PRETTY_FUNCTION__.14864> "poll_for_event") at assert.c:92
#3  0x00007f3efe78e252 in __GI___assert_fail (assertion=assertion@entry=0x7f3ee68ac580 "!xcb_xlib_threads_sequence_lost", 
    file=file@entry=0x7f3ee68ac3f3 "xcb_io.c", line=line@entry=263, function=function@entry=0x7f3ee68ac827 <__PRETTY_FUNCTION__.14864> "poll_for_event")
    at assert.c:101
#4  0x00007f3ee683a85a in poll_for_event (dpy=dpy@entry=0x1493800, queued_only=queued_only@entry=0) at xcb_io.c:260
#5  0x00007f3ee683a90c in poll_for_response (dpy=dpy@entry=0x1493800) at xcb_io.c:278
#6  0x00007f3ee683abfd in _XEventsQueued (dpy=0x1493800, mode=mode@entry=1) at xcb_io.c:362
#7  0x00007f3ee683aeae in _XFlush (dpy=<optimized out>) at xcb_io.c:518
...

Comment 5 RHEL Program Management 2023-09-11 15:05:02 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 6 RHEL Program Management 2023-09-11 17:00:44 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.