I just installed VNCServer on my Ubuntu box. I've tested the connection on my Windows box and connect fine.If I were to restart Ubuntu, would the VNCServer start automatically? If not, how would I do this?
I am currently using FC10 on a Dell 4600 with 2GB of ram. I love Linux as it is the most stable OS around. My end goal is to have the machine boot and start the vncserver automatically, eventually using an ssh tunnel to make it secure. My main problem is the vncserver is not starting on boot, I must login as a user then it works great. the error I get is
[Code]....
Basically what happens is the vncserver fails on boot however, if I login to the Fedora box I am able to connect and I get the GDM login screen. I have read many, many posts but have not been able to get over the boot issue. I really want to make this a headless box I can put in another room so I have more room for my musical gear.
When I start the vncserver process, I get a message saying "Starting VNC server: no displays configured." I edited the /root/.vnc/xstartup file and changed twm & to say "gnome-session &" (Without quotes). Not sure why I am still seeing this error. It's CentOS 5.4.
played around with Plymouth Manager yesterday, and today, my system would not start. I got some help from #ubuntu, and to my surprise, startx ran without problems. sudo service gdm start also worked perfectly. However, when I boot up my computer, I am always taken to the recovery screen. How can I stop this from happening, get my boot screen back, and make everything work as it should?I'm on Ubuntu 10.10 32-bit with an nVidia GeForce 8800 GT and version current on the nVidia restricted drivers.
and i have to type bash everytime to get it running. i found a bandaid fix by having it type bash at the "custom command" profile preference... but i still consider the problem to be unsolved, because i still have to manually type 'bash' whenever i log remotely (putty). it seems like something happened, and now bash is not loaded by the terminal by default like it should.
PS: i already tried 'cp /etc/skel/.bashrc ~./bashrc', and it didn't seem to do anything.
I am using Ubuntu 9.10, fairly fresh install. Had one hard reset since I installed it, which could be when the problem started. Also, I was messing a bit with profiles, switching their ID's and adding/deleting them (not sure if that would be the problem).
I'm moving a homebrew arcade cabinet I have in my sitting room over from Gentoo to Ubuntu. Gentoo's served me well for a couple of years, but it refuses to recognise a touchscreen I recently installed on the cab, so I thought I'd give Ubuntu a try.
There is very little space on the SATA DOM inside the board in the cab, so I try and put as little OS on there as possible. To that end, I installed the minimal iso, and then apt-got X. I manually configured xorg.conf to make both monitors attached to the cab work, and I can enter X fine from the command line.
But what I need to do is have X start on powerup and automatically run my game. In Gentoo this is as simple as putting "xinit [GAME]" into /etc/init.d/local.start (the equivalent of rc.local). No login required, the prompt didn't even come up until I'd exited the game.
However, if I try and do this in Ubuntu, X can't find any devices, even though rc.local is at position 99. I've tried putting the lines in rc.local as well as manually update-rc.d-ing my own files, but no luck. X refuses to start until after the login.
So what seem to need is some way of automatically logging in as root on the command line, starting X, then running my game.
I am helping a local genealogy society set up their research center. They want three workstations and a single data server. The genealogy program of choice was GRAMPS, which I have used for years a Wonderful program! No data is going to be input on the workstations the users are simply researching existing data on the server.
Since several RDP-based Wyse thin client units were available for free as were monitors and keyboards, the decision was quickly made to use an RDP based client/server system. Using VNC was unacceptable due to its speed and latency issues, plus, it isn't supported by the Wyse thin client units ONLY RDP and Cytrix.
Using Microsoft's server OS and Terminal Server package was far, far beyond the society's budget. We briefly considered equipping a Windows XP box with a copy ThinSoft's RDP server package, WinConnect Server XP, but its $300 price tag was still too much for the society.
The decision was to use Linux for the server. At first we considered LTSP but it is oriented towards PXE net boots and, while this may have worked, its complexity scared us off and we opted for what, we initially thought, was a much simpler solution XRDP.
We were right and wrong at the same time. It is simple to set up very simple, but the lack of documentation places many pitfalls in front of you, PLUS the solution is distribution dependent.
I spent many hours on this issue. There are numerous sources on the web citing solutions to running XRDP. Unfortunately, they all involve running vncserver against the destination logins. This is NOT what we desired. We wanted to be able to boot up the host system but not login at all, yet still be able to connect to a session via RDP.
I tried numerous distributions and eventually spending a lot of time going through the xrdp source code and planting out my own debug messages in /etc/xrdp/startsm.sh to output to a file in /tmp. Putting in ps -eS >> /tmp/xrdp.txt was particularly useful because it showed that xrdp/sesman DID launch an Xvnc, meaning that it was unnecessary to pre-launch vncserver, as most pundits recommend. The solution was figuring out how to connect to the Xvnc session created by sesman.
I discovered the solution somewhat by accident. It seems that the files created in the destination user's .vnc folder by vncserver were interfering with xrdp/sesman. Here is what worked. 1.Starting with a nearly virgin install of Ubuntu 10.04 beta 1, installed two users intended to be accessed for remote login via RDP. That is ALL that I did I never even logged into them. 2.My first entry xrdp.ini was unmodified except that ask was deleted from username=. Everything was unmodified.
3.Using tsclient on another machine, with the desired username, that was NOT logged in, and password pre-filled, I connected and received a nice Gnome desktop. 4.The session was on 5910. 5.While keeping this session active, I logged into the next login created for remote access and received my second nice Gnome sesktop on port 5911 automatically. Xrdp-sesman DOES automatically launch Xvnc in a useful way!
I can ONLY get this to work on Ubuntu version 10.04 e/w Gnome. It fails on CentOS 5.2, Xubuntu 9.10, SuperOS 9.10 and Lubuntu 10.04. In all cases xrdp was version 4.1.1, so the issue is not with xrdp/sesman it lies within the OS what, I do not know. I did not test KDE at all.
Code:
The system is running Ubuntu 10.04 LTS beta - the Lucid Lynx, amd64:
uname -a Linux ubu910 2.6.32-16-generic #25-Ubuntu SMP Tue Mar 9 16:33:12 UTC 2010 x86_64 GNU/Linux --------------------------------- Contents of /etc/xrdp/sesman.ini: --------------------------------- [Globals] ListenAddress=127.0.0.1
I have a couple apps that I cannot figure out how to prevent them from starting automatically upon logging in. They are NOT listed in my Startup Applications under preferences. For example, pidgin. Pidgin automatically starts at each login even though it is not in the startup apps nor can I find an option in pidgin itself. Tomboy is another. I always get an error that tomboy cannot be added to my panel when I restart. The error in the tomboy panel log is that tomboy is already running. Does ubuntu have a hidden "start up" folder like Windows does in the start menu? Where can I clear this file/folder?
Anyone know how to stop the pureftpd starting up automatically? I've tried the usual in /etc/init.d/pureftpd but it still starts and I need to log in and close it in the admin UI or in terminal.
I have posted this somewhere here before and solved it but can't seem to find it. Just waisted 50 minutes googling and checking man pages for upstart. By the way; are man pages written by someone using their tows to type and getting beaten by a stick for every character they type? It seems missing a lot of info. Anyway, I know smbd is started with /etc/init/smbd.conf and there is a line like:
Code: start on local-filesystems Now it needs to be started on? (manually) I can't seem to find any useful information but did seem to find the upstart man pages a hundred times or so (same info same missing parts). I would love to get involved writing documentation for these things if only I know what I was doing.
A server like Lighttpd or Apache starts automatically at boot after you install it. How do I stop it from auto starting? I'd prefer to manually start it when I need it.
i run opensuse 11.2 with kdebase4-4.3.5-0.1.1.x86_64 on a hp elitebook 8530w. when i start opensuse and the sound is initially turned off, it will be turned on while starting. if i turn it of manually (by pushing the appropriate button) it will be turned on again. I assume that there is a script like .bashrc for bash scripts which tells the system to turn on the sound. Does anyone knows whether there is such a script and if yes, where can i find it and edit it?
I recently upgraded to zenwalk 6.2 and xscreensaver now starts automatically so i have to input my password whenever i shut and reopen my laptop lid. how can i stop it from auto-starting.
Running openSuse 11.2-64 on a DualCore / 2Gb machine.I have 3 nfs shares described in my /etc/fstabAll three were mounted at boot time when I was connecting to the network through the wired interface (eth0).I need to use the wireless interface, and even if that interface is up and running well (I use ifup), the nfs client doesn't start... if just after boot I do a mount -a or simply a nfs start, everything comes up and runs well.This machine will not be used by myself, and the users cannot just jump into a command line and type nfs start or even mount -a (they would need su privileges...)I have disabled the eth0, killed the eth0 config (with yast) edited /etc/sysconfig/nfs and setted the NFS_START_SERVICE to yes to force the gssd and idmapd to always start even if there was no nfs entry in fstab, but nothing changed.
kde knetworkmanager is not starting on startup.i am starting this manually every time on login to connect to network..how to make it start automatically?
I am loading the file in Fortran. File looks something like this (shown below) I am interested in Velocity values and not Pressure values. Is there a way to code in Fortran which finds the staring LINE of Velocity values and ending LINE of values or I have to manually find the lines? IN this case it should return Starting line : 9 Ending line: 11
Firstly I remote login to a PC by telnet/sshAfter thatI type vncserver in the terminal.Then I gotvncserver: couldn't find "xauth" on your PATH.May I know what it is about and how to setup vncserver?
I set up 11.4 in my laptopnd, after updating and downloading the proper firmwareeverytihing runs great. I already configured the wireless network via the standard NetworkManager but the connection never starts automatically. When I boot up it reports all the wireless connections available and also let me connect to hidden networks (mine is not broadcasting so I have to use this option). I had to reconfigure my network options the first time I selected Hidden Networks but it connects fine. Please note I had already selected the "Automatic connection" optionSo the only question is how I configure my equipment so it connects automatically to the already configured network
this is probably something trivial but how can I auto start gdm on CentOS 5.4??I had to perform a text install due to Anaconda having some issues as I'm running Cent on Sun's VirtualBox.I have tried to add chkconfig --add gdm which didn't work, also there is no init.d script either for gdm so not sure if it's in a directory somewhere or if I have to create it manually??IF I run simply gdm from teh cli then everything is ok and starts fine....
I am trying to VNC into a server to which I have no physical access (but I can ask someone to start a session or something) but can ssh into. I have gotten a VNC session working by sshing in and running vncserver, although once the VNC session died in a confusing manner.
I don't know how to start a VNC session any way but vncserver, which is odd since I'm sure that Ubuntu's Remote desktop should somehow allow me to do this by default. The server by the way is being used as a desktop by someone else. Also, how do I tell if my VNC is encrypted and if it isn't how do I make sure it is?
In normal desktop GUI is working fine. But when in install VNCserver and tried to connect form my window machine through Ultra vnc it is not working properly. The issue I am facing is: when I am opening a terminal and enter later "m" from keyboard its work as a short for mail, and in case of later "s" the shortcut is "shutdown tab" those are present in panel. Then I remove those from panel and now I can enter the word m and s in terminal. The behavior is seems like a bug.
I used the cmd "vncserver" to start a vnc session, and it created a log file like this "/root/.vnc/linux-vzra:2.log". As time going on, the file "/root/.vnc/linux-vzra:2.log" became bigger and bigger, it is too huge indeed. How can I start a vnc session without a log file?
It is about vncserver. While I use Vncviewer connect to Desktop :0. The Kile picture is the same as that I am on the local machine. But, when I connect to the desktop created by vncserver,say Desktop :1. The Kile picture is pretty bad. I attached two pictures. One is for Desktop :0 and another is Desktop :1. I wonder how to make configurations to vncserver in order to make Kile look better.
I am setting up a server with Ubuntu Server edition. It is has 4gb of ram and had been working great the first week or so but something strange started happening about the same time I installed MythTV. After that, the server would slow down considerably and the ram being used would go from about 400megs up to all of the 4gb and use about 2gb or swap. After much research and investigating, I've narrowed it down to the vncserver starting up all 100 displays/sessions even if I try to specify one with : vncserver :1
I'm running a server that boots into runlevel 3. I can ssh into it but I only get a blank screen when I try to connect to the vncserver that's running on it. Is it possible to connect to a vncserver that's running on runlevel 3 or does X have to be running for the vnc to work?
I'm new to Linux. I'm trying to install the VNCserver using SSH connection in a remote pc with Fedora 13. I would like to access the Gnome through remote connection. I did the setup Iptables freeing ports 5901 and 5902. Also set up vncserver and user. The user "aquiles" is a user of the system and also the vncserver. The problem is that I am not able to start the service. I think that seen anything related to Perl. Displays the following error:
[Root @ sinahome ~] # service vncserver start Starting VNC server: 1: aquiles/usr/bin/env: perl: No such file or directory [FAILED] The file /etc/sysconfig/vncservers Vncservers = "1: aquiles' VNCSERVERARGS [1] = "-geometry 800x600-depth 16"
[root@sinahome ~] # iptables - list Chain INPUT (policy ACCEPT) target prot opt source destination ACCEPT tcp - anywhere anywhere tcp dpt: ftp ACCEPT tcp - anywhere anywhere tcp dpt: vnc-server ACCEPT tcp - anywhere anywhere tcp dpt: https ACCEPT tcp - anywhere anywhere tcp dpt: http ACCEPT tcp - anywhere anywhere tcp dpt: ssh ACCEPT all - anywhere anywhere state RELATED, Estaba LISHED ACCEPT icmp - anywhere anywhere ACCEPT all - anywhere anywhere ACCEPT tcp - anywhere anywhere state NEW tcp dpt: s sh REJECT all - anywhere anywhere reject-with icmp-ho st-Prohibited ACCEPT all - anywhere anywhere state RELATED, Estaba LISHED ACCEPT tcp - anywhere anywhere tcp PTPs: commplex-m ain: targus-getdata ACCEPT tcp - anywhere anywhere state NEW tcp PTPs: 5901:5902