18.04 boots ok, but once lock screen appears I can't unlock itGnome-Shell and Unity run at the same timeWhy...

CAST throwing error when run in stored procedure but not when run as raw query

Arrow those variables!

Expand and Contract

Assassin's bullet with mercury

How did the Super Star Destroyer Executor get destroyed exactly?

How do I deal with an unproductive colleague in a small company?

Can my sorcerer use a spellbook only to collect spells and scribe scrolls, not cast?

Why do bosons tend to occupy the same state?

Is it inappropriate for a student to attend their mentor's dissertation defense?

How can I prevent hyper evolved versions of regular creatures from wiping out their cousins?

How do I gain back my faith in my PhD degree?

Little known, relatively unlikely, but scientifically plausible, apocalyptic (or near apocalyptic) events

Are there any examples of a variable being normally distributed that is *not* due to the Central Limit Theorem?

Can a virus destroy the BIOS of a modern computer?

How can saying a song's name be a copyright violation?

Venezuelan girlfriend wants to travel the USA to be with me. What is the process?

Unlock My Phone! February 2018

How to remove strange space symbols in Word

What reasons are there for a Capitalist to oppose a 100% inheritance tax?

Size of subfigure fitting its content (tikzpicture)

What exploit are these user agents trying to use?

Is it possible to create a QR code using text?

Is the myth that if you can play one instrument, you can learn another instrument with ease true?

How to show a landlord what we have in savings?



18.04 boots ok, but once lock screen appears I can't unlock it


Gnome-Shell and Unity run at the same timeWhy doesn't Gnome3 work even after trying all these workarounds?How to debug slow session start of Gnome 3?Desktop shows a combination of gnome 2 and gnome 3 elementsCannot unlock from graphical screenUbuntu 14.10 x64 very slow boot. Nouveau / nVidia: broken pipe?Cannot login to Gnome Shell after random lockup on 15.10Terminal won't openUnable to end session/log out using lightdm (16.04)After upgrade from 16.04 LTS to 18.04 LTS, display manager fails apparently because of freedesktop













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










share|improve this question



























    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










    share|improve this question

























      0












      0








      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










      share|improve this question














      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






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 11 mins ago









      TrevorNTrevorN

      235




      235






















          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
          });


          }
          });














          draft saved

          draft discarded


















          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
















          draft saved

          draft discarded




















































          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.




          draft saved


          draft discarded














          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





















































          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







          Popular posts from this blog

          Why do type traits not work with types in namespace scope?What are POD types in C++?Why can templates only be...

          Will tsunami waves travel forever if there was no land?Why do tsunami waves begin with the water flowing away...

          Should I use Docker or LXD?How to cache (more) data on SSD/RAM to avoid spin up?Unable to get Windows File...