FedoraThis forum is for the discussion of the Fedora Project.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have Fedora 20, and trying to install RealVNC. I read where I have to uninstall tiger vnc and Anaconda, and did this. When I try:
rpm -ifvh --nodeps VNC-Server-5.2.1-Linux-x64.rpm
Iget the below error
Please advise, Thanks AJ
Preparing... ################################# [100%]
file /usr/bin/Xvnc from install of realvnc-vnc-server-5.2.1.5668-1.x86_64 conflicts with file from package tigervnc-server-minimal-1.3.0-7.fc20.x86_64
file /usr/bin/vncpasswd from install of realvnc-vnc-server-5.2.1.5668-1.x86_64 conflicts with file from package tigervnc-server-minimal-1.3.0-7.fc20.x86_64
file /usr/share/man/man1/Xvnc.1.gz from install of realvnc-vnc-server-5.2.1.5668-1.x86_64 conflicts with file from package tigervnc-server-minimal-1.3.0-7.fc20.x86_64
file /usr/share/man/man1/vncpasswd.1.gz from install of realvnc-vnc-server-5.2.1.5668-1.x86_64 conflicts with file from package tigervnc-server-minimal-1.3.0-7.fc20.x86_64
UPDATE:-----------------------
I got this to work by removing tigervnc and anaconda (may not need to remove anaconda)
rpm -ifvh --nodeps VNC-Server-5.2.1-Linux-x64.rpm
or
yum localinstall VNC-Server-5.2.1-Linux-x64.rpm
------------------------
Now? Can anyone tell me two things?
1) how to make Fedora autologin. I already do not use a password, but the user icon comes up and I have to click it...would like it to go straight to desktop
2) how to make RealVNC start as a service and be running automatically soon as it boots up
thanks AJ
Last edited by Janning; 11-02-2014 at 01:33 PM.
Reason: update
If I had to guess Fedora has a script that takes you to the login screen.
I don't edit initialization script's so maybe another member will be able to tell you how to avoid the log-in. I would imagine you could comment out the argument or just delete that whole line.
To get it started automatically ( the vncserver that is) is to put
the your line at the top of /etc/rc.d/rc.local.
This file gets executed after all the init scripts and right before it
brings up the login prompt.
I had my realvnc starting up before the logon page, but I forgot how I did this? I upgraded to Fedora 21, now Realvnc will not start until after I login. Can someone tell me how to have realVNC start up during reboot once again?
Thanks AJ
I'm now upgraded to Fedora 21. Using RealVNC 5.2.2. I'm able to auto login, and therefore RealVNC is up and running after reboot.
HOWEVER, since my upgrade to Fedora 21, FROM my windows notebook, TO the Fedora 21, I can see the Fedora desktop...but it is not refreshing.
The desktop and icons are all there, the mouse is there and moves, but clicking on icons does nothing. In the upper right hand corner,
I get the RealVNC box saying 1 user is connected...just flashing.
I'm now upgraded to Fedora 21. Using RealVNC 5.2.2. I'm able to auto login, and therefore RealVNC is up and running after reboot.
HOWEVER, since my upgrade to Fedora 21, FROM my windows notebook, TO the Fedora 21, I can see the Fedora desktop...but it is not refreshing.
The desktop and icons are all there, the mouse is there and moves, but clicking on icons does nothing. In the upper right hand corner,
I get the RealVNC box saying 1 user is connected...just flashing.
Please advise
Thanks much, James.
Are you using Windows to remotely connect to Fedora?
I'm not sure why the icons are not working.(maybe missing a library)
I'm going to have to do some research to find out more for you.
Yes, as my "from" - viewer Notebook, it is Windows 8.1, RealVNC 5.2.2...as I said it worked fine on Fedora 20 and GNOME. Now on Fedora 21 / GNOME 3.14.2 I get this issue.
From the same notebook windows 8.1 I can RealVNC just fine into my other Fedora 20 / KDE 5 Plasma...even after upgrading to Fedora 21,,, no issues.
I had this issue on Kubuntu/KDE5 plasma...RealVNC wants to blame KDE5 plasma, well Fedora 21 / GNOOME 3.14.2 has no plasma, and the Fedora 21 / KDE 5 plasma works fine.
Please let me know, if you know the answer to this. I'm sure its real simple, just not in my area of knowledge.
Thanks AJ
Oh the icons do work...if I go to the Fedora PC...all is well. If on the windows 8.1 PC, viewing into Fedora 21, and click an icon...it does work (nouse arrow will do the small spin and turn back to an arrow)...I just do not see the app open on the view-from win 8.1 PC...if I walk over to the Fedora box, the clicked icon app did open...what's on the Fedora box, is not refreshed back to the viewing win 8.1 box. If I close RealVNC viewer, go to Fedora box and open say 5 apps, they all appear. If I again login the Windows 8.1 RealVNC view...I do not see the 5 apps, only what that last screen was the last time realVNC view was logged in.
Yes, as my "from" - viewer Notebook, it is Windows 8.1, RealVNC 5.2.2...as I said it worked fine on Fedora 20 and GNOME. Now on Fedora 21 / GNOME 3.14.2 I get this issue.
From the same notebook windows 8.1 I can RealVNC just fine into my other Fedora 20 / KDE 5 Plasma...even after upgrading to Fedora 21,,, no issues.
I had this issue on Kubuntu/KDE5 plasma...RealVNC wants to blame KDE5 plasma, well Fedora 21 / GNOOME 3.14.2 has no plasma, and the Fedora 21 / KDE 5 plasma works fine.
Please let me know, if you know the answer to this. I'm sure its real simple, just not in my area of knowledge.
Thanks AJ
Oh the icons do work...if I go to the Fedora PC...all is well. If on the windows 8.1 PC, viewing into Fedora 21, and click an icon...it does work (nouse arrow will do the small spin and turn back to an arrow)...I just do not see the app open on the view-from win 8.1 PC...if I walk over to the Fedora box, the clicked icon app did open...what's on the Fedora box, is not refreshed back to the viewing win 8.1 box. If I close RealVNC viewer, go to Fedora box and open say 5 apps, they all appear. If I again login the Windows 8.1 RealVNC view...I do not see the 5 apps, only what that last screen was the last time realVNC view was logged in.
I think your going to need a member with more experience with RealVNC and Windows.
I'm sorry I haven't used Windows in 4 years and don't know.
If I close RealVNC viewer, go to Fedora box and open say 5 apps, they all appear. If I again login the Windows 8.1 RealVNC view...I do not see the 5 apps, only what that last screen was the last time realVNC view was logged in.
That's odd that you can see the apps in FC but not in Windows.
I would lean more towards maybe something in your Windows settings may not be set correctly.
Look through a few tutorials on VNC and Windows 8 to ensure you have it set up right.
It can't be a windows issue, it did work on fedora 20/ GNOME...but stopped when I upgraded to 21...and it does work on a 2nd fedora 21/KDE 5 plasma box
It can't be a windows issue, it did work on fedora 20/ GNOME...but stopped when I upgraded to 21...and it does work on a 2nd fedora 21/KDE 5 plasma box
When did FC 21 get released?
When I was running Fedora I use to wait at least 3 months for the Developers to get the bugs out before I would do a fresh installation.
When you upgraded did you use fedup or did you perform a fresh installation?
as above
i normally would wait 60 to 90 days to upgrade fedora
then do a fresh clean install of a very min. install
( after 90 days a full fedora install would have 3+ gig's of updates)
there are often a TON of config files that would not work with a "in place upgrade"
i am guessing this was resolved ( first post)
i noticed this tid bit
Quote:
rpm -ifvh --nodeps VNC-Server-5.2.1-Linux-x64.rpm
one really SHOULD NOT do it that way
use yum and NOT "rpm"
and do NOT use the FORCE and NO DEP unless you KNOW!!! for 100% FACT!!!! exactly what will happen
and what WILL NOT HAPPEN
-- seeing as that is almost NEVER ....
use this
Code:
su -
cd /to/the/location/of/the/rpm
yum localinstall VNC-Server-5.2.1
--- or if that dose not work the full name --
yum localinstall VNC-Server-5.2.1-Linux-x64.rpm
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.