After upgrading Kubuntu from 16.04 to 18.04 get black screen on login
After upgrading Kubuntu from 16.04 to 18.04 the system seemed to work ok except for problems with multiple monitors.
But after a reboot X started crashing on start up (that's another problem). I removed the Nvidia card, and now I can get to the login screen. But after logging in the screen goes blank with just the mouse cursor visible.
I can Shift+Alt+F2 to switch to a tty. I've tried xrandr
from there but can't connect to the X display.
Any suggestions?
18.04 xorg
add a comment |
After upgrading Kubuntu from 16.04 to 18.04 the system seemed to work ok except for problems with multiple monitors.
But after a reboot X started crashing on start up (that's another problem). I removed the Nvidia card, and now I can get to the login screen. But after logging in the screen goes blank with just the mouse cursor visible.
I can Shift+Alt+F2 to switch to a tty. I've tried xrandr
from there but can't connect to the X display.
Any suggestions?
18.04 xorg
I managed to stop gdm from a tty and tried starting out using startx, where I got a window containing "Could not sync environment to dbus." and OK button. On clicking Ok the X session terminates. In ~/.X's I see "dbus-update-activation-environment: error: unable to connect to D-Bus: Failed to connect to socket /run/user/1000/bus: Connection refused"
– hughworm
Aug 16 '18 at 13:52
add a comment |
After upgrading Kubuntu from 16.04 to 18.04 the system seemed to work ok except for problems with multiple monitors.
But after a reboot X started crashing on start up (that's another problem). I removed the Nvidia card, and now I can get to the login screen. But after logging in the screen goes blank with just the mouse cursor visible.
I can Shift+Alt+F2 to switch to a tty. I've tried xrandr
from there but can't connect to the X display.
Any suggestions?
18.04 xorg
After upgrading Kubuntu from 16.04 to 18.04 the system seemed to work ok except for problems with multiple monitors.
But after a reboot X started crashing on start up (that's another problem). I removed the Nvidia card, and now I can get to the login screen. But after logging in the screen goes blank with just the mouse cursor visible.
I can Shift+Alt+F2 to switch to a tty. I've tried xrandr
from there but can't connect to the X display.
Any suggestions?
18.04 xorg
18.04 xorg
edited Aug 16 '18 at 14:12
damadam
1,008219
1,008219
asked Aug 16 '18 at 12:16
hughwormhughworm
11
11
I managed to stop gdm from a tty and tried starting out using startx, where I got a window containing "Could not sync environment to dbus." and OK button. On clicking Ok the X session terminates. In ~/.X's I see "dbus-update-activation-environment: error: unable to connect to D-Bus: Failed to connect to socket /run/user/1000/bus: Connection refused"
– hughworm
Aug 16 '18 at 13:52
add a comment |
I managed to stop gdm from a tty and tried starting out using startx, where I got a window containing "Could not sync environment to dbus." and OK button. On clicking Ok the X session terminates. In ~/.X's I see "dbus-update-activation-environment: error: unable to connect to D-Bus: Failed to connect to socket /run/user/1000/bus: Connection refused"
– hughworm
Aug 16 '18 at 13:52
I managed to stop gdm from a tty and tried starting out using startx, where I got a window containing "Could not sync environment to dbus." and OK button. On clicking Ok the X session terminates. In ~/.X's I see "dbus-update-activation-environment: error: unable to connect to D-Bus: Failed to connect to socket /run/user/1000/bus: Connection refused"
– hughworm
Aug 16 '18 at 13:52
I managed to stop gdm from a tty and tried starting out using startx, where I got a window containing "Could not sync environment to dbus." and OK button. On clicking Ok the X session terminates. In ~/.X's I see "dbus-update-activation-environment: error: unable to connect to D-Bus: Failed to connect to socket /run/user/1000/bus: Connection refused"
– hughworm
Aug 16 '18 at 13:52
add a comment |
2 Answers
2
active
oldest
votes
The answer seemed to be to remove and purge the nvidia drivers.
However I now have the nvidia card working after following advice in
this post
Unfortunately I'm still limited the one graphics card with DVI and VGA, whereas in 16.04 I was successfully running 3 monitors via two cards.
add a comment |
I had similar issues where the upgrade from 16.04 to 18.04 resulted in blank screen.
The key to finding the problems was reviewing the errors in the file /var/log/syslog
gnome-session[2851]: X Error of failed request: BadValue (integer parameter out of range for operation)
gnome-session[2851]: Major opcode of failed request: 154 (GLX)
gnome-session[2851]: Minor opcode of failed request: 3 (X_GLXCreateContext)
gnome-session[2851]: Value in failed request: 0x0
gnome-session[2851]: Serial number of failed request: 19
gnome-session[2851]: Current serial number in output stream: 20
gnome-session[2851]: gnome-session-check-accelerated: GL Helper exited with code 256
gnome-session-c[2979]: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-4UdC671MtT: Connection refused
gnome-session-c[2979]: eglGetDisplay() failed
gnome-session[2851]: gnome-session-check-accelerated: GLES Helper exited with code 256
gnome-session-c[2980]: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-4UdC671MtT: Connection refused
gnome-session[2851]: X Error of failed request: BadValue (integer parameter out of range for operation)
gnome-session[2851]: Major opcode of failed request: 154 (GLX)
gnome-session[2851]: Minor opcode of failed request: 3 (X_GLXCreateContext)
gnome-session[2851]: Value in failed request: 0x0
gnome-session[2851]: Serial number of failed request: 19
gnome-session[2851]: Current serial number in output stream: 20
gnome-session[2851]: gnome-session-check-accelerated: GL Helper exited with code 256
The solution was found in the outline in the link below, to remove the nvidia drivers.
I was surprised this was the solution as my system ran on intel integrated gpu. However its hard to know how things precipitate till they do.
https://www.osso.nl/blog/ubuntu-bionic-crashing-gdm-eglgetdisplay/
First I changed the display manager to lightdm.
$ sudo apt-get install lightdm
$ sudo dpkg-reconfigure lightdm
to select lightdm as the default desktop manager
Then the login screen came up. However , I entered the famous ubuntu login loop , where upon successful login to the system resulted into the same greeter screen again instead of navigating into the desktop.
$ dpkg -l | grep nvidia
$ sudo apt-get remove --purge nvidia-***
Voila, the system starts again as before.
I also had issues with the gnome themes, which cause the menus and window title bars to disappear. I had to install the gnome "tweaks" program to select the right theme and things were back.
New contributor
It looks wrong to permanently switch back to lightdm.
– Pilot6
6 hours ago
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%2f1065883%2fafter-upgrading-kubuntu-from-16-04-to-18-04-get-black-screen-on-login%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
The answer seemed to be to remove and purge the nvidia drivers.
However I now have the nvidia card working after following advice in
this post
Unfortunately I'm still limited the one graphics card with DVI and VGA, whereas in 16.04 I was successfully running 3 monitors via two cards.
add a comment |
The answer seemed to be to remove and purge the nvidia drivers.
However I now have the nvidia card working after following advice in
this post
Unfortunately I'm still limited the one graphics card with DVI and VGA, whereas in 16.04 I was successfully running 3 monitors via two cards.
add a comment |
The answer seemed to be to remove and purge the nvidia drivers.
However I now have the nvidia card working after following advice in
this post
Unfortunately I'm still limited the one graphics card with DVI and VGA, whereas in 16.04 I was successfully running 3 monitors via two cards.
The answer seemed to be to remove and purge the nvidia drivers.
However I now have the nvidia card working after following advice in
this post
Unfortunately I'm still limited the one graphics card with DVI and VGA, whereas in 16.04 I was successfully running 3 monitors via two cards.
answered Aug 16 '18 at 18:04
hughwormhughworm
11
11
add a comment |
add a comment |
I had similar issues where the upgrade from 16.04 to 18.04 resulted in blank screen.
The key to finding the problems was reviewing the errors in the file /var/log/syslog
gnome-session[2851]: X Error of failed request: BadValue (integer parameter out of range for operation)
gnome-session[2851]: Major opcode of failed request: 154 (GLX)
gnome-session[2851]: Minor opcode of failed request: 3 (X_GLXCreateContext)
gnome-session[2851]: Value in failed request: 0x0
gnome-session[2851]: Serial number of failed request: 19
gnome-session[2851]: Current serial number in output stream: 20
gnome-session[2851]: gnome-session-check-accelerated: GL Helper exited with code 256
gnome-session-c[2979]: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-4UdC671MtT: Connection refused
gnome-session-c[2979]: eglGetDisplay() failed
gnome-session[2851]: gnome-session-check-accelerated: GLES Helper exited with code 256
gnome-session-c[2980]: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-4UdC671MtT: Connection refused
gnome-session[2851]: X Error of failed request: BadValue (integer parameter out of range for operation)
gnome-session[2851]: Major opcode of failed request: 154 (GLX)
gnome-session[2851]: Minor opcode of failed request: 3 (X_GLXCreateContext)
gnome-session[2851]: Value in failed request: 0x0
gnome-session[2851]: Serial number of failed request: 19
gnome-session[2851]: Current serial number in output stream: 20
gnome-session[2851]: gnome-session-check-accelerated: GL Helper exited with code 256
The solution was found in the outline in the link below, to remove the nvidia drivers.
I was surprised this was the solution as my system ran on intel integrated gpu. However its hard to know how things precipitate till they do.
https://www.osso.nl/blog/ubuntu-bionic-crashing-gdm-eglgetdisplay/
First I changed the display manager to lightdm.
$ sudo apt-get install lightdm
$ sudo dpkg-reconfigure lightdm
to select lightdm as the default desktop manager
Then the login screen came up. However , I entered the famous ubuntu login loop , where upon successful login to the system resulted into the same greeter screen again instead of navigating into the desktop.
$ dpkg -l | grep nvidia
$ sudo apt-get remove --purge nvidia-***
Voila, the system starts again as before.
I also had issues with the gnome themes, which cause the menus and window title bars to disappear. I had to install the gnome "tweaks" program to select the right theme and things were back.
New contributor
It looks wrong to permanently switch back to lightdm.
– Pilot6
6 hours ago
add a comment |
I had similar issues where the upgrade from 16.04 to 18.04 resulted in blank screen.
The key to finding the problems was reviewing the errors in the file /var/log/syslog
gnome-session[2851]: X Error of failed request: BadValue (integer parameter out of range for operation)
gnome-session[2851]: Major opcode of failed request: 154 (GLX)
gnome-session[2851]: Minor opcode of failed request: 3 (X_GLXCreateContext)
gnome-session[2851]: Value in failed request: 0x0
gnome-session[2851]: Serial number of failed request: 19
gnome-session[2851]: Current serial number in output stream: 20
gnome-session[2851]: gnome-session-check-accelerated: GL Helper exited with code 256
gnome-session-c[2979]: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-4UdC671MtT: Connection refused
gnome-session-c[2979]: eglGetDisplay() failed
gnome-session[2851]: gnome-session-check-accelerated: GLES Helper exited with code 256
gnome-session-c[2980]: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-4UdC671MtT: Connection refused
gnome-session[2851]: X Error of failed request: BadValue (integer parameter out of range for operation)
gnome-session[2851]: Major opcode of failed request: 154 (GLX)
gnome-session[2851]: Minor opcode of failed request: 3 (X_GLXCreateContext)
gnome-session[2851]: Value in failed request: 0x0
gnome-session[2851]: Serial number of failed request: 19
gnome-session[2851]: Current serial number in output stream: 20
gnome-session[2851]: gnome-session-check-accelerated: GL Helper exited with code 256
The solution was found in the outline in the link below, to remove the nvidia drivers.
I was surprised this was the solution as my system ran on intel integrated gpu. However its hard to know how things precipitate till they do.
https://www.osso.nl/blog/ubuntu-bionic-crashing-gdm-eglgetdisplay/
First I changed the display manager to lightdm.
$ sudo apt-get install lightdm
$ sudo dpkg-reconfigure lightdm
to select lightdm as the default desktop manager
Then the login screen came up. However , I entered the famous ubuntu login loop , where upon successful login to the system resulted into the same greeter screen again instead of navigating into the desktop.
$ dpkg -l | grep nvidia
$ sudo apt-get remove --purge nvidia-***
Voila, the system starts again as before.
I also had issues with the gnome themes, which cause the menus and window title bars to disappear. I had to install the gnome "tweaks" program to select the right theme and things were back.
New contributor
It looks wrong to permanently switch back to lightdm.
– Pilot6
6 hours ago
add a comment |
I had similar issues where the upgrade from 16.04 to 18.04 resulted in blank screen.
The key to finding the problems was reviewing the errors in the file /var/log/syslog
gnome-session[2851]: X Error of failed request: BadValue (integer parameter out of range for operation)
gnome-session[2851]: Major opcode of failed request: 154 (GLX)
gnome-session[2851]: Minor opcode of failed request: 3 (X_GLXCreateContext)
gnome-session[2851]: Value in failed request: 0x0
gnome-session[2851]: Serial number of failed request: 19
gnome-session[2851]: Current serial number in output stream: 20
gnome-session[2851]: gnome-session-check-accelerated: GL Helper exited with code 256
gnome-session-c[2979]: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-4UdC671MtT: Connection refused
gnome-session-c[2979]: eglGetDisplay() failed
gnome-session[2851]: gnome-session-check-accelerated: GLES Helper exited with code 256
gnome-session-c[2980]: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-4UdC671MtT: Connection refused
gnome-session[2851]: X Error of failed request: BadValue (integer parameter out of range for operation)
gnome-session[2851]: Major opcode of failed request: 154 (GLX)
gnome-session[2851]: Minor opcode of failed request: 3 (X_GLXCreateContext)
gnome-session[2851]: Value in failed request: 0x0
gnome-session[2851]: Serial number of failed request: 19
gnome-session[2851]: Current serial number in output stream: 20
gnome-session[2851]: gnome-session-check-accelerated: GL Helper exited with code 256
The solution was found in the outline in the link below, to remove the nvidia drivers.
I was surprised this was the solution as my system ran on intel integrated gpu. However its hard to know how things precipitate till they do.
https://www.osso.nl/blog/ubuntu-bionic-crashing-gdm-eglgetdisplay/
First I changed the display manager to lightdm.
$ sudo apt-get install lightdm
$ sudo dpkg-reconfigure lightdm
to select lightdm as the default desktop manager
Then the login screen came up. However , I entered the famous ubuntu login loop , where upon successful login to the system resulted into the same greeter screen again instead of navigating into the desktop.
$ dpkg -l | grep nvidia
$ sudo apt-get remove --purge nvidia-***
Voila, the system starts again as before.
I also had issues with the gnome themes, which cause the menus and window title bars to disappear. I had to install the gnome "tweaks" program to select the right theme and things were back.
New contributor
I had similar issues where the upgrade from 16.04 to 18.04 resulted in blank screen.
The key to finding the problems was reviewing the errors in the file /var/log/syslog
gnome-session[2851]: X Error of failed request: BadValue (integer parameter out of range for operation)
gnome-session[2851]: Major opcode of failed request: 154 (GLX)
gnome-session[2851]: Minor opcode of failed request: 3 (X_GLXCreateContext)
gnome-session[2851]: Value in failed request: 0x0
gnome-session[2851]: Serial number of failed request: 19
gnome-session[2851]: Current serial number in output stream: 20
gnome-session[2851]: gnome-session-check-accelerated: GL Helper exited with code 256
gnome-session-c[2979]: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-4UdC671MtT: Connection refused
gnome-session-c[2979]: eglGetDisplay() failed
gnome-session[2851]: gnome-session-check-accelerated: GLES Helper exited with code 256
gnome-session-c[2980]: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-4UdC671MtT: Connection refused
gnome-session[2851]: X Error of failed request: BadValue (integer parameter out of range for operation)
gnome-session[2851]: Major opcode of failed request: 154 (GLX)
gnome-session[2851]: Minor opcode of failed request: 3 (X_GLXCreateContext)
gnome-session[2851]: Value in failed request: 0x0
gnome-session[2851]: Serial number of failed request: 19
gnome-session[2851]: Current serial number in output stream: 20
gnome-session[2851]: gnome-session-check-accelerated: GL Helper exited with code 256
The solution was found in the outline in the link below, to remove the nvidia drivers.
I was surprised this was the solution as my system ran on intel integrated gpu. However its hard to know how things precipitate till they do.
https://www.osso.nl/blog/ubuntu-bionic-crashing-gdm-eglgetdisplay/
First I changed the display manager to lightdm.
$ sudo apt-get install lightdm
$ sudo dpkg-reconfigure lightdm
to select lightdm as the default desktop manager
Then the login screen came up. However , I entered the famous ubuntu login loop , where upon successful login to the system resulted into the same greeter screen again instead of navigating into the desktop.
$ dpkg -l | grep nvidia
$ sudo apt-get remove --purge nvidia-***
Voila, the system starts again as before.
I also had issues with the gnome themes, which cause the menus and window title bars to disappear. I had to install the gnome "tweaks" program to select the right theme and things were back.
New contributor
edited 6 hours ago
MatsK
517214
517214
New contributor
answered 9 hours ago
RupinderRupinder
1
1
New contributor
New contributor
It looks wrong to permanently switch back to lightdm.
– Pilot6
6 hours ago
add a comment |
It looks wrong to permanently switch back to lightdm.
– Pilot6
6 hours ago
It looks wrong to permanently switch back to lightdm.
– Pilot6
6 hours ago
It looks wrong to permanently switch back to lightdm.
– Pilot6
6 hours ago
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%2f1065883%2fafter-upgrading-kubuntu-from-16-04-to-18-04-get-black-screen-on-login%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
I managed to stop gdm from a tty and tried starting out using startx, where I got a window containing "Could not sync environment to dbus." and OK button. On clicking Ok the X session terminates. In ~/.X's I see "dbus-update-activation-environment: error: unable to connect to D-Bus: Failed to connect to socket /run/user/1000/bus: Connection refused"
– hughworm
Aug 16 '18 at 13:52