Bug 1382328 - Backgrounding spicy causes it to freeze
Summary: Backgrounding spicy causes it to freeze
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: spice-gtk
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Marc-Andre Lureau
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-06 11:18 UTC by Hans de Goede
Modified: 2016-11-03 23:53 UTC (History)
7 users (show)

Fixed In Version: spice-gtk-0.32-4.fc24
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-03 23:53:27 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Hans de Goede 2016-10-06 11:18:19 UTC 
Description of problem:
Backgrounding spicy causes it to freeze

Version-Release number of selected component (if applicable):
spice-gtk-tools-0.32-2.fc25.x86_64

How reproducible:

Steps to Reproduce:
1. Start spicy from a terminal as: "spicy&"
2. Try to connect to a spice server
3. spicy is hung, needs to be forgrounded before it will continue

Actual results:
spicy is hung, needs to be forgrounded before it will continue.

Expected results:
spicy works normally.
Comment 1 Marc-Andre Lureau 2016-10-06 11:47:22 UTC 
This is not new, it hangs in tcsetattr(). sending a fix upstream
Comment 2 Fedora Update System 2016-10-11 03:22:40 UTC 
spice-gtk-0.32-4.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-fea866fa85
Comment 3 Fedora Update System 2016-11-03 23:53:27 UTC 
spice-gtk-0.32-4.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.