Gnome session broken on Ubuntu 17.10
My dell inspiron 660s with intel graphics ran Ubuntu 16.04.3 for a year with no issues, and I decided to give 17.10 a try.
After installing 17.10, ubuntu restricted extras, lowlatency kernel, and applying all updates and rebooting, GDM fails to start.
Here are some relevant log entries:
Oct 21 14:27:24 olympia gnome-session[2984]: gnome-session-check-accelerated: GL Helper exited with code 256
Oct 21 14:27:24 olympia gnome-session-c[3030]: eglGetDisplay() failed
Oct 21 14:27:24 olympia gnome-session[2984]: gnome-session-check-accelerated: GLES Helper exited with code 256
Oct 21 14:27:24 olympia gnome-session[2984]: gnome-session-binary[2984]: WARNING: software acceleration check failed: Child process exited with code 1
Oct 21 14:27:24 olympia gnome-session[2984]: gnome-session-binary[2984]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Oct 21 14:27:24 olympia gnome-session-binary[2984]: WARNING: software acceleration check failed: Child process exited with code 1
Oct 21 14:27:24 olympia gnome-session-binary[2984]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Oct 21 14:27:24 olympia org.a11y.atspi.Registry[3002]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
Oct 21 14:27:24 olympia org.a11y.atspi.Registry[3002]: after 21 requests (21 known processed) with 0 events remaining.
gdm 17.10 wayland gnome-session
edited Oct 21 '17 at 21:42
ravery
5,48351132
asked Oct 21 '17 at 21:36
user207065user207065
1612
bumped to the homepage by Community♦ 2 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
My dell inspiron 660s with intel graphics ran Ubuntu 16.04.3 for a year with no issues, and I decided to give 17.10 a try.
After installing 17.10, ubuntu restricted extras, lowlatency kernel, and applying all updates and rebooting, GDM fails to start.
Here are some relevant log entries:
Oct 21 14:27:24 olympia gnome-session[2984]: gnome-session-check-accelerated: GL Helper exited with code 256
Oct 21 14:27:24 olympia gnome-session-c[3030]: eglGetDisplay() failed
Oct 21 14:27:24 olympia gnome-session[2984]: gnome-session-check-accelerated: GLES Helper exited with code 256
Oct 21 14:27:24 olympia gnome-session[2984]: gnome-session-binary[2984]: WARNING: software acceleration check failed: Child process exited with code 1
Oct 21 14:27:24 olympia gnome-session[2984]: gnome-session-binary[2984]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Oct 21 14:27:24 olympia gnome-session-binary[2984]: WARNING: software acceleration check failed: Child process exited with code 1
Oct 21 14:27:24 olympia gnome-session-binary[2984]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Oct 21 14:27:24 olympia org.a11y.atspi.Registry[3002]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
Oct 21 14:27:24 olympia org.a11y.atspi.Registry[3002]: after 21 requests (21 known processed) with 0 events remaining.
gdm 17.10 wayland gnome-session
edited Oct 21 '17 at 21:42
ravery
5,48351132
asked Oct 21 '17 at 21:36
user207065user207065
1612
bumped to the homepage by Community♦ 2 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
My dell inspiron 660s with intel graphics ran Ubuntu 16.04.3 for a year with no issues, and I decided to give 17.10 a try.
After installing 17.10, ubuntu restricted extras, lowlatency kernel, and applying all updates and rebooting, GDM fails to start.
Here are some relevant log entries:
Oct 21 14:27:24 olympia gnome-session[2984]: gnome-session-check-accelerated: GL Helper exited with code 256
Oct 21 14:27:24 olympia gnome-session-c[3030]: eglGetDisplay() failed
Oct 21 14:27:24 olympia gnome-session[2984]: gnome-session-check-accelerated: GLES Helper exited with code 256
Oct 21 14:27:24 olympia gnome-session[2984]: gnome-session-binary[2984]: WARNING: software acceleration check failed: Child process exited with code 1
Oct 21 14:27:24 olympia gnome-session[2984]: gnome-session-binary[2984]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Oct 21 14:27:24 olympia gnome-session-binary[2984]: WARNING: software acceleration check failed: Child process exited with code 1
Oct 21 14:27:24 olympia gnome-session-binary[2984]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Oct 21 14:27:24 olympia org.a11y.atspi.Registry[3002]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
Oct 21 14:27:24 olympia org.a11y.atspi.Registry[3002]: after 21 requests (21 known processed) with 0 events remaining.
gdm 17.10 wayland gnome-session
edited Oct 21 '17 at 21:42
ravery
5,48351132
asked Oct 21 '17 at 21:36
user207065user207065
1612
My dell inspiron 660s with intel graphics ran Ubuntu 16.04.3 for a year with no issues, and I decided to give 17.10 a try.
After installing 17.10, ubuntu restricted extras, lowlatency kernel, and applying all updates and rebooting, GDM fails to start.
Here are some relevant log entries:
Oct 21 14:27:24 olympia gnome-session[2984]: gnome-session-check-accelerated: GL Helper exited with code 256
Oct 21 14:27:24 olympia gnome-session-c[3030]: eglGetDisplay() failed
Oct 21 14:27:24 olympia gnome-session[2984]: gnome-session-check-accelerated: GLES Helper exited with code 256
Oct 21 14:27:24 olympia gnome-session[2984]: gnome-session-binary[2984]: WARNING: software acceleration check failed: Child process exited with code 1
Oct 21 14:27:24 olympia gnome-session[2984]: gnome-session-binary[2984]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Oct 21 14:27:24 olympia gnome-session-binary[2984]: WARNING: software acceleration check failed: Child process exited with code 1
Oct 21 14:27:24 olympia gnome-session-binary[2984]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Oct 21 14:27:24 olympia org.a11y.atspi.Registry[3002]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
Oct 21 14:27:24 olympia org.a11y.atspi.Registry[3002]: after 21 requests (21 known processed) with 0 events remaining.
gdm 17.10 wayland gnome-session
gdm 17.10 wayland gnome-session
edited Oct 21 '17 at 21:42
ravery
5,48351132
asked Oct 21 '17 at 21:36
user207065user207065
1612
edited Oct 21 '17 at 21:42
ravery
5,48351132
asked Oct 21 '17 at 21:36
user207065user207065
1612
edited Oct 21 '17 at 21:42
ravery
5,48351132
edited Oct 21 '17 at 21:42
ravery
5,48351132
edited Oct 21 '17 at 21:42
ravery
5,48351132
5,48351132
asked Oct 21 '17 at 21:36
user207065user207065
1612
asked Oct 21 '17 at 21:36
user207065user207065
1612
asked Oct 21 '17 at 21:36
user207065user207065
1612
1612
bumped to the homepage by Community♦ 2 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 2 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I had, what seemed to be, the same problem. In my case the headers didn't get installed during the upgrade and thus the video driver never got built.
Here's what I did:
- installed
linux-headers-lowlatency
- ran
sudo dpkg-reconfigure nvidia-384
- make sure wayland was enabled in
/etc/gdm3/custom.conf(I had changed it before)
I may have uninstalled nouveau (xserver-xorg-video-nouveau package) but I think it was getting the driver module built/installed and re-enabling wayland (after I disabled it trying to get things working) that did the trick for me.
FYI, for me everything feels sluggish, and it doesn't take refresh-rate changes.. but that's a problem for another day.
answered Oct 22 '17 at 16:00
Nathan CazaNathan Caza
1
Thanks, I've seen this problem with headers and nvidia driver happen on my other desktop which has an nvidia card. But the machine in question above is just straight onboard intel video, so you'd think nothing could go wrong....
– user207065
Oct 22 '17 at 16:40
Oh wow, I completely missed the "intel graphics" part of your post, my bad. ><
– Nathan Caza
Oct 22 '17 at 21:54
The problems with 17.10 were not resolved. I decided to go ahead and install the daily build of 18.04, which, as it turns out, works, even at this early stage. I won't pursue the 17.10 issues any longer
– user207065
Nov 10 '17 at 23:04
add a comment |
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
});
}
});
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%2f967374%2fgnome-session-broken-on-ubuntu-17-10%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
I had, what seemed to be, the same problem. In my case the headers didn't get installed during the upgrade and thus the video driver never got built.
Here's what I did:
- installed
linux-headers-lowlatency
- ran
sudo dpkg-reconfigure nvidia-384
- make sure wayland was enabled in
/etc/gdm3/custom.conf(I had changed it before)
I may have uninstalled nouveau (xserver-xorg-video-nouveau package) but I think it was getting the driver module built/installed and re-enabling wayland (after I disabled it trying to get things working) that did the trick for me.
FYI, for me everything feels sluggish, and it doesn't take refresh-rate changes.. but that's a problem for another day.
answered Oct 22 '17 at 16:00
Nathan CazaNathan Caza
1
Thanks, I've seen this problem with headers and nvidia driver happen on my other desktop which has an nvidia card. But the machine in question above is just straight onboard intel video, so you'd think nothing could go wrong....
– user207065
Oct 22 '17 at 16:40
Oh wow, I completely missed the "intel graphics" part of your post, my bad. ><
– Nathan Caza
Oct 22 '17 at 21:54
The problems with 17.10 were not resolved. I decided to go ahead and install the daily build of 18.04, which, as it turns out, works, even at this early stage. I won't pursue the 17.10 issues any longer
– user207065
Nov 10 '17 at 23:04
add a comment |
I had, what seemed to be, the same problem. In my case the headers didn't get installed during the upgrade and thus the video driver never got built.
Here's what I did:
- installed
linux-headers-lowlatency
- ran
sudo dpkg-reconfigure nvidia-384
- make sure wayland was enabled in
/etc/gdm3/custom.conf(I had changed it before)
I may have uninstalled nouveau (xserver-xorg-video-nouveau package) but I think it was getting the driver module built/installed and re-enabling wayland (after I disabled it trying to get things working) that did the trick for me.
FYI, for me everything feels sluggish, and it doesn't take refresh-rate changes.. but that's a problem for another day.
answered Oct 22 '17 at 16:00
Nathan CazaNathan Caza
1
Thanks, I've seen this problem with headers and nvidia driver happen on my other desktop which has an nvidia card. But the machine in question above is just straight onboard intel video, so you'd think nothing could go wrong....
– user207065
Oct 22 '17 at 16:40
Oh wow, I completely missed the "intel graphics" part of your post, my bad. ><
– Nathan Caza
Oct 22 '17 at 21:54
The problems with 17.10 were not resolved. I decided to go ahead and install the daily build of 18.04, which, as it turns out, works, even at this early stage. I won't pursue the 17.10 issues any longer
– user207065
Nov 10 '17 at 23:04
add a comment |
I had, what seemed to be, the same problem. In my case the headers didn't get installed during the upgrade and thus the video driver never got built.
Here's what I did:
- installed
linux-headers-lowlatency
- ran
sudo dpkg-reconfigure nvidia-384
- make sure wayland was enabled in
/etc/gdm3/custom.conf(I had changed it before)
I may have uninstalled nouveau (xserver-xorg-video-nouveau package) but I think it was getting the driver module built/installed and re-enabling wayland (after I disabled it trying to get things working) that did the trick for me.
FYI, for me everything feels sluggish, and it doesn't take refresh-rate changes.. but that's a problem for another day.
answered Oct 22 '17 at 16:00
Nathan CazaNathan Caza
1
I had, what seemed to be, the same problem. In my case the headers didn't get installed during the upgrade and thus the video driver never got built.
Here's what I did:
- installed
linux-headers-lowlatency
- ran
sudo dpkg-reconfigure nvidia-384
- make sure wayland was enabled in
/etc/gdm3/custom.conf(I had changed it before)
I may have uninstalled nouveau (xserver-xorg-video-nouveau package) but I think it was getting the driver module built/installed and re-enabling wayland (after I disabled it trying to get things working) that did the trick for me.
FYI, for me everything feels sluggish, and it doesn't take refresh-rate changes.. but that's a problem for another day.
answered Oct 22 '17 at 16:00
Nathan CazaNathan Caza
1
answered Oct 22 '17 at 16:00
Nathan CazaNathan Caza
1
answered Oct 22 '17 at 16:00
Nathan CazaNathan Caza
1
answered Oct 22 '17 at 16:00
Nathan CazaNathan Caza
1
1
Thanks, I've seen this problem with headers and nvidia driver happen on my other desktop which has an nvidia card. But the machine in question above is just straight onboard intel video, so you'd think nothing could go wrong....
– user207065
Oct 22 '17 at 16:40
Oh wow, I completely missed the "intel graphics" part of your post, my bad. ><
– Nathan Caza
Oct 22 '17 at 21:54
The problems with 17.10 were not resolved. I decided to go ahead and install the daily build of 18.04, which, as it turns out, works, even at this early stage. I won't pursue the 17.10 issues any longer
– user207065
Nov 10 '17 at 23:04
add a comment |
Thanks, I've seen this problem with headers and nvidia driver happen on my other desktop which has an nvidia card. But the machine in question above is just straight onboard intel video, so you'd think nothing could go wrong....
– user207065
Oct 22 '17 at 16:40
Oh wow, I completely missed the "intel graphics" part of your post, my bad. ><
– Nathan Caza
Oct 22 '17 at 21:54
The problems with 17.10 were not resolved. I decided to go ahead and install the daily build of 18.04, which, as it turns out, works, even at this early stage. I won't pursue the 17.10 issues any longer
– user207065
Nov 10 '17 at 23:04
Thanks, I've seen this problem with headers and nvidia driver happen on my other desktop which has an nvidia card. But the machine in question above is just straight onboard intel video, so you'd think nothing could go wrong....
– user207065
Oct 22 '17 at 16:40
Thanks, I've seen this problem with headers and nvidia driver happen on my other desktop which has an nvidia card. But the machine in question above is just straight onboard intel video, so you'd think nothing could go wrong....
– user207065
Oct 22 '17 at 16:40
Oh wow, I completely missed the "intel graphics" part of your post, my bad. ><
– Nathan Caza
Oct 22 '17 at 21:54
Oh wow, I completely missed the "intel graphics" part of your post, my bad. ><
– Nathan Caza
Oct 22 '17 at 21:54
The problems with 17.10 were not resolved. I decided to go ahead and install the daily build of 18.04, which, as it turns out, works, even at this early stage. I won't pursue the 17.10 issues any longer
– user207065
Nov 10 '17 at 23:04
The problems with 17.10 were not resolved. I decided to go ahead and install the daily build of 18.04, which, as it turns out, works, even at this early stage. I won't pursue the 17.10 issues any longer
– user207065
Nov 10 '17 at 23:04
add a comment |
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%2f967374%2fgnome-session-broken-on-ubuntu-17-10%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
