Takes for life to login?

After updating to 10.04, Ubuntu takes a long period of time (1 - 2 mins) to login after keying the qualifications. Most of this moment the dialog box claims "examining qualifications". Just how do I also deal with debugging what is taking place below? This is a really stylish system, yet evidently something is hanging or otherwise reacting throughout the login.

Below is my :0 - greeter.log. Any kind of suggestions?

Window manager warning: Failed to read saved session file /var/lib/gdm/.config/metacity/sessions/1046b54d5b8b97fbb2128498129581685800000016580008.ms: Failed to open file '/var/lib/gdm/.config/metacity/sessions/1046b54d5b8b97fbb2128498129581685800000016580008.ms': No such file or directory
** (process:1742): DEBUG: Greeter session pid=1742 display=:0.0 xauthority=/var/run/gdm/auth-for-gdm-pWDXxn/database

(gnome-power-manager:1745): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.24.1/gobject/gsignal.c:2273: signal `proxy-status' is invalid for instance `0x21f5160'

** (gnome-power-manager:1745): WARNING **: Either HAL or DBUS are not working!

** (gnome-power-manager:1745): WARNING **: proxy failed

** (gnome-power-manager:1745): WARNING **: failed to get Computer root object

** (gnome-power-manager:1745): WARNING **: proxy NULL!!
gdm-simple-greeter[1742]: Gtk-WARNING: /build/buildd/gtk+2.0-2.20.1/gtk/gtkwidget.c:5636: widget not within a GtkWindow
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xe00046 (Login Wind)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xe00046 (Login Wind)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.

(gnome-settings-daemon:1666): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates_libgtk_only: assertion `private->update_and_descendants_freeze_count > 0' failed
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xe00046 (Login Wind)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: CurrentTime used to choose focus window; focus window may not be correct.
Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0.  This shouldn't happen!

(gnome-power-manager:1745): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
0
2019-05-13 04:29:36
Source Share
Answers: 4

As a start, attempt reading /var/log/gdm/:0-greeter.log. See if you can detect the hold-up by adhering to the timestamps in /var/log/auth.log.

0
2019-05-17 17:31:24
Source

Idea # 1: Sounds like maybe DNS - timeout relevant probably?

  • Validate your network setups, and also see to it you can sound any kind of DNS web servers detailed in /etc/resolv.conf.
  • Attempt doing some points that will certainly settle names to IPs, like ping www.google.com

If they do not function, or take a long period of time, that can be the concern.

Suggestion # 2 : Is this equipment making use of something exterior - like LDAP or NIS or something - for auth qualifications? If so, maybe waiting on feedback from that exterior equipment.

0
2019-05-17 17:30:14
Source

" HAL or DBUS not functioning" is to Gnome as "gas pump not functioning" is to auto, or at the very least close. gnome - power - supervisor isn't creating your trouble, yet its issue is respectable sign of what is. There are 2 prongs to the solution:

conserve the globe

This is "need to not take place" and also if it has actually taken place to you on an Ubuntu LTS upgrade, it likely has or will certainly take place to somebody else and also Ubuntu needs to know concerning it. The command to make use of is

$ ubuntu-bug gdm

as recorded at Reporting Bugs - HowTo.

save on your own

There was a time when I can assert thorough expertise of the Unix procedure power structure and also initialization regimens ; no more. I locate the dbus system fairly magical, and also need to consider:

  1. expanded, described, excruciating debug sessions, or
  2. make use of the Microsoft "Nuke it from Orbit Approach to System Administration" ® Across this

transmission capacity minimal network, I would certainly advise (2) and also:

  • visit on the console Ctrl-Alt F1
  • nuke gdm, dbus and also relationships with sudo apt-get purge gdm dbus dbus-x11
  • reboot
  • from the console reinstall gdm and also dbus with sudo apt-get install gdm dbus dbus-x11
  • reboot
  • calculate in euphoric consistency

Good good luck.

0
2019-05-13 16:32:00
Source

There were some wonderful pointers below, and also I desire I can do greater than simply upvote. Nonetheless, the actual trouble which I uncovered many thanks to msw, was this bug https://bugs.launchpad.net/ubuntu/+source/samba/+bug/584428

To address it, I commented out this line in/ etc/pam. d/common - auth

auth optional pam_smbpass.so migrate

I do not recognize why this creates troubles ; I never ever made use of samba for login verification on this equipment.

0
2019-05-13 15:54:39
Source