tigervnc on centos - black screen
I am running tigervnc-server on CentOS 6.8, however the gnome desktop won't start for me! I have done a yum groupinstall of "X Window System", "Desktop" and "General Purpose Desktop". On one of my other CentOS VMs (v6.6), installing these packages is sufficient for having the gnome-desktop automatically startup for me when starting a vncserver.
I'm running:
vncserver :05 -geometry 2048x1024
In /home/user/.vnc/hostname:05.log, I see:
vncconfig: unable to open display "hostname:05"
xrdb: Connection refused
xrdb: Can't open display 'hostname:05'
xmodmap: unable to open display 'hostname:05'
** (gnome-session:12313):WARNING **: Cannot open display
The VNC server starts, and I'm able to connect via vncviewer, but get a black screen.
Is there anything else I can look at to troubleshoot? The log isn't very helpful; I've been googling this problem for days, and haven't found anything that fixes it (Ex: made sure I'm in runlevel 5, I re-installed the desktop packages mentioned above, removed .vnc directory, stepped through xstartup, tried comparing various settings with my other VM where the gnome desktop is working)
Anyone know of something else I can look at to troubleshoot this issue? Any other logs, or things to check?
centos gnome vnc
asked Oct 18 '16 at 12:00
user1160958
111
add a comment |
I am running tigervnc-server on CentOS 6.8, however the gnome desktop won't start for me! I have done a yum groupinstall of "X Window System", "Desktop" and "General Purpose Desktop". On one of my other CentOS VMs (v6.6), installing these packages is sufficient for having the gnome-desktop automatically startup for me when starting a vncserver.
I'm running:
vncserver :05 -geometry 2048x1024
In /home/user/.vnc/hostname:05.log, I see:
vncconfig: unable to open display "hostname:05"
xrdb: Connection refused
xrdb: Can't open display 'hostname:05'
xmodmap: unable to open display 'hostname:05'
** (gnome-session:12313):WARNING **: Cannot open display
The VNC server starts, and I'm able to connect via vncviewer, but get a black screen.
Is there anything else I can look at to troubleshoot? The log isn't very helpful; I've been googling this problem for days, and haven't found anything that fixes it (Ex: made sure I'm in runlevel 5, I re-installed the desktop packages mentioned above, removed .vnc directory, stepped through xstartup, tried comparing various settings with my other VM where the gnome desktop is working)
Anyone know of something else I can look at to troubleshoot this issue? Any other logs, or things to check?
centos gnome vnc
asked Oct 18 '16 at 12:00
user1160958
111
Update; it doesn't appear that the X server is being started with VNC. I attempted to run Xvnc manually, and the vncserver starts find (i see the Xnvc process listening on 5905). But I do not see Xvnc listening on port 6005, which is where the X server would be listening. No error messages are being displayed.
– user1160958
Oct 18 '16 at 19:52
To follow up, I think I figured out the issue. It appears to be a problem specific to tigervnc v1.1.0-18. On my VM where VNC and X are working, I was running tigervnc v1.1.0-16. When I upgraded to tigervnc v1.1.0-18, this issue appeared for me where the X server doesn't start with VNC. For now, my solution will be to revert back to tigervnc-1.1.0-16. Not sure if I should make this accepted solution or not...
– user1160958
Oct 19 '16 at 12:57
add a comment |
I am running tigervnc-server on CentOS 6.8, however the gnome desktop won't start for me! I have done a yum groupinstall of "X Window System", "Desktop" and "General Purpose Desktop". On one of my other CentOS VMs (v6.6), installing these packages is sufficient for having the gnome-desktop automatically startup for me when starting a vncserver.
I'm running:
vncserver :05 -geometry 2048x1024
In /home/user/.vnc/hostname:05.log, I see:
vncconfig: unable to open display "hostname:05"
xrdb: Connection refused
xrdb: Can't open display 'hostname:05'
xmodmap: unable to open display 'hostname:05'
** (gnome-session:12313):WARNING **: Cannot open display
The VNC server starts, and I'm able to connect via vncviewer, but get a black screen.
Is there anything else I can look at to troubleshoot? The log isn't very helpful; I've been googling this problem for days, and haven't found anything that fixes it (Ex: made sure I'm in runlevel 5, I re-installed the desktop packages mentioned above, removed .vnc directory, stepped through xstartup, tried comparing various settings with my other VM where the gnome desktop is working)
Anyone know of something else I can look at to troubleshoot this issue? Any other logs, or things to check?
centos gnome vnc
asked Oct 18 '16 at 12:00
user1160958
111
I am running tigervnc-server on CentOS 6.8, however the gnome desktop won't start for me! I have done a yum groupinstall of "X Window System", "Desktop" and "General Purpose Desktop". On one of my other CentOS VMs (v6.6), installing these packages is sufficient for having the gnome-desktop automatically startup for me when starting a vncserver.
I'm running:
vncserver :05 -geometry 2048x1024
In /home/user/.vnc/hostname:05.log, I see:
vncconfig: unable to open display "hostname:05"
xrdb: Connection refused
xrdb: Can't open display 'hostname:05'
xmodmap: unable to open display 'hostname:05'
** (gnome-session:12313):WARNING **: Cannot open display
The VNC server starts, and I'm able to connect via vncviewer, but get a black screen.
Is there anything else I can look at to troubleshoot? The log isn't very helpful; I've been googling this problem for days, and haven't found anything that fixes it (Ex: made sure I'm in runlevel 5, I re-installed the desktop packages mentioned above, removed .vnc directory, stepped through xstartup, tried comparing various settings with my other VM where the gnome desktop is working)
Anyone know of something else I can look at to troubleshoot this issue? Any other logs, or things to check?
centos gnome vnc
centos gnome vnc
asked Oct 18 '16 at 12:00
user1160958
111
asked Oct 18 '16 at 12:00
user1160958
111
asked Oct 18 '16 at 12:00
user1160958
111
asked Oct 18 '16 at 12:00
user1160958
111
asked Oct 18 '16 at 12:00
user1160958
111
111
Update; it doesn't appear that the X server is being started with VNC. I attempted to run Xvnc manually, and the vncserver starts find (i see the Xnvc process listening on 5905). But I do not see Xvnc listening on port 6005, which is where the X server would be listening. No error messages are being displayed.
– user1160958
Oct 18 '16 at 19:52
To follow up, I think I figured out the issue. It appears to be a problem specific to tigervnc v1.1.0-18. On my VM where VNC and X are working, I was running tigervnc v1.1.0-16. When I upgraded to tigervnc v1.1.0-18, this issue appeared for me where the X server doesn't start with VNC. For now, my solution will be to revert back to tigervnc-1.1.0-16. Not sure if I should make this accepted solution or not...
– user1160958
Oct 19 '16 at 12:57
add a comment |
Update; it doesn't appear that the X server is being started with VNC. I attempted to run Xvnc manually, and the vncserver starts find (i see the Xnvc process listening on 5905). But I do not see Xvnc listening on port 6005, which is where the X server would be listening. No error messages are being displayed.
– user1160958
Oct 18 '16 at 19:52
To follow up, I think I figured out the issue. It appears to be a problem specific to tigervnc v1.1.0-18. On my VM where VNC and X are working, I was running tigervnc v1.1.0-16. When I upgraded to tigervnc v1.1.0-18, this issue appeared for me where the X server doesn't start with VNC. For now, my solution will be to revert back to tigervnc-1.1.0-16. Not sure if I should make this accepted solution or not...
– user1160958
Oct 19 '16 at 12:57
Update; it doesn't appear that the X server is being started with VNC. I attempted to run Xvnc manually, and the vncserver starts find (i see the Xnvc process listening on 5905). But I do not see Xvnc listening on port 6005, which is where the X server would be listening. No error messages are being displayed.
– user1160958
Oct 18 '16 at 19:52
Update; it doesn't appear that the X server is being started with VNC. I attempted to run Xvnc manually, and the vncserver starts find (i see the Xnvc process listening on 5905). But I do not see Xvnc listening on port 6005, which is where the X server would be listening. No error messages are being displayed.
– user1160958
Oct 18 '16 at 19:52
To follow up, I think I figured out the issue. It appears to be a problem specific to tigervnc v1.1.0-18. On my VM where VNC and X are working, I was running tigervnc v1.1.0-16. When I upgraded to tigervnc v1.1.0-18, this issue appeared for me where the X server doesn't start with VNC. For now, my solution will be to revert back to tigervnc-1.1.0-16. Not sure if I should make this accepted solution or not...
– user1160958
Oct 19 '16 at 12:57
To follow up, I think I figured out the issue. It appears to be a problem specific to tigervnc v1.1.0-18. On my VM where VNC and X are working, I was running tigervnc v1.1.0-16. When I upgraded to tigervnc v1.1.0-18, this issue appeared for me where the X server doesn't start with VNC. For now, my solution will be to revert back to tigervnc-1.1.0-16. Not sure if I should make this accepted solution or not...
– user1160958
Oct 19 '16 at 12:57
add a comment |
1 Answer
1
active
oldest
votes
On FreeBSD, you have to edit ~/.vnc/xstartup and specify the Desktop environment.
In my case I had to replace twm by startxfce4 .
answered Oct 11 at 11:04
brunobhr
167
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f317179%2ftigervnc-on-centos-black-screen%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
On FreeBSD, you have to edit ~/.vnc/xstartup and specify the Desktop environment.
In my case I had to replace twm by startxfce4 .
answered Oct 11 at 11:04
brunobhr
167
add a comment |
On FreeBSD, you have to edit ~/.vnc/xstartup and specify the Desktop environment.
In my case I had to replace twm by startxfce4 .
answered Oct 11 at 11:04
brunobhr
167
add a comment |
On FreeBSD, you have to edit ~/.vnc/xstartup and specify the Desktop environment.
In my case I had to replace twm by startxfce4 .
answered Oct 11 at 11:04
brunobhr
167
On FreeBSD, you have to edit ~/.vnc/xstartup and specify the Desktop environment.
In my case I had to replace twm by startxfce4 .
answered Oct 11 at 11:04
brunobhr
167
answered Oct 11 at 11:04
brunobhr
167
answered Oct 11 at 11:04
brunobhr
167
answered Oct 11 at 11:04
brunobhr
167
167
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f317179%2ftigervnc-on-centos-black-screen%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Update; it doesn't appear that the X server is being started with VNC. I attempted to run Xvnc manually, and the vncserver starts find (i see the Xnvc process listening on 5905). But I do not see Xvnc listening on port 6005, which is where the X server would be listening. No error messages are being displayed.
– user1160958
Oct 18 '16 at 19:52
To follow up, I think I figured out the issue. It appears to be a problem specific to tigervnc v1.1.0-18. On my VM where VNC and X are working, I was running tigervnc v1.1.0-16. When I upgraded to tigervnc v1.1.0-18, this issue appeared for me where the X server doesn't start with VNC. For now, my solution will be to revert back to tigervnc-1.1.0-16. Not sure if I should make this accepted solution or not...
– user1160958
Oct 19 '16 at 12:57