Description of problem:
Let's get the ball rolling on this one...
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Created attachment 522415 [details]
Created attachment 522416 [details]
Created attachment 522417 [details]
Created attachment 522418 [details]
Created attachment 522419 [details]
Created attachment 522420 [details]
Created attachment 522421 [details]
Created attachment 522422 [details]
Created attachment 522423 [details]
Created attachment 522424 [details]
Created attachment 522425 [details]
Created attachment 522426 [details]
Passes simple telnet test...
[root@localhost system]# systemctl start vnc-1024x768x16.socket
[root@localhost system]# systemctl status vnc-1024x768x16.socket
vnc-1024x768x16.socket - Vnc Remote Activation Socket ( 1024x768x16 )
Loaded: loaded (/lib/systemd/system/vnc-1024x768x16.socket; disabled)
Active: active (listening) since Fri, 09 Sep 2011 21:46:05 +0000; 1min 4s ago
Accepted: 1; Connected: 0
[root@localhost system]# telnet localhost 5900
Connected to localhost.
Escape character is '^]'.
Connection closed by foreign host.
And note there is still a (tight) window to have this in F16
Once package and shipped your package should no longer have to depend on xinetd
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.
(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)
More information and reason for this action is here:
Given that I have left the project and a new individual may or may not continue with systemd integration in the project by submitting new feature following whatever demands FPC and FESCo might have and thus new units in the process I'm closing this and all remaining bugs I had submitted for this particular feature as WONTFIX
I'd like to keep this open. Now that I understand systemd a little better and have time, would like to integration this sooner or later (preferably sooner).
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.
marking futurefeature, so it avoids autoclose