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:
Xspice doesn't respond/can't be connected to/stays black if connected to previously/uses 100% of CPU when running certain applications on it first. 

Version-Release number of selected component (if applicable):
xorg-x11-server-Xspice-0.1.0-2.el7.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Open a display running Xspice on your machine( Xspice --disable-ticketing --port 3000 :3.0 )
2. Connect to it (remote-viewer spice://localhost:3000 )
   -- you should have black screen now, that's ok and expected as there are no clients running on the server just yet
3. Run a certain (gnome-terminal) client on Xspice: 
   DISPLAY=:3.0 gnome-terminal
  
Actual results:
Xspice starts using 100% CPU and doesn't respond to anything.

Notes: Happens also with metacity.

Doesn't happen if the first app is: xterm, icewm.

To be more precise:

This works:
1. xterm. 2. anything

This fails:
1. gnome-terminal
or
1. metacity

Failure looks like memory corruption, since it is looking on sched_yield with a 0 sized ring.

I've tested with xorg-x11-server-Xspice-0.1.1-0.13.20130703git8b03ec16.el7 and I no longer see a problem. I've tried these scenarios:

1. start Xspice
2. connect with remote-viewer
3. start gnome-terminal

1+2 same
3. start mutter
4. start gnome-terminal

both result in functional gnome terminal and mutter (when it is run, i.e. the second case).

I've also tried reversing the order of remote-viewer and application start, it still works.

Please let me know if this version works for you to so I can close the bug. If you have the time you could check which version is the lowest where the bug is fixed, it would be good to know what actually fixed it.

Alon

Sorry for the delay. It's fixed in xorg-x11-server-Xspice-0.1.1-5.el7.x86_64

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.