After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 557671 - vino-server remains inoperative until user logs in
vino-server remains inoperative until user logs in
Status: RESOLVED DUPLICATE of bug 352349
Product: vino
Classification: Applications
Component: Server
2.20.x
Other All
: Normal normal
: ---
Assigned To: Vino Maintainer(s)
Vino Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2008-10-23 22:09 UTC by bzb.dev001
Modified: 2008-10-23 22:34 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description bzb.dev001 2008-10-23 22:09:34 UTC 
Please describe the problem:
I'm currently running openSuse 10.3.

When a remote openSuse system boots up and no user has logs in yet.  A local openSuse system cannot use vncviewer to access the remote system.  When attempted,  the console shows the following message:

$ vncviewer 192.168.15.12
vncviewer: ConnectToTcpAddr: connect: Connection refused
Unable to connect to VNC server


It is only after a user at the remote system has logged in, then the local user running vncviewer can access the remote system.


Steps to reproduce:
1. 
2. 
3. 


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Jonh Wendell 2008-10-23 22:34:32 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 352349 ***