Bug 65185 - Xspice: failure to bind to port should be an error, not a warning
Summary: Xspice: failure to bind to port should be an error, not a warning
Status: RESOLVED FIXED
Alias: None
Product: Spice
Classification: Unclassified
Component: xorg qxl (show other bugs)
Version: unspecified
Hardware: Other All
: medium enhancement
Assignee: Spice Bug List
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-30 17:18 UTC by Zbigniew Jedrzejewski-Szmek
Modified: 2014-11-10 10:35 UTC (History)
5 users (show)

See Also:
i915 platform:
i915 features:

Attachments

Description Zbigniew Jedrzejewski-Szmek 2013-05-30 17:18:47 UTC 
Xspice isn't very useful without the TCP connection possibility. When the port is busy:

$ Xspice --disable-ticketing --xsession /usr/bin/gnome-terminal :0 --port 5900
...
(/usr/bin/Xspice:6677): Spice-Warning **: reds.c:3037:reds_init_socket: reds_init_socket: binding socket to :5900 failed
...

If the port was explicitly requested, failure to bind should be prominently displayed, and preferably result in a termination of Xspice.

xorg-x11-server-Xspice-0.1.1-0.8.20130514git77a1594.fc19.x86_64
Comment 1 David Jaša 2013-05-30 19:09:30 UTC 
qemu bug about the same: https://bugzilla.redhat.com/show_bug.cgi?id=682227
Comment 3 Marc-Andre Lureau 2014-11-10 10:35:06 UTC 
commit 97c7c183d7d8585d93eab4f13645acb2d47ca763
Author: Marc-André Lureau <marcandre.lureau@redhat.com>
Date:   Mon Nov 3 01:14:48 2014 +0100

    Xspice: fail if server can't be initialized

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.