Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Hey I was wondering if anyone could solve this problem. I am connecting to a fedora box from a windows 7 box using tightvnc. The problem is that when I connect I am not prompted to log into my Linux box, therefore I am left there just looking at the fedora background without the ability to do anything. I read a thread here saying it might be the firewall, so I disabled windows firewall and then connected but still had the same issue. Any ideas on how to fix this?
This "fedora server" have a public IP, (internet or intranet)?
How was it installed on the server and when was the last time it worked?
What user are you trying to connect as? More than one? root? ???
"fedora" has like 21 versions now, which one?
output please. Sanitize it if necessary.
Since you say you get a desktop with nothing on it and can't do anything, this suggests that the firewall may not be an|the issue, however, https://wiki.archlinux.org/index.php/Vncserver says that 5901 should be opened.
[root@localhost ~]# cat /etc/sysconfig/vncservers
# THIS FILE HAS BEEN REPLACED BY /lib/systemd/system/vncserver@.service
[root@localhost ~]# cat /lib/systemd/system/vncserver@.service
# The vncserver service unit file
# Quick HowTo:
# 1. Copy this file to /etc/systemd/system/vncserver@:<display>.service
# 2. Edit <USER> and vncserver parameters appropriately
# ("runuser -l <USER> -c /usr/bin/vncserver %i -arg1 -arg2")
# 3. Run `systemctl daemon-reload`
# 4. Run `systemctl enable vncserver@:<display>.service`
# DO NOT RUN THIS SERVICE if your local area network is
# untrusted! For a secure way of using VNC, you should
# limit connections to the local host and then tunnel from
# the machine you want to view VNC on (host A) to the machine
# whose VNC output you want to view (host B)
# [user@hostA ~]$ ssh -v -C -L 590N:localhost:590M hostB
# this will open a connection on port 590N of your hostA to hostB's port 590M
# (in fact, it ssh-connects to hostB and then connects to localhost (on hostB).
# See the ssh man page for details on port forwarding)
# You can then point a VNC client on hostA at vncdisplay N of localhost and with
# the help of ssh, you end up seeing what hostB makes available on port 590M
# Use "-nolisten tcp" to prevent X connections to your VNC server via TCP.
# Use "-localhost" to prevent remote VNC clients connecting except when
# doing so through a secure tunnel. See the "-via" option in the
# `man vncviewer' manual page.
Description=Remote desktop service (VNC)
I have read several reports on the web and experienced for myself that tigervnc-server does not work with Gnome 3 unless you are in fallback mode. I'm on Fedora 18 and able to get tigervnc-server to work, but only if the user executing the vncserver command has Gnome 3 in fallback mode. If Gnome 3 is not in fallback mode you get exactly what you described in your initial post. Another option is to use vino-server instead to connect to Gnome 3 in standard experience mode, but you must have a running Gnome session that the client can connect to.
To explain the root only login issue you need to understand a little more about how vnc works. vnc is not like a regular login. When you connect you don't specify a user to connect to, you specify a display. If the display you are connecting to is running as root, root will be your user. So you need to start either vncserver or vino on fedora with the user you want to connect to with the vnc client. The password that you use to connect is set using vncpasswd in the case of tigervnc and with the Desktop Sharing application in the case of vino.
Let me know if you want specifics to setup either vncserver [tigervnc-server] or vino-server [vino].
See also Bug 896648 - vncserver fails to load gnome 3 session
Last edited by wmakowski; 11-29-2013 at 08:38 PM.
Reason: Added bug report
There are a couple ways. One is to login normally as the user, go to System Settings -> Details -> Graphics and then there is a switch to turn forced fallback mode on or off. You'll want to turn it on. After that you need to logout for it to take effect. If the vncserver was running it will need to be stopped and started as well so it picks up the new forced fallback mode. It works, but it means that this user will run in fallback mode however they login.
Another workaround is explained inside Bug 896648 Comment 5. They place a few extra commands inside /home/user/.vnc/xstartup to make the vncserver start Gnome in fallback.