18.04 boots ok, but once lock screen appears I can't unlock it
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
Started yesterday; the system is running all the background applications it is supposed to but the only way to use it interactively is to power off completely and restart. The screen, keyboard and mouse then operate fine but if I go away for 10 minutes and the screen sleeps I can't get past the lock screen. Normally the ESC key or a mouse click will prompt for a login, but not any more.
Looking in syslog there is a truckload of gdm-x-session and gnome-shell errors. I don't know if this is relevant but the first of these after reboot is as follows:
dbus-daemon[1086]: [session uid=125 pid=1086] Activating service name='org.gnome.ScreenSaver' requested by ':1:12' (uid=125 pid=1088 comm="/usr/lib/gnome-session/gnome-session-binary --auto" label="unconfined")
org.gnome.ScreenSaver[1086]: Unable to init server: Could not connect: Connection refused
gnome-screensav[1094]: Cannot open display:
dbus-daemon[1086]: [session uid=125 pid=1086] Activated service 'org.gnome.ScreenSaver' failed: Process org.gnome.ScreenSaver exited with status 1
gnome-session[1088]: gnome-session-binary[1088]: CRITICAL: Unable to create a DBus proxy for GnomeScreenSaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1
and so on.
At the point when I try to reawaken the desktop this message is written to the log:
gnome-shell[1497]: JS ERROR: Exception in callback for signal: activate: Error: Error invoking IBus.set_global_engine_async: Expected function for callback argument callback, got undefined
Any suggestions where/how I could find out what is going wrong, and fix it?!
Thanks, T
boot gnome gnome-screensaver
asked Apr 4 at 6:37
TrevorNTrevorN
236
add a comment |
Started yesterday; the system is running all the background applications it is supposed to but the only way to use it interactively is to power off completely and restart. The screen, keyboard and mouse then operate fine but if I go away for 10 minutes and the screen sleeps I can't get past the lock screen. Normally the ESC key or a mouse click will prompt for a login, but not any more.
Looking in syslog there is a truckload of gdm-x-session and gnome-shell errors. I don't know if this is relevant but the first of these after reboot is as follows:
dbus-daemon[1086]: [session uid=125 pid=1086] Activating service name='org.gnome.ScreenSaver' requested by ':1:12' (uid=125 pid=1088 comm="/usr/lib/gnome-session/gnome-session-binary --auto" label="unconfined")
org.gnome.ScreenSaver[1086]: Unable to init server: Could not connect: Connection refused
gnome-screensav[1094]: Cannot open display:
dbus-daemon[1086]: [session uid=125 pid=1086] Activated service 'org.gnome.ScreenSaver' failed: Process org.gnome.ScreenSaver exited with status 1
gnome-session[1088]: gnome-session-binary[1088]: CRITICAL: Unable to create a DBus proxy for GnomeScreenSaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1
and so on.
At the point when I try to reawaken the desktop this message is written to the log:
gnome-shell[1497]: JS ERROR: Exception in callback for signal: activate: Error: Error invoking IBus.set_global_engine_async: Expected function for callback argument callback, got undefined
Any suggestions where/how I could find out what is going wrong, and fix it?!
Thanks, T
boot gnome gnome-screensaver
asked Apr 4 at 6:37
TrevorNTrevorN
236
add a comment |
Started yesterday; the system is running all the background applications it is supposed to but the only way to use it interactively is to power off completely and restart. The screen, keyboard and mouse then operate fine but if I go away for 10 minutes and the screen sleeps I can't get past the lock screen. Normally the ESC key or a mouse click will prompt for a login, but not any more.
Looking in syslog there is a truckload of gdm-x-session and gnome-shell errors. I don't know if this is relevant but the first of these after reboot is as follows:
dbus-daemon[1086]: [session uid=125 pid=1086] Activating service name='org.gnome.ScreenSaver' requested by ':1:12' (uid=125 pid=1088 comm="/usr/lib/gnome-session/gnome-session-binary --auto" label="unconfined")
org.gnome.ScreenSaver[1086]: Unable to init server: Could not connect: Connection refused
gnome-screensav[1094]: Cannot open display:
dbus-daemon[1086]: [session uid=125 pid=1086] Activated service 'org.gnome.ScreenSaver' failed: Process org.gnome.ScreenSaver exited with status 1
gnome-session[1088]: gnome-session-binary[1088]: CRITICAL: Unable to create a DBus proxy for GnomeScreenSaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1
and so on.
At the point when I try to reawaken the desktop this message is written to the log:
gnome-shell[1497]: JS ERROR: Exception in callback for signal: activate: Error: Error invoking IBus.set_global_engine_async: Expected function for callback argument callback, got undefined
Any suggestions where/how I could find out what is going wrong, and fix it?!
Thanks, T
boot gnome gnome-screensaver
asked Apr 4 at 6:37
TrevorNTrevorN
236
Started yesterday; the system is running all the background applications it is supposed to but the only way to use it interactively is to power off completely and restart. The screen, keyboard and mouse then operate fine but if I go away for 10 minutes and the screen sleeps I can't get past the lock screen. Normally the ESC key or a mouse click will prompt for a login, but not any more.
Looking in syslog there is a truckload of gdm-x-session and gnome-shell errors. I don't know if this is relevant but the first of these after reboot is as follows:
dbus-daemon[1086]: [session uid=125 pid=1086] Activating service name='org.gnome.ScreenSaver' requested by ':1:12' (uid=125 pid=1088 comm="/usr/lib/gnome-session/gnome-session-binary --auto" label="unconfined")
org.gnome.ScreenSaver[1086]: Unable to init server: Could not connect: Connection refused
gnome-screensav[1094]: Cannot open display:
dbus-daemon[1086]: [session uid=125 pid=1086] Activated service 'org.gnome.ScreenSaver' failed: Process org.gnome.ScreenSaver exited with status 1
gnome-session[1088]: gnome-session-binary[1088]: CRITICAL: Unable to create a DBus proxy for GnomeScreenSaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1
and so on.
At the point when I try to reawaken the desktop this message is written to the log:
gnome-shell[1497]: JS ERROR: Exception in callback for signal: activate: Error: Error invoking IBus.set_global_engine_async: Expected function for callback argument callback, got undefined
Any suggestions where/how I could find out what is going wrong, and fix it?!
Thanks, T
boot gnome gnome-screensaver
boot gnome gnome-screensaver
asked Apr 4 at 6:37
TrevorNTrevorN
236
asked Apr 4 at 6:37
TrevorNTrevorN
236
asked Apr 4 at 6:37
TrevorNTrevorN
236
asked Apr 4 at 6:37
TrevorNTrevorN
236
asked Apr 4 at 6:37
TrevorNTrevorN
236
236
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
});
}
});
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%2f1131092%2f18-04-boots-ok-but-once-lock-screen-appears-i-cant-unlock-it%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
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%2f1131092%2f18-04-boots-ok-but-once-lock-screen-appears-i-cant-unlock-it%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
