Find the answer to your Linux question:
Results 1 to 9 of 9
Hello all, Let me start off by saying that I am very new to linux. ie still reading linux for dummies. I am also new to this forum so please ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    May 2012
    Posts
    4

    Installing RealVNC on RedHat Enterprise Linux 6


    Hello all,

    Let me start off by saying that I am very new to linux. ie still reading linux for dummies. I am also new to this forum so please take that into consideration. I am a Windows Admin and I am trying to expand my knowlege. I am still trying to understand the basics of this.

    I have been tasked with setting up a RedHat Server and making sure that we could access it via VNC. The issue is when I try and install RealVNC I get the following error
    " rpm vnc-4_1_3-x86_linux.rpm -i
    error: Failed dependencies:
    ld-linux.so.2 is needed by vnc-4.1.3-1.i386
    libc.so.6 is needed by vnc-4.1.3-1.i386
    libdl.so.2 is needed by vnc-4.1.3-1.i386
    libICE.so.6 is needed by vnc-4.1.3-1.i386
    libm.so.6 is needed by vnc-4.1.3-1.i386
    libSM.so.6 is needed by vnc-4.1.3-1.i386
    libstdc++-libc6.2-2.so.3 is needed by vnc-4.1.3-1.i386
    libX11.so.6 is needed by vnc-4.1.3-1.i386
    libXext.so.6 is needed by vnc-4.1.3-1.i386
    libXtst.so.6 is needed by vnc-4.1.3-1.i386
    libc.so.6(GLIBC_2.0) is needed by vnc-4.1.3-1.i386
    libc.so.6(GLIBC_2.1) is needed by vnc-4.1.3-1.i386
    libc.so.6(GLIBC_2.1.3) is needed by vnc-4.1.3-1.i386
    libc.so.6(GLIBC_2.2) is needed by vnc-4.1.3-1.i386
    libm.so.6(GLIBC_2.0) is needed by vnc-4.1.3-1.i386
    [Admin Test Downloads]$ "

    I have been all over the internet trying to figure this out but have had no luck.

    I am not sure if the libaries are not installed, or if they just are not pathed correctly so that the RPM installer knows where they are.

    Thanks for all your help in advance.

  2. #2
    Administrator MikeTbob's Avatar
    Join Date
    Apr 2006
    Location
    Texas
    Posts
    7,864
    Hello and Welcome.
    Using the RPM method is the "old school" way of installing programs and whatnot into RPM based systems. The new way is by using YUM, which in turn uses RPM's downloaded from a central repository.
    You can still use RPM's but it becomes very difficult to keep track of all the depends that each program needs to be installed first to run correctly. You can find out more here, about RPM's
    RPM Guide
    If you want to use the updated method of using YUM, try this link. Yum does all the work of RPM for you.
    Yum - FedoraProject
    I do not respond to private messages asking for Linux help, Please keep it on the forums only.
    All new users please read this.** Forum FAQS. ** Adopt an unanswered post.

    I'd rather be lost at the lake than found at home.

  3. #3
    Trusted Penguin Irithori's Avatar
    Join Date
    May 2009
    Location
    Munich
    Posts
    3,422
    In addition to what MikeTbob said:

    First of all:
    Are you sure, you even need a gui and vnc? There are usecases, of course.
    But imho, more often than not unix machines are console and ssh only.
    For example: None of my several hundred machines does have a gui.

    If you do need it, then I would suggest to install TigerVNC
    Why? Because it is part of the standard RedHat rpm repository and therefore just a command away:
    Code:
    yum install tigervnc-server
    In general it is a good idea to search the repo first and install from there.
    Background:
    In windows, everything an application needs is in one directory.
    (This is an oversimplification. But please bare with me for the sake of an easy explanation)
    In linux, an app can depend on many other apps or libs.
    Each of these are developed by separate people.
    The gain from that is, that an application developer doesnt have to reinvent the wheel for e.g. ssl or compression or <whatever>

    The package maintainers of a given linux distribution will then take the source codes of these apps/libs and create rpms out of them.
    As a consequence, rpms are not interchangeable between distributions (At least, it is not a good idea)

    So if you need an application, that is not in your repo, then you need to find an rpm for redhat 6.
    Or compile it yourself.
    You must always face the curtain with a bow.

  4. $spacer_open
    $spacer_close
  5. #4
    Linux Newbie
    Join Date
    Apr 2012
    Posts
    112
    I agree with Irithori, generally speaking there is very little need to use a GUI for a Unix Server but since its part of the RHCSA I wrote a post about it.

  6. #5
    Just Joined!
    Join Date
    May 2012
    Posts
    4
    Quote Originally Posted by MikeTbob View Post
    Hello and Welcome.
    Using the RPM method is the "old school" way of installing programs and whatnot into RPM based systems. The new way is by using YUM, which in turn uses RPM's downloaded from a central repository.
    Mike,

    Thanks for the reply. So I attempted to install this using YUM. It appears that I am getting the same or really similar errors. I read the YUM commands, the site will not let me link a url yet but it was the yum_baseurl_org site.

    Here is what I am getting now.
    "sudo yum install vnc-4_1_3-x86_linux.rpm
    [sudo] password for Admin:
    Loaded plugins: product-id, refresh-packagekit, security, subscription-manager
    Updating certificate-based repositories.
    Setting up Install Process
    Examining vnc-4_1_3-x86_linux.rpm: vnc-4.1.3-1.i386
    Marking vnc-4_1_3-x86_linux.rpm to be installed
    Resolving Dependencies
    --> Running transaction check
    ---> Package vnc.i386 0:4.1.3-1 will be installed
    --> Processing Dependency: ld-linux.so.2 for package: vnc-4.1.3-1.i386
    --> Processing Dependency: libc.so.6 for package: vnc-4.1.3-1.i386
    --> Processing Dependency: libdl.so.2 for package: vnc-4.1.3-1.i386
    --> Processing Dependency: libICE.so.6 for package: vnc-4.1.3-1.i386
    --> Processing Dependency: libm.so.6 for package: vnc-4.1.3-1.i386
    --> Processing Dependency: libSM.so.6 for package: vnc-4.1.3-1.i386
    --> Processing Dependency: libstdc++-libc6.2-2.so.3 for package: vnc-4.1.3-1.i386
    --> Processing Dependency: libX11.so.6 for package: vnc-4.1.3-1.i386
    --> Processing Dependency: libXext.so.6 for package: vnc-4.1.3-1.i386
    --> Processing Dependency: libXtst.so.6 for package: vnc-4.1.3-1.i386
    --> Processing Dependency: libc.so.6(GLIBC_2.0) for package: vnc-4.1.3-1.i386
    --> Processing Dependency: libc.so.6(GLIBC_2.1) for package: vnc-4.1.3-1.i386
    --> Processing Dependency: libc.so.6(GLIBC_2.1.3) for package: vnc-4.1.3-1.i386
    --> Processing Dependency: libc.so.6(GLIBC_2.2) for package: vnc-4.1.3-1.i386
    --> Processing Dependency: libm.so.6(GLIBC_2.0) for package: vnc-4.1.3-1.i386
    --> Finished Dependency Resolution
    Error: Package: vnc-4.1.3-1.i386 (/vnc-4_1_3-x86_linux)
    Requires: libc.so.6(GLIBC_2.2)
    Error: Package: vnc-4.1.3-1.i386 (/vnc-4_1_3-x86_linux)
    Requires: libc.so.6(GLIBC_2.1)
    Error: Package: vnc-4.1.3-1.i386 (/vnc-4_1_3-x86_linux)
    Requires: libc.so.6(GLIBC_2.0)
    Error: Package: vnc-4.1.3-1.i386 (/vnc-4_1_3-x86_linux)
    Requires: libX11.so.6
    Error: Package: vnc-4.1.3-1.i386 (/vnc-4_1_3-x86_linux)
    Requires: libc.so.6(GLIBC_2.1.3)
    Error: Package: vnc-4.1.3-1.i386 (/vnc-4_1_3-x86_linux)
    Requires: ld-linux.so.2
    Error: Package: vnc-4.1.3-1.i386 (/vnc-4_1_3-x86_linux)
    Requires: libstdc++-libc6.2-2.so.3
    Error: Package: vnc-4.1.3-1.i386 (/vnc-4_1_3-x86_linux)
    Requires: libdl.so.2
    Error: Package: vnc-4.1.3-1.i386 (/vnc-4_1_3-x86_linux)
    Requires: libm.so.6(GLIBC_2.0)
    Error: Package: vnc-4.1.3-1.i386 (/vnc-4_1_3-x86_linux)
    Requires: libICE.so.6
    Error: Package: vnc-4.1.3-1.i386 (/vnc-4_1_3-x86_linux)
    Requires: libXext.so.6
    Error: Package: vnc-4.1.3-1.i386 (/vnc-4_1_3-x86_linux)
    Requires: libc.so.6
    Error: Package: vnc-4.1.3-1.i386 (/vnc-4_1_3-x86_linux)
    Requires: libSM.so.6
    Error: Package: vnc-4.1.3-1.i386 (/vnc-4_1_3-x86_linux)
    Requires: libXtst.so.6
    Error: Package: vnc-4.1.3-1.i386 (/vnc-4_1_3-x86_linux)
    Requires: libm.so.6
    You could try using --skip-broken to work around the problem
    You could try running: rpm -Va --nofiles --nodigest
    [AdminTest Downloads]$ "

    I also looked at the help file but could not find a way to have the dependancies automatically load. I am assuming that this is what I need to do, have it look for what is missing and then go to a respository and install the files from that.

    Thanks again for taking time to look at this issue.

  7. #6
    Trusted Penguin Irithori's Avatar
    Join Date
    May 2009
    Location
    Munich
    Posts
    3,422
    I believe the RPM you have is not meant for redhat 6.
    As briefly explained above: This causes issues, namely dependency issues.

    Is TigerVNC an option for you?
    You must always face the curtain with a bow.

  8. #7
    Just Joined!
    Join Date
    May 2012
    Posts
    4
    Quote Originally Posted by Irithori View Post
    I believe the RPM you have is not meant for redhat 6.
    As briefly explained above: This causes issues, namely dependency issues.

    Is TigerVNC an option for you?
    Many thanks Irithori, I tried posting another reply so this may be a dupe, but I think that the system logged me out before my other reply was posted.

    The info on the RPM package is very good to know.

    I was able to use TigerVNC and was successfully able to remote into the system. The issue I have now is that if I reboot the system TigerVNC will not work untill the user account is logged in.

    Is there a way to chanage this? I was using www_confignotes_com/2011/08/rhel-vnc-server-configuration/ as a guide. I still cannot post with urls yet, sorry about the adjusted web address.

    I need to be able to reboot the server and log in with VNC. I also noticed that I set the password, but I was not prompted for a password when I tried to connect.

    Thanks again for all your help.

  9. #8
    Just Joined!
    Join Date
    May 2012
    Posts
    4

    More Info

    I think I found out why it is not working before login. When I click on the ! for the boot messages I see that there is an error starting

    "Starting VNC server: 2:Admin vcserver: geometry 800x600 is invalid"

    I tried changing it to 1024x768 but got the same message.

  10. #9
    Trusted Penguin
    Join Date
    May 2011
    Posts
    4,353
    Quote Originally Posted by tdisalvo View Post
    I think I found out why it is not working before login. When I click on the ! for the boot messages I see that there is an error starting

    "Starting VNC server: 2:Admin vcserver: geometry 800x600 is invalid"

    I tried changing it to 1024x768 but got the same message.
    where did you make those changes, as in, what file did you edit?

    you want to be editing this file:
    Code:
    /etc/sysconfig/vncservers
    there are examples in it on how to add a vnc session for a given user (use the VNCSERVERS and VNCSERVERARGS variables). it is kind of non-intuitive.

    also, you need to have the session start-up file properly configured, as well as the VNC password file, for the given user, e.g.:
    Code:
    ~/.vnc/xstartup  <-- bash script
    ~/.vnc/passwd    <-- ASCII file containing encrypted password
    the xstartup file can contain:
    Code:
    #!/bin/bash
    #exec fluxbox
    #exec blackbox
    exec gnome-session
    and the vnc password can be created by running the "vncpasswd" command as the given user.

    note: both of these files are created the first time you run "vncserver :1" as the given user (i think). the :1 is the display number (which is used in the /etc/sysconfig/vncserver file).

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •