After upgrade from 16.04 LTS to 18.04 LTS, display manager fails apparently because of freedesktop
I recently took the hint and upgraded from 16.04 LTS to 18.04 LTS, but had a nasty surprise when no login screen appeared, and even ctrl-alt F2 and friends didn't work. Fortunately, I was able to ssh in from elsewhere.
Welcome to Ubuntu 18.04.1 LTS (GNU/Linux 4.15.0-33-generic x86_64)
Looking at syslog, I saw that gdm3/wayland tried repeatedly to start org.freedesktop.systemd1 and it would immediately fail (exit 1). A message like this would be repeated over and over in syslog.
Aug 30 09:13:38 pabst /usr/lib/gdm3/gdm-wayland-session[1442]: dbus-daemon[1444]: [session uid=127 pid=1444] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=127 pid=1442 comm="/usr/lib/gdm3/gdm-wayland-session gnome-session --" label="unconfined")
Aug 30 09:13:38 pabst /usr/lib/gdm3/gdm-wayland-session[1442]: dbus-daemon[1444]: [session uid=127 pid=1444] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Aug 30 09:13:38 pabst /usr/lib/gdm3/gdm-wayland-session[1442]: Unable to register display with display manager
Aug 30 09:13:38 pabst gdm3: Child process -1442 was already dead.
Aug 30 09:13:38 pabst gdm3: Child process 1439 was already dead.
Aug 30 09:13:38 pabst gdm3: Unable to kill session worker process
Seeing advice elsewhere, I tried using "ubuntu-drivers autoinstall" which installed the recommended nvidia-driver-390.
That didn't help.
I also tried disabling Wayland in a configuration file,
but also no good.
I purged the Nvidia driver and tried with nouveau. Still no dice.
Then I installed nvidia-340 which at least sets the
screen resolution correctly (as seen using "xinit" which
brings up an xterm without a display manager).
Then I installed xdm, and made "xdm" the default greeter
(it was part of the configuration when xdm was installed).
Now a login screen appears (and ctrl-alt F2 and friends work)
but if I try to log on, it waits a bit after the login and then
bumps back to the login screen.
.xsession-errors shows no serious problems.
But syslog shows that gnome-session-binary is trying to start org.freedesktop.systemd1 which (of course) fails again, which makes the required Gnome Shell.desktop die which causes the whole shebang fail (after lots of futile tries).
The sad ending to the story:
Aug 30 11:40:12 pabst dbus-daemon[3966]: [session uid=820 pid=3964] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Aug 30 11:40:12 pabst gnome-keyring-secrets.desktop[4042]: GNOME_KEYRING_CONTROL=/home/john/.cache/keyring-DFQHOZ
Aug 30 11:40:12 pabst gnome-keyring-secrets.desktop[4042]: SSH_AUTH_SOCK=/home/john/.cache/keyring-DFQHOZ/ssh
Aug 30 11:40:12 pabst org.gnome.Shell.desktop[4057]: Window manager warning: Unsupported session type
Aug 30 11:40:12 pabst gnome-session[3926]: gnome-session-binary[3926]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Aug 30 11:40:12 pabst gnome-session-binary[3926]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Aug 30 11:40:13 pabst org.gnome.Shell.desktop[4060]: Window manager warning: Unsupported session type
Aug 30 11:40:13 pabst gnome-session[3926]: gnome-session-binary[3926]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Aug 30 11:40:13 pabst gnome-session[3926]: gnome-session-binary[3926]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
Aug 30 11:40:13 pabst gnome-session[3926]: gnome-session-binary[3926]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Aug 30 11:40:13 pabst gnome-session-binary[3926]: Unrecoverable failure in required component org.gnome.Shell.desktop
Aug 30 11:40:13 pabst gnome-session-binary[3926]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Aug 30 11:40:13 pabst gnome-session-binary[3926]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
Aug 30 11:40:13 pabst gnome-session-binary[3926]: CRITICAL: We failed, but the fail whale is dead. Sorry....
So:
(1) Can org.freedesktop.systemd1 be fixed? Is there any way to see why it's failing? or if it's unfixable
(2) Is there a way to have gnome use something other than org.freedesktop.systemd1 ? or
(3) Is there a display manager I can use on Ubuntu bionic that doesn't use any gnome stuff?
nvidia gnome 18.04
add a comment |
I recently took the hint and upgraded from 16.04 LTS to 18.04 LTS, but had a nasty surprise when no login screen appeared, and even ctrl-alt F2 and friends didn't work. Fortunately, I was able to ssh in from elsewhere.
Welcome to Ubuntu 18.04.1 LTS (GNU/Linux 4.15.0-33-generic x86_64)
Looking at syslog, I saw that gdm3/wayland tried repeatedly to start org.freedesktop.systemd1 and it would immediately fail (exit 1). A message like this would be repeated over and over in syslog.
Aug 30 09:13:38 pabst /usr/lib/gdm3/gdm-wayland-session[1442]: dbus-daemon[1444]: [session uid=127 pid=1444] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=127 pid=1442 comm="/usr/lib/gdm3/gdm-wayland-session gnome-session --" label="unconfined")
Aug 30 09:13:38 pabst /usr/lib/gdm3/gdm-wayland-session[1442]: dbus-daemon[1444]: [session uid=127 pid=1444] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Aug 30 09:13:38 pabst /usr/lib/gdm3/gdm-wayland-session[1442]: Unable to register display with display manager
Aug 30 09:13:38 pabst gdm3: Child process -1442 was already dead.
Aug 30 09:13:38 pabst gdm3: Child process 1439 was already dead.
Aug 30 09:13:38 pabst gdm3: Unable to kill session worker process
Seeing advice elsewhere, I tried using "ubuntu-drivers autoinstall" which installed the recommended nvidia-driver-390.
That didn't help.
I also tried disabling Wayland in a configuration file,
but also no good.
I purged the Nvidia driver and tried with nouveau. Still no dice.
Then I installed nvidia-340 which at least sets the
screen resolution correctly (as seen using "xinit" which
brings up an xterm without a display manager).
Then I installed xdm, and made "xdm" the default greeter
(it was part of the configuration when xdm was installed).
Now a login screen appears (and ctrl-alt F2 and friends work)
but if I try to log on, it waits a bit after the login and then
bumps back to the login screen.
.xsession-errors shows no serious problems.
But syslog shows that gnome-session-binary is trying to start org.freedesktop.systemd1 which (of course) fails again, which makes the required Gnome Shell.desktop die which causes the whole shebang fail (after lots of futile tries).
The sad ending to the story:
Aug 30 11:40:12 pabst dbus-daemon[3966]: [session uid=820 pid=3964] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Aug 30 11:40:12 pabst gnome-keyring-secrets.desktop[4042]: GNOME_KEYRING_CONTROL=/home/john/.cache/keyring-DFQHOZ
Aug 30 11:40:12 pabst gnome-keyring-secrets.desktop[4042]: SSH_AUTH_SOCK=/home/john/.cache/keyring-DFQHOZ/ssh
Aug 30 11:40:12 pabst org.gnome.Shell.desktop[4057]: Window manager warning: Unsupported session type
Aug 30 11:40:12 pabst gnome-session[3926]: gnome-session-binary[3926]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Aug 30 11:40:12 pabst gnome-session-binary[3926]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Aug 30 11:40:13 pabst org.gnome.Shell.desktop[4060]: Window manager warning: Unsupported session type
Aug 30 11:40:13 pabst gnome-session[3926]: gnome-session-binary[3926]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Aug 30 11:40:13 pabst gnome-session[3926]: gnome-session-binary[3926]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
Aug 30 11:40:13 pabst gnome-session[3926]: gnome-session-binary[3926]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Aug 30 11:40:13 pabst gnome-session-binary[3926]: Unrecoverable failure in required component org.gnome.Shell.desktop
Aug 30 11:40:13 pabst gnome-session-binary[3926]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Aug 30 11:40:13 pabst gnome-session-binary[3926]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
Aug 30 11:40:13 pabst gnome-session-binary[3926]: CRITICAL: We failed, but the fail whale is dead. Sorry....
So:
(1) Can org.freedesktop.systemd1 be fixed? Is there any way to see why it's failing? or if it's unfixable
(2) Is there a way to have gnome use something other than org.freedesktop.systemd1 ? or
(3) Is there a display manager I can use on Ubuntu bionic that doesn't use any gnome stuff?
nvidia gnome 18.04
1
I faced the same issue upgrading from 16.04 to 18.04. ctrl-alt F2 worked for me but goes full black screen after some 10 to 15 second and pressing again ctrl-alt F2 I tried many solution. One of them tried removing gdm3 and then reinstalling it worked for me. But not in a strait path.
– M.A.K. Ripon
Sep 11 '18 at 9:50
add a comment |
I recently took the hint and upgraded from 16.04 LTS to 18.04 LTS, but had a nasty surprise when no login screen appeared, and even ctrl-alt F2 and friends didn't work. Fortunately, I was able to ssh in from elsewhere.
Welcome to Ubuntu 18.04.1 LTS (GNU/Linux 4.15.0-33-generic x86_64)
Looking at syslog, I saw that gdm3/wayland tried repeatedly to start org.freedesktop.systemd1 and it would immediately fail (exit 1). A message like this would be repeated over and over in syslog.
Aug 30 09:13:38 pabst /usr/lib/gdm3/gdm-wayland-session[1442]: dbus-daemon[1444]: [session uid=127 pid=1444] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=127 pid=1442 comm="/usr/lib/gdm3/gdm-wayland-session gnome-session --" label="unconfined")
Aug 30 09:13:38 pabst /usr/lib/gdm3/gdm-wayland-session[1442]: dbus-daemon[1444]: [session uid=127 pid=1444] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Aug 30 09:13:38 pabst /usr/lib/gdm3/gdm-wayland-session[1442]: Unable to register display with display manager
Aug 30 09:13:38 pabst gdm3: Child process -1442 was already dead.
Aug 30 09:13:38 pabst gdm3: Child process 1439 was already dead.
Aug 30 09:13:38 pabst gdm3: Unable to kill session worker process
Seeing advice elsewhere, I tried using "ubuntu-drivers autoinstall" which installed the recommended nvidia-driver-390.
That didn't help.
I also tried disabling Wayland in a configuration file,
but also no good.
I purged the Nvidia driver and tried with nouveau. Still no dice.
Then I installed nvidia-340 which at least sets the
screen resolution correctly (as seen using "xinit" which
brings up an xterm without a display manager).
Then I installed xdm, and made "xdm" the default greeter
(it was part of the configuration when xdm was installed).
Now a login screen appears (and ctrl-alt F2 and friends work)
but if I try to log on, it waits a bit after the login and then
bumps back to the login screen.
.xsession-errors shows no serious problems.
But syslog shows that gnome-session-binary is trying to start org.freedesktop.systemd1 which (of course) fails again, which makes the required Gnome Shell.desktop die which causes the whole shebang fail (after lots of futile tries).
The sad ending to the story:
Aug 30 11:40:12 pabst dbus-daemon[3966]: [session uid=820 pid=3964] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Aug 30 11:40:12 pabst gnome-keyring-secrets.desktop[4042]: GNOME_KEYRING_CONTROL=/home/john/.cache/keyring-DFQHOZ
Aug 30 11:40:12 pabst gnome-keyring-secrets.desktop[4042]: SSH_AUTH_SOCK=/home/john/.cache/keyring-DFQHOZ/ssh
Aug 30 11:40:12 pabst org.gnome.Shell.desktop[4057]: Window manager warning: Unsupported session type
Aug 30 11:40:12 pabst gnome-session[3926]: gnome-session-binary[3926]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Aug 30 11:40:12 pabst gnome-session-binary[3926]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Aug 30 11:40:13 pabst org.gnome.Shell.desktop[4060]: Window manager warning: Unsupported session type
Aug 30 11:40:13 pabst gnome-session[3926]: gnome-session-binary[3926]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Aug 30 11:40:13 pabst gnome-session[3926]: gnome-session-binary[3926]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
Aug 30 11:40:13 pabst gnome-session[3926]: gnome-session-binary[3926]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Aug 30 11:40:13 pabst gnome-session-binary[3926]: Unrecoverable failure in required component org.gnome.Shell.desktop
Aug 30 11:40:13 pabst gnome-session-binary[3926]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Aug 30 11:40:13 pabst gnome-session-binary[3926]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
Aug 30 11:40:13 pabst gnome-session-binary[3926]: CRITICAL: We failed, but the fail whale is dead. Sorry....
So:
(1) Can org.freedesktop.systemd1 be fixed? Is there any way to see why it's failing? or if it's unfixable
(2) Is there a way to have gnome use something other than org.freedesktop.systemd1 ? or
(3) Is there a display manager I can use on Ubuntu bionic that doesn't use any gnome stuff?
nvidia gnome 18.04
I recently took the hint and upgraded from 16.04 LTS to 18.04 LTS, but had a nasty surprise when no login screen appeared, and even ctrl-alt F2 and friends didn't work. Fortunately, I was able to ssh in from elsewhere.
Welcome to Ubuntu 18.04.1 LTS (GNU/Linux 4.15.0-33-generic x86_64)
Looking at syslog, I saw that gdm3/wayland tried repeatedly to start org.freedesktop.systemd1 and it would immediately fail (exit 1). A message like this would be repeated over and over in syslog.
Aug 30 09:13:38 pabst /usr/lib/gdm3/gdm-wayland-session[1442]: dbus-daemon[1444]: [session uid=127 pid=1444] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=127 pid=1442 comm="/usr/lib/gdm3/gdm-wayland-session gnome-session --" label="unconfined")
Aug 30 09:13:38 pabst /usr/lib/gdm3/gdm-wayland-session[1442]: dbus-daemon[1444]: [session uid=127 pid=1444] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Aug 30 09:13:38 pabst /usr/lib/gdm3/gdm-wayland-session[1442]: Unable to register display with display manager
Aug 30 09:13:38 pabst gdm3: Child process -1442 was already dead.
Aug 30 09:13:38 pabst gdm3: Child process 1439 was already dead.
Aug 30 09:13:38 pabst gdm3: Unable to kill session worker process
Seeing advice elsewhere, I tried using "ubuntu-drivers autoinstall" which installed the recommended nvidia-driver-390.
That didn't help.
I also tried disabling Wayland in a configuration file,
but also no good.
I purged the Nvidia driver and tried with nouveau. Still no dice.
Then I installed nvidia-340 which at least sets the
screen resolution correctly (as seen using "xinit" which
brings up an xterm without a display manager).
Then I installed xdm, and made "xdm" the default greeter
(it was part of the configuration when xdm was installed).
Now a login screen appears (and ctrl-alt F2 and friends work)
but if I try to log on, it waits a bit after the login and then
bumps back to the login screen.
.xsession-errors shows no serious problems.
But syslog shows that gnome-session-binary is trying to start org.freedesktop.systemd1 which (of course) fails again, which makes the required Gnome Shell.desktop die which causes the whole shebang fail (after lots of futile tries).
The sad ending to the story:
Aug 30 11:40:12 pabst dbus-daemon[3966]: [session uid=820 pid=3964] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Aug 30 11:40:12 pabst gnome-keyring-secrets.desktop[4042]: GNOME_KEYRING_CONTROL=/home/john/.cache/keyring-DFQHOZ
Aug 30 11:40:12 pabst gnome-keyring-secrets.desktop[4042]: SSH_AUTH_SOCK=/home/john/.cache/keyring-DFQHOZ/ssh
Aug 30 11:40:12 pabst org.gnome.Shell.desktop[4057]: Window manager warning: Unsupported session type
Aug 30 11:40:12 pabst gnome-session[3926]: gnome-session-binary[3926]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Aug 30 11:40:12 pabst gnome-session-binary[3926]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Aug 30 11:40:13 pabst org.gnome.Shell.desktop[4060]: Window manager warning: Unsupported session type
Aug 30 11:40:13 pabst gnome-session[3926]: gnome-session-binary[3926]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Aug 30 11:40:13 pabst gnome-session[3926]: gnome-session-binary[3926]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
Aug 30 11:40:13 pabst gnome-session[3926]: gnome-session-binary[3926]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Aug 30 11:40:13 pabst gnome-session-binary[3926]: Unrecoverable failure in required component org.gnome.Shell.desktop
Aug 30 11:40:13 pabst gnome-session-binary[3926]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Aug 30 11:40:13 pabst gnome-session-binary[3926]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
Aug 30 11:40:13 pabst gnome-session-binary[3926]: CRITICAL: We failed, but the fail whale is dead. Sorry....
So:
(1) Can org.freedesktop.systemd1 be fixed? Is there any way to see why it's failing? or if it's unfixable
(2) Is there a way to have gnome use something other than org.freedesktop.systemd1 ? or
(3) Is there a display manager I can use on Ubuntu bionic that doesn't use any gnome stuff?
nvidia gnome 18.04
nvidia gnome 18.04
edited Sep 12 '18 at 1:14
John Tang Boyland
asked Aug 30 '18 at 16:49
John Tang BoylandJohn Tang Boyland
965
965
1
I faced the same issue upgrading from 16.04 to 18.04. ctrl-alt F2 worked for me but goes full black screen after some 10 to 15 second and pressing again ctrl-alt F2 I tried many solution. One of them tried removing gdm3 and then reinstalling it worked for me. But not in a strait path.
– M.A.K. Ripon
Sep 11 '18 at 9:50
add a comment |
1
I faced the same issue upgrading from 16.04 to 18.04. ctrl-alt F2 worked for me but goes full black screen after some 10 to 15 second and pressing again ctrl-alt F2 I tried many solution. One of them tried removing gdm3 and then reinstalling it worked for me. But not in a strait path.
– M.A.K. Ripon
Sep 11 '18 at 9:50
1
1
I faced the same issue upgrading from 16.04 to 18.04. ctrl-alt F2 worked for me but goes full black screen after some 10 to 15 second and pressing again ctrl-alt F2 I tried many solution. One of them tried removing gdm3 and then reinstalling it worked for me. But not in a strait path.
– M.A.K. Ripon
Sep 11 '18 at 9:50
I faced the same issue upgrading from 16.04 to 18.04. ctrl-alt F2 worked for me but goes full black screen after some 10 to 15 second and pressing again ctrl-alt F2 I tried many solution. One of them tried removing gdm3 and then reinstalling it worked for me. But not in a strait path.
– M.A.K. Ripon
Sep 11 '18 at 9:50
add a comment |
2 Answers
2
active
oldest
votes
I think you need to select Xorg from Xwayland, see this bug
Edit your /etc/gdm3/custom.conf
file and add :
WaylandEnable=false
another user issue had fixed after install haveged
, may you can try :
sudo apt install haveged
and also you need make sure had plymouth
package.
sudo apt install plymouth
and also you might make sure your kernel fixed, see this bug
Hope this helps.
1
I tried everything: edited /etc/gdm3/custom.conf, installed haveged and plymouth and updated to the latest kernel (for 18.04.01: 4.15.0-34-generic), but no improvement. org.freedesktop.systemd1 still fails. None of the links you point to mention this tool. Thanks for trying! Ubuntu 18.04 has been a disaster.
– John Tang Boyland
Sep 10 '18 at 21:07
I cannot see how to repair manually, i think only reinstall your OS sir.
– abu-ahmed al-khatiri
Sep 11 '18 at 9:46
add a comment |
I had a similar issue, do not know if this is exactly the way to fix this but it worked. I added this line to /etc/pam.d/gdm-launch-environment (adding to /etc/pam.d/common-session worked as well):
session optional pam_systemd.so
I do not know if it should have been there in 16.04, or if something with the 16.04 to 18.04 upgrade was skipped.
It was this error in syslog that finally lead me to this fix:
(EE) systemd-logind: failed to get session: PID 10023 does not belong to any known session
As a result of that, gdm-x-session failed and aborted, and the gdm3 service just kept trying over and over again, flooding my syslog.
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%2f1070572%2fafter-upgrade-from-16-04-lts-to-18-04-lts-display-manager-fails-apparently-beca%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
I think you need to select Xorg from Xwayland, see this bug
Edit your /etc/gdm3/custom.conf
file and add :
WaylandEnable=false
another user issue had fixed after install haveged
, may you can try :
sudo apt install haveged
and also you need make sure had plymouth
package.
sudo apt install plymouth
and also you might make sure your kernel fixed, see this bug
Hope this helps.
1
I tried everything: edited /etc/gdm3/custom.conf, installed haveged and plymouth and updated to the latest kernel (for 18.04.01: 4.15.0-34-generic), but no improvement. org.freedesktop.systemd1 still fails. None of the links you point to mention this tool. Thanks for trying! Ubuntu 18.04 has been a disaster.
– John Tang Boyland
Sep 10 '18 at 21:07
I cannot see how to repair manually, i think only reinstall your OS sir.
– abu-ahmed al-khatiri
Sep 11 '18 at 9:46
add a comment |
I think you need to select Xorg from Xwayland, see this bug
Edit your /etc/gdm3/custom.conf
file and add :
WaylandEnable=false
another user issue had fixed after install haveged
, may you can try :
sudo apt install haveged
and also you need make sure had plymouth
package.
sudo apt install plymouth
and also you might make sure your kernel fixed, see this bug
Hope this helps.
1
I tried everything: edited /etc/gdm3/custom.conf, installed haveged and plymouth and updated to the latest kernel (for 18.04.01: 4.15.0-34-generic), but no improvement. org.freedesktop.systemd1 still fails. None of the links you point to mention this tool. Thanks for trying! Ubuntu 18.04 has been a disaster.
– John Tang Boyland
Sep 10 '18 at 21:07
I cannot see how to repair manually, i think only reinstall your OS sir.
– abu-ahmed al-khatiri
Sep 11 '18 at 9:46
add a comment |
I think you need to select Xorg from Xwayland, see this bug
Edit your /etc/gdm3/custom.conf
file and add :
WaylandEnable=false
another user issue had fixed after install haveged
, may you can try :
sudo apt install haveged
and also you need make sure had plymouth
package.
sudo apt install plymouth
and also you might make sure your kernel fixed, see this bug
Hope this helps.
I think you need to select Xorg from Xwayland, see this bug
Edit your /etc/gdm3/custom.conf
file and add :
WaylandEnable=false
another user issue had fixed after install haveged
, may you can try :
sudo apt install haveged
and also you need make sure had plymouth
package.
sudo apt install plymouth
and also you might make sure your kernel fixed, see this bug
Hope this helps.
answered Sep 10 '18 at 15:12
abu-ahmed al-khatiriabu-ahmed al-khatiri
1,014116
1,014116
1
I tried everything: edited /etc/gdm3/custom.conf, installed haveged and plymouth and updated to the latest kernel (for 18.04.01: 4.15.0-34-generic), but no improvement. org.freedesktop.systemd1 still fails. None of the links you point to mention this tool. Thanks for trying! Ubuntu 18.04 has been a disaster.
– John Tang Boyland
Sep 10 '18 at 21:07
I cannot see how to repair manually, i think only reinstall your OS sir.
– abu-ahmed al-khatiri
Sep 11 '18 at 9:46
add a comment |
1
I tried everything: edited /etc/gdm3/custom.conf, installed haveged and plymouth and updated to the latest kernel (for 18.04.01: 4.15.0-34-generic), but no improvement. org.freedesktop.systemd1 still fails. None of the links you point to mention this tool. Thanks for trying! Ubuntu 18.04 has been a disaster.
– John Tang Boyland
Sep 10 '18 at 21:07
I cannot see how to repair manually, i think only reinstall your OS sir.
– abu-ahmed al-khatiri
Sep 11 '18 at 9:46
1
1
I tried everything: edited /etc/gdm3/custom.conf, installed haveged and plymouth and updated to the latest kernel (for 18.04.01: 4.15.0-34-generic), but no improvement. org.freedesktop.systemd1 still fails. None of the links you point to mention this tool. Thanks for trying! Ubuntu 18.04 has been a disaster.
– John Tang Boyland
Sep 10 '18 at 21:07
I tried everything: edited /etc/gdm3/custom.conf, installed haveged and plymouth and updated to the latest kernel (for 18.04.01: 4.15.0-34-generic), but no improvement. org.freedesktop.systemd1 still fails. None of the links you point to mention this tool. Thanks for trying! Ubuntu 18.04 has been a disaster.
– John Tang Boyland
Sep 10 '18 at 21:07
I cannot see how to repair manually, i think only reinstall your OS sir.
– abu-ahmed al-khatiri
Sep 11 '18 at 9:46
I cannot see how to repair manually, i think only reinstall your OS sir.
– abu-ahmed al-khatiri
Sep 11 '18 at 9:46
add a comment |
I had a similar issue, do not know if this is exactly the way to fix this but it worked. I added this line to /etc/pam.d/gdm-launch-environment (adding to /etc/pam.d/common-session worked as well):
session optional pam_systemd.so
I do not know if it should have been there in 16.04, or if something with the 16.04 to 18.04 upgrade was skipped.
It was this error in syslog that finally lead me to this fix:
(EE) systemd-logind: failed to get session: PID 10023 does not belong to any known session
As a result of that, gdm-x-session failed and aborted, and the gdm3 service just kept trying over and over again, flooding my syslog.
add a comment |
I had a similar issue, do not know if this is exactly the way to fix this but it worked. I added this line to /etc/pam.d/gdm-launch-environment (adding to /etc/pam.d/common-session worked as well):
session optional pam_systemd.so
I do not know if it should have been there in 16.04, or if something with the 16.04 to 18.04 upgrade was skipped.
It was this error in syslog that finally lead me to this fix:
(EE) systemd-logind: failed to get session: PID 10023 does not belong to any known session
As a result of that, gdm-x-session failed and aborted, and the gdm3 service just kept trying over and over again, flooding my syslog.
add a comment |
I had a similar issue, do not know if this is exactly the way to fix this but it worked. I added this line to /etc/pam.d/gdm-launch-environment (adding to /etc/pam.d/common-session worked as well):
session optional pam_systemd.so
I do not know if it should have been there in 16.04, or if something with the 16.04 to 18.04 upgrade was skipped.
It was this error in syslog that finally lead me to this fix:
(EE) systemd-logind: failed to get session: PID 10023 does not belong to any known session
As a result of that, gdm-x-session failed and aborted, and the gdm3 service just kept trying over and over again, flooding my syslog.
I had a similar issue, do not know if this is exactly the way to fix this but it worked. I added this line to /etc/pam.d/gdm-launch-environment (adding to /etc/pam.d/common-session worked as well):
session optional pam_systemd.so
I do not know if it should have been there in 16.04, or if something with the 16.04 to 18.04 upgrade was skipped.
It was this error in syslog that finally lead me to this fix:
(EE) systemd-logind: failed to get session: PID 10023 does not belong to any known session
As a result of that, gdm-x-session failed and aborted, and the gdm3 service just kept trying over and over again, flooding my syslog.
answered 1 hour ago
IntegratorIntegrator
1714
1714
add a comment |
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%2f1070572%2fafter-upgrade-from-16-04-lts-to-18-04-lts-display-manager-fails-apparently-beca%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
1
I faced the same issue upgrading from 16.04 to 18.04. ctrl-alt F2 worked for me but goes full black screen after some 10 to 15 second and pressing again ctrl-alt F2 I tried many solution. One of them tried removing gdm3 and then reinstalling it worked for me. But not in a strait path.
– M.A.K. Ripon
Sep 11 '18 at 9:50