similar to: Xlib: extension "RANDR" missing on display ":1".

Hello, I''m doing my first steps with Xen and have my first domU up now (Debian/sid under Debian/sid). The main problem I had, was to bring up the graphical desktop of the guest with vnc4server. The solution was simple - but not easy to find for me - so let me share it: Whenever I tried to login on xdm or gdm via xvnc4viewer coming from dom0, I found errors in .xsession-errors of

I get back from two weeks on the road, and try to VNC to my server and it fails. I ssh in and see that, yes vncserver is dead. I tried restarting it and see below for the failure messages plus my systemd setup. Can someone point me to trouble shooting why it says about resources (if that is the problem); # systemctl -l status vncserver@:3.service ? vncserver@:3.service - Remote desktop

Actually it is running: netstat -tuln | grep 590 tcp 0 0 0.0.0.0:5901 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:5902 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:5903 0.0.0.0:* LISTEN tcp6 0 0 :::5901 :::* LISTEN tcp6 0 0 :::5902 :::* LISTEN tcp6 0 0 :::5903 :::* LISTEN

I got vncserver working per: https://www.tecmint.com/install-and-configure-vnc-server-in-centos-7/ Then I went to set up a second instance, and have that for logging on to root: ========== cp /lib/systemd/system/vncserver at .service /etc/systemd/system/vncserver@:2.service vi /etc/systemd/system/vncserver@\:2.service replace <USER> with root systemctl daemon-reload systemctl start

A couple of days ago, I posted a question about using vnc with winbind users (i.e. users from a Win2k3 Active Directory domain being authenticated locally on a Linux box -- in this case Fedora Core 3 -- with winbind). The consensus seemed to be that it wasn't possible, at least with the free versions of VNC. Well, not so. Here's how I did it. First, I found out by accident (i.e. just

OK, first time configuring vncserver on Centos7. I have read through a bunch of old messages here on vncserver and thought I had it. Obviously not. 1) cp /usr/lib/systemd/system/vncserver at .service /etc/systemd/system/vncserver at .service 2) vi /etc/systemd/system/vncserver at .service I changed <USER> in both places to root 3) systemctl daemon-reload 4) systemctl

Hi Jerry, I done a lot of search in google. Than I find your post, but without success for my problem. I have add your xstartup file. But I can't get it working with this startupfile. One problem is, that I can't find the x-terminal-emulator on my machine. Which package must I install for x-terminal-emulator in CentOS7 ? Maybe you can have a look at my logfile and my configuration for

Hi Patrick, Thanks for you quickly answer. Yes, x11vnc was installed on my system. The problem is i not understand the ?logic" of vnc connection, so i try to dark? I copy the /etc/systemd/system/vncserver@:1.service to /etc/systemd/system/vncserver@:0.service restart the vnc service and obtain Jul 18 11:17:16 systemd[1]: vncserver@:0.service: control process exited, code=exited

(Please don't top-post.) Milton Plasencia wrote: > I copy the /etc/systemd/system/vncserver@:1.service to /etc/systemd/system/vncserver@:0.service As I said in my previous post, for what you are wanting to do, vncserver is not the right tool. Use x11vnc instead (and also remove the above copy). > Jul 18 11:17:16 systemd[1]: vncserver@:0.service: control process exited, code=exited

>You should: >cp /lib/systemd/system/vncserver at .service <http://lists.centos.org/mailman/listinfo/centos> /lib/systemd/system/vncserver@:#.service >Where # is the vnc port 590# to open. Like /lib/systemd/system/vncserver@:4.service to start a vncserver on port 5904. > Then use `systemctl start vncserver@:4' to start that VNC server. Remember to edit the

The suggestion from Marco to try a non-3D DE worked. I tried two methods: 1. minimal Centos 7 install and xfce install via CLI. Worked fine. 2. Gnome Centos 7 install and then xfce install via yum groupinstall. Worked fine. One tip for anyone doing this: After starting vncserver the first time, it creates a ~/.vnc/xstartup file. This will be the same type of session if you logged in locally.

HI all, i am configuring VNC server in CentOS 5.1. i have enables this two lines in /etc/sysconfig/vncserver file VNCSERVERS="2:vnc" VNCSERVERARGS[2]="-geometry 1024x768 -depth 24" here i have created a user vnc and set the password using vncpasswd cmd. then i started the vncserver # vncserver New 'localhost.localdomain:1 (gopinath)' desktop is

I tried to use tightvnc back in August and had some help, but I stopped due to IPv6 support. Now I am back at tightvnc and cannot get the server started. This is on a new Centos install that did have regular vncserver working on it (I did a yum erase vnc-server first). So I have a working /etc/sysconfig/vncserver and my user has the appropriate ~/.vnc files that worked with regular vnc.

Hi, I just installed CentOS7 and managed to start the vncserver service, but once I connect to the machine, the desktop resolution isn't the one which I set in the vncserver@:3.service file located in /lib/systemd/system/ directory. The content of the mention file: ---------------------------------------- [Unit] Description=Remote desktop service (VNC) After=syslog.target network.target

Gerald and P.J., I just finished setting up VNC services following http://wiki.centos.org/HowTos/VNC-Server and have a few comments. "2.3. Edit the server configuration" The last line should be corrected from VNCSERVERARGS[1]="-geometry 800x600" to VNCSERVERARGS[3]="-geometry 800x600" "2.4. Create xstartup scripts" Comments about the rational for

I am trying to setup a centos 7.1 vncserver I cannot believe they went from a relatively easy process in 6 to the "crazyness" that is 7. I did the following: yum install tigervnc-server cp /lib/systemd/system/vncserver at .service /etc/systemd/system systemctl daemon-reload edit /etc/systemd.system/vncserver at .service

Hello, I want to run some program with Wine in a headless server. However, I want to access it via VNC, so I am using Xvnc (vncserver is a wrapper script) from tightvnc as a X server. But I have a problem: wine doesn't detect the display of the X server. This is what happens: Code: [martin at urano ~]$ DISPLAY=:1 [martin at urano ~]$ vncserver :1 New 'X' desktop is urano:1 (...)

I still don't like gnome.... Got a user who wants the "whole gnome experience" (i.e., he can't deal w/ the command line), so I'm testing this: I'm running 6.5, KDE. On the server, I've installed both Xnest, "Gnome Desktop Environment", and "X Window System". Xnest works fine, I can start xclock, or an xterm, but if I try DISPLAY=:1, I see the

I've been scratching my head over this one after setting up VNC on another existing server. Followed the instructions here http://wiki.centos.org/HowTos/VNC-Server as usual. It worked initially. However since this server is going to be installed in a rather inconvenient place and having done pretty stupid things before, I decided for the first time to try the portion that says # Add the

Chris, could you have a look at this since it's allegedly your work in the intel driver and let us know if it's reasonable? I'm definitely not enough of an X driver guy to rule one way or the other. On Wed, Mar 29, 2017 at 4:07 PM, Mariusz Bialonczyk <manio at skyboo.net> wrote: > When using Xinerama, RandR is automatically disabled, and calling RR > routines will trigger