Running into this issue on 19.10, so none of the unity-specific
solutions work. If I switch TTY with ctrl+alt+F1, after I try to log
back in and just see the desktop background, I'm brought to login screen
again, but this time log in is successful. Disabling all gnome
extensions doesn't seem to help. Happens every time after suspending
laptop.

Not sure if this is helpful or relevant, but I tried looking at the
following logs:

% journalctl -e /usr/bin/gnome-shell

Feb 16 12:15:05 tula-Z gnome-shell[2114]: JS WARNING: 
[resource:///org/gnome/gjs/modules/signals.js 135]: Too many arguments to 
method Clutter.Actor.destroy: expected 0, got 
Feb 16 12:15:05 tula-Z gnome-shell[2114]: JS WARNING: 
[resource:///org/gnome/gjs/modules/signals.js 135]: Too many arguments to 
method Clutter.Actor.destroy: expected 0, got 
Feb 16 12:15:15 tula-Z gnome-shell[2114]: An active wireless connection, in 
infrastructure mode, involves no access point?
Feb 16 12:15:15 tula-Z gnome-shell[2114]: An active wireless connection, in 
infrastructure mode, involves no access point?
Feb 16 12:15:26 tula-Z gnome-shell[8675]: Failed to obtain high priority context
Feb 16 12:15:26 tula-Z gnome-shell[8675]: Failed to obtain high priority context
Feb 16 12:15:27 tula-Z gnome-shell[8675]: Unset XDG_SESSION_ID, 
getCurrentSessionProxy() called outside a user session. Asking logind directly.
Feb 16 12:15:27 tula-Z gnome-shell[8675]: Will monitor session c3
Feb 16 12:15:27 tula-Z gnome-shell[8675]: Getting invalid resource scale 
property
Feb 16 12:15:27 tula-Z gnome-shell[8675]: ibus_bus_hello: assertion 
'ibus_bus_is_connected (bus)' failed
Feb 16 12:15:27 tula-Z gnome-shell[8675]: Error while sending AddMatch() 
message: The connection is closed
Feb 16 12:15:27 tula-Z gnome-shell[8675]: ibus_bus_call_async: assertion 
'ibus_bus_is_connected (bus)' failed
Feb 16 12:15:27 tula-Z gnome-shell[8675]: Getting invalid resource scale 
property
Feb 16 12:15:27 tula-Z gnome-shell[8675]: ibus_bus_hello: assertion 
'ibus_bus_is_connected (bus)' failed
Feb 16 12:15:27 tula-Z gnome-shell[8675]: Error while sending AddMatch() 
message: The connection is closed
Feb 16 12:15:27 tula-Z gnome-shell[8675]: ibus_bus_call_async: assertion 
'ibus_bus_is_connected (bus)' failed
Feb 16 12:15:27 tula-Z gnome-shell[8675]: ibus_bus_call_async: assertion 
'ibus_bus_is_connected (bus)' failed
Feb 16 12:15:28 tula-Z gnome-shell[8675]: Error looking up permission: 
GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
Feb 16 12:15:28 tula-Z gnome-shell[8675]: JS WARNING: 
[resource:///org/gnome/shell/ui/windowManager.js 1640]: reference to undefined 
property "MetaWindowXwayland"
Feb 16 12:15:27 tula-Z gnome-shell[8675]: ibus_bus_call_async: assertion 
'ibus_bus_is_connected (bus)' failed
Feb 16 12:15:28 tula-Z gnome-shell[8675]: Error looking up permission: 
GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
Feb 16 12:15:28 tula-Z gnome-shell[8675]: JS WARNING: 
[resource:///org/gnome/shell/ui/windowManager.js 1640]: reference to undefined 
property "MetaWindowXwayland"
Feb 16 12:15:28 tula-Z gnome-shell[8675]: Registering session with GDM
Feb 16 12:15:34 tula-Z gnome-shell[2114]: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem 
:1.180/org/ayatana/NotificationItem/software_update_available
Feb 16 12:15:34 tula-Z gnome-shell[2114]: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem 
:1.90/org/ayatana/NotificationItem/dropbox_client_2433
Feb 16 12:15:34 tula-Z gnome-shell[2114]: [AppIndicatorSupport-FATAL] unable to 
update overlay icon
Feb 16 12:15:34 tula-Z gnome-shell[2114]: [AppIndicatorSupport-FATAL] unable to 
update overlay icon
Feb 16 12:15:34 tula-Z gnome-shell[2114]: [AppIndicatorSupport-FATAL] unable to 
update overlay icon
Feb 16 12:15:34 tula-Z gnome-shell[2114]: [AppIndicatorSupport-FATAL] unable to 
update overlay icon

Hope this is helpful!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to at-spi2-core in Ubuntu.
https://bugs.launchpad.net/bugs/1285444

Title:
  Login Successful, Desktop Never Loads

Status in at-spi2-core package in Ubuntu:
  Triaged

Bug description:
  Here is what I encounter
  1. Boot computer, boot proceeds normally
  2. Reach standard Ubuntu login screen, nothing seems to be amiss
  3. Enter user name and password
  4. Login disappears, just see the pink "Ubuntu 14.04" background

  The desktop never loads, not even after ~30 minutes. The launcher
  never appears, and the Desktop background never changes to the user-
  configured background.

  Other features:
  * Cursor works fine, it can be moved around the screen
  * No error messages pop up
  * ALT+F1 etc. can be used to switch to different TTYs; all files on the 
system appear to be intact
  * Print screen button works (I will upload a screen shot when I get a chance 
to copy it onto a USB drive)
  * Hitting power button pops up a window prompting the user to decide whether 
to shut down
  * CTRL+ALT+DELETE prompts the user to log out
  * Desktop does not load on any user accounts, including the guest account

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1285444/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to