How can Ubuntu 18.04 be configured to use X instead of Wayland?
This is a new post to an existing problem My original forum post.
I didn't get any answers to the original post but I've now made some important discoveries that I think will help pinpoint what the problem is here.
To recap, the original issue is with an external monitor not being detected on a new install of Ubuntu (18.04) on a W530 Thinkpad with NVIDIA Quadro K1000M card installed. Various NVIDIA drivers have been installed and tried, none of which solved the problem.
I've now summarised my findings as follows.
- When external monitor is attached, the login screen appears on the monitor and the laptop screen is blank.
- The default setting for login is Ubuntu on Wayland. Switching this to Ubuntu on default, then entering password simply causes the same login screen to reappear.
- Leaving the setting as Ubuntu on Wayland, and typing password on the monitor screen results in the desktop then appearing on the laptop screen and the monitor to go blank.
- Modifying etc/gdm3/custom.conf and uncommenting the line
WaylandEnable=false
appears to make no difference to the behaviour just described. - Running ps -ef | grep X shows /usr/bin/Xwayland process running, but no X server processes (as I was used to seeing them).
- Dropping out of the desktop and back into command mode (by typing Ctl-Alt-PF1) and logging in as non-root user, I then type sudo startx and the desktop appears on the external monitor – the laptop screen goes blank.
- The desktop session is now running with the root user logged in.
- Issuing command ps -ef | grep X shows 2 X server processes now running,
1 - xinit and
2 – usr/lib/xorg/Xorg
- Also, the NVIDIA X Server Settings application now appears ‘fully populated’ as shown in the attached image NVIDIA X Server Settings under root.
Contrast this with the same app running under the normal desktop session NVIDIA X Server Settings when X not running . - Furthermore, I can successfully launch applications that require hardware/graphics acceleration from this session.
So far, I’ve reached the following conclusions
- Wayland is enabled, not X
- If Wayland is not enabled (i.e. Ubuntu set to default on login screen), login is unsuccessful
- The NVIDIA card and/or drivers are NOT playing nicely wth Wayland, BUT do play nicely with X when it is enabled
So, does anyone know how I can fix this awful mess so that I can get on and use my Ubuntu 18.04 to do some real work? I really don't care about the merits of Wayland vs. X...I just want to get my computer back up and running like it was before I upgraded - at a minimum, that means
- Being able to use an external monitor, not possible in my current environment.
- Being able to use applications (like Sketchup under vmware) that require the accelerated hardware capability, currently missing in my default environment.
Thanks for any help.
nvidia graphics xorg multiple-monitors
New contributor
add a comment |
This is a new post to an existing problem My original forum post.
I didn't get any answers to the original post but I've now made some important discoveries that I think will help pinpoint what the problem is here.
To recap, the original issue is with an external monitor not being detected on a new install of Ubuntu (18.04) on a W530 Thinkpad with NVIDIA Quadro K1000M card installed. Various NVIDIA drivers have been installed and tried, none of which solved the problem.
I've now summarised my findings as follows.
- When external monitor is attached, the login screen appears on the monitor and the laptop screen is blank.
- The default setting for login is Ubuntu on Wayland. Switching this to Ubuntu on default, then entering password simply causes the same login screen to reappear.
- Leaving the setting as Ubuntu on Wayland, and typing password on the monitor screen results in the desktop then appearing on the laptop screen and the monitor to go blank.
- Modifying etc/gdm3/custom.conf and uncommenting the line
WaylandEnable=false
appears to make no difference to the behaviour just described. - Running ps -ef | grep X shows /usr/bin/Xwayland process running, but no X server processes (as I was used to seeing them).
- Dropping out of the desktop and back into command mode (by typing Ctl-Alt-PF1) and logging in as non-root user, I then type sudo startx and the desktop appears on the external monitor – the laptop screen goes blank.
- The desktop session is now running with the root user logged in.
- Issuing command ps -ef | grep X shows 2 X server processes now running,
1 - xinit and
2 – usr/lib/xorg/Xorg
- Also, the NVIDIA X Server Settings application now appears ‘fully populated’ as shown in the attached image NVIDIA X Server Settings under root.
Contrast this with the same app running under the normal desktop session NVIDIA X Server Settings when X not running . - Furthermore, I can successfully launch applications that require hardware/graphics acceleration from this session.
So far, I’ve reached the following conclusions
- Wayland is enabled, not X
- If Wayland is not enabled (i.e. Ubuntu set to default on login screen), login is unsuccessful
- The NVIDIA card and/or drivers are NOT playing nicely wth Wayland, BUT do play nicely with X when it is enabled
So, does anyone know how I can fix this awful mess so that I can get on and use my Ubuntu 18.04 to do some real work? I really don't care about the merits of Wayland vs. X...I just want to get my computer back up and running like it was before I upgraded - at a minimum, that means
- Being able to use an external monitor, not possible in my current environment.
- Being able to use applications (like Sketchup under vmware) that require the accelerated hardware capability, currently missing in my default environment.
Thanks for any help.
nvidia graphics xorg multiple-monitors
New contributor
add a comment |
This is a new post to an existing problem My original forum post.
I didn't get any answers to the original post but I've now made some important discoveries that I think will help pinpoint what the problem is here.
To recap, the original issue is with an external monitor not being detected on a new install of Ubuntu (18.04) on a W530 Thinkpad with NVIDIA Quadro K1000M card installed. Various NVIDIA drivers have been installed and tried, none of which solved the problem.
I've now summarised my findings as follows.
- When external monitor is attached, the login screen appears on the monitor and the laptop screen is blank.
- The default setting for login is Ubuntu on Wayland. Switching this to Ubuntu on default, then entering password simply causes the same login screen to reappear.
- Leaving the setting as Ubuntu on Wayland, and typing password on the monitor screen results in the desktop then appearing on the laptop screen and the monitor to go blank.
- Modifying etc/gdm3/custom.conf and uncommenting the line
WaylandEnable=false
appears to make no difference to the behaviour just described. - Running ps -ef | grep X shows /usr/bin/Xwayland process running, but no X server processes (as I was used to seeing them).
- Dropping out of the desktop and back into command mode (by typing Ctl-Alt-PF1) and logging in as non-root user, I then type sudo startx and the desktop appears on the external monitor – the laptop screen goes blank.
- The desktop session is now running with the root user logged in.
- Issuing command ps -ef | grep X shows 2 X server processes now running,
1 - xinit and
2 – usr/lib/xorg/Xorg
- Also, the NVIDIA X Server Settings application now appears ‘fully populated’ as shown in the attached image NVIDIA X Server Settings under root.
Contrast this with the same app running under the normal desktop session NVIDIA X Server Settings when X not running . - Furthermore, I can successfully launch applications that require hardware/graphics acceleration from this session.
So far, I’ve reached the following conclusions
- Wayland is enabled, not X
- If Wayland is not enabled (i.e. Ubuntu set to default on login screen), login is unsuccessful
- The NVIDIA card and/or drivers are NOT playing nicely wth Wayland, BUT do play nicely with X when it is enabled
So, does anyone know how I can fix this awful mess so that I can get on and use my Ubuntu 18.04 to do some real work? I really don't care about the merits of Wayland vs. X...I just want to get my computer back up and running like it was before I upgraded - at a minimum, that means
- Being able to use an external monitor, not possible in my current environment.
- Being able to use applications (like Sketchup under vmware) that require the accelerated hardware capability, currently missing in my default environment.
Thanks for any help.
nvidia graphics xorg multiple-monitors
New contributor
This is a new post to an existing problem My original forum post.
I didn't get any answers to the original post but I've now made some important discoveries that I think will help pinpoint what the problem is here.
To recap, the original issue is with an external monitor not being detected on a new install of Ubuntu (18.04) on a W530 Thinkpad with NVIDIA Quadro K1000M card installed. Various NVIDIA drivers have been installed and tried, none of which solved the problem.
I've now summarised my findings as follows.
- When external monitor is attached, the login screen appears on the monitor and the laptop screen is blank.
- The default setting for login is Ubuntu on Wayland. Switching this to Ubuntu on default, then entering password simply causes the same login screen to reappear.
- Leaving the setting as Ubuntu on Wayland, and typing password on the monitor screen results in the desktop then appearing on the laptop screen and the monitor to go blank.
- Modifying etc/gdm3/custom.conf and uncommenting the line
WaylandEnable=false
appears to make no difference to the behaviour just described. - Running ps -ef | grep X shows /usr/bin/Xwayland process running, but no X server processes (as I was used to seeing them).
- Dropping out of the desktop and back into command mode (by typing Ctl-Alt-PF1) and logging in as non-root user, I then type sudo startx and the desktop appears on the external monitor – the laptop screen goes blank.
- The desktop session is now running with the root user logged in.
- Issuing command ps -ef | grep X shows 2 X server processes now running,
1 - xinit and
2 – usr/lib/xorg/Xorg
- Also, the NVIDIA X Server Settings application now appears ‘fully populated’ as shown in the attached image NVIDIA X Server Settings under root.
Contrast this with the same app running under the normal desktop session NVIDIA X Server Settings when X not running . - Furthermore, I can successfully launch applications that require hardware/graphics acceleration from this session.
So far, I’ve reached the following conclusions
- Wayland is enabled, not X
- If Wayland is not enabled (i.e. Ubuntu set to default on login screen), login is unsuccessful
- The NVIDIA card and/or drivers are NOT playing nicely wth Wayland, BUT do play nicely with X when it is enabled
So, does anyone know how I can fix this awful mess so that I can get on and use my Ubuntu 18.04 to do some real work? I really don't care about the merits of Wayland vs. X...I just want to get my computer back up and running like it was before I upgraded - at a minimum, that means
- Being able to use an external monitor, not possible in my current environment.
- Being able to use applications (like Sketchup under vmware) that require the accelerated hardware capability, currently missing in my default environment.
Thanks for any help.
nvidia graphics xorg multiple-monitors
nvidia graphics xorg multiple-monitors
New contributor
New contributor
New contributor
asked 5 mins ago
NomadAUNomadAU
12
12
New contributor
New contributor
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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
});
}
});
NomadAU is a new contributor. Be nice, and check out our Code of Conduct.
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%2faskubuntu.com%2fquestions%2f1118889%2fhow-can-ubuntu-18-04-be-configured-to-use-x-instead-of-wayland%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
NomadAU is a new contributor. Be nice, and check out our Code of Conduct.
NomadAU is a new contributor. Be nice, and check out our Code of Conduct.
NomadAU is a new contributor. Be nice, and check out our Code of Conduct.
NomadAU is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f1118889%2fhow-can-ubuntu-18-04-be-configured-to-use-x-instead-of-wayland%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