I too have the error displayed in the original bug.

I intentionally waited a good few seconds before logging in to help with
the log timestamps, my machine boots in ~3-5 seconds. No matter how long
I wait after boot before logging in, it always takes the same time to
show the desktop.

My login delay appears to be at this point.

Jan 12 20:53:53 Freyja rtkit-daemon[1975]: Successfully made thread 2798 of 
process 2798 (n/a) owned by '1000' high priority at nice level -11.
Jan 12 20:53:53 Freyja rtkit-daemon[1975]: Supervising 1 threads of 1 processes 
of 2 users.
Jan 12 20:54:07 Freyja rtkit-daemon[1975]: Supervising 1 threads of 1 processes 
of 2 users.


Just before all this, there is a lot of logging from gdm-x-session 
"configuring" my displays or something.

Those ~200 lines of gdm-x-session occur within about a 2 second period
(not much), just before this delay seen here. To my untrained eye it's
hard to see where the log relates to the login delay, but if it looks
like

As with yolen, I am also running "high res" displays, 3 x 3840x2160, 2 x
DP, 1 x HDMI and the Nvidia drivers and related hog a good proportion of
the log.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1736011

Title:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1736011/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Reply via email to