Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: interesting part of backtrace: Thread 1 (Thread 0x7ffff7fb0940 (LWP 13531)): #0 0x00007ffff52ae8a5 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #1 0x00007ffff52b0085 in abort () at abort.c:92 #2 0x000000389664337a in IA__g_logv (log_domain=0x389668a0e6 "GLib", log_level=<value optimized out>, format=0x3896697fe0 "The thread system is not yet initialized.", args1=0x7fffffffd360) at gmessages.c:549 #3 0x0000003896643413 in IA__g_log (log_domain=<value optimized out>, log_level=<value optimized out>, format=<value optimized out>) at gmessages.c:569 #4 0x000000389666059e in g_thread_fail () at gthread.c:591 #5 0x00007ffff64a264e in usbredirhost_open_full (usb_ctx=0x69cd60, usb_dev_handle=0x0, log_func=0x7ffff78f96e0 <usbredir_log>, read_guest_data_func=0x7ffff78f9670 <usbredir_read_callback>, write_guest_data_func=<value optimized out>, flush_writes_func=<value optimized out>, alloc_lock_func=0x7ffff78f92d0 <usbredir_alloc_lock>, lock_func=0x7ffff78f92e0 <usbredir_lock_lock>, unlock_func=0x7ffff78f9300 <usbredir_unlock_lock>, free_lock_func=0x7ffff78f9320 <usbredir_free_lock>, func_priv=0x7bd400, version=0x7ffff799517a "spice-gtk 0.11", verbose=2, flags=1) at usbredirhost.c:610 #6 0x00007ffff78f959d in spice_usbredir_channel_set_context (channel=0x7bd400 [SpiceUsbredirChannel], context=<value optimized out>) at channel-usbredir.c:193 #7 0x00007ffff78fc58b in channel_new (session=<value optimized out>, channel=0x7bd400 [SpiceUsbredirChannel], user_data=0x680ba0) at usb-device-manager.c:494