unity-greeter crashed with signal 5 in atspi_dbus_connection_setup_with_g_main()

[Michael Walker]

1.)
Description: Ubuntu Saucy Salamander (development branch)
Release: 13.10

2.)
unity-greeter:
  Installed: 13.10.3-0ubuntu1
  Candidate: 13.10.3-0ubuntu1
  Version table:
 *** 13.10.3-0ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
        100 /var/lib/dpkg/status

3.) I expected that no error message occured after the startup.
4.) An error message occured after the startup.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: unity-greeter 13.10.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
Uname: Linux 3.11.0-11-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
Date: Sun Oct 6 23:36:22 2013
ExecutablePath: /usr/sbin/unity-greeter
InstallationDate: Installed on 2012-06-05 (491 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MarkForUpload: True
ProcCmdline: /usr/sbin/unity-greeter
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/false
Signal: 5
SourcePackage: unity-greeter
StacktraceTop:
 atspi_dbus_connection_setup_with_g_main () from /usr/lib/x86_64-linux-gnu/libatspi.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 gtk_main_do_event () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: unity-greeter crashed with signal 5 in atspi_dbus_connection_setup_with_g_main()
UpgradeStatus: Upgraded to saucy on 2013-10-06 (2 days ago)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 atspi_dbus_connection_setup_with_g_main (connection=0x0, context=context@entry=0x120ce20) at atspi-gmain.c:602
 atspi_set_main_context (cnx=cnx@entry=0x120ce20) at atspi-misc.c:1667
 switch_main_context (cnx=0x120ce20) at event.c:70
 send_and_allow_reentry (message=0x1477c00, bus=0x11f3c50) at event.c:107
 Accessibility_DeviceEventController_NotifyListenersSync (key_event=0x7fff13d302a0) at event.c:153

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[John Belton (jbelton1950)]

The problem occured when I ran the update this morning (2014-02-05) when I had enabled the "on screen keyboard" as it was still dark, the update completed but the fault flag appeared on reboot without the title bar or launcher showing.
John

[John Belton (jbelton1950)]

The problem persists with no normal keyboard access until "on screen keyboard" is activated but still no launcher or top panel on the GUI. I have not found a way to restore the normal GUI operation yet.

[John Belton (jbelton1950)]

It happened again when I powered up this morning, before I could enter my password the error alert came on screen then dissappeared until after I logged in when it re-appeared. I am also getting warnings about backup unable to open /home/john/.cache/dconf
/home/john/.gvfs
folders for backup, it may be an operation sequence at the start-up that is causing the problem.
John

[nvsoar (nvsoar)]

For info - workaround for me is to click twice on any of the icons at the top right of the password log in screen. This action will allow the hardware keyboard to make an entry.

[John Belton (jbelton1950)]

This time it occured after updateing and failing to reboot cleanly. It didn't seem to complete the shutdown/reboot sequenceproperly, the keyboard was inactive and the "on-screen keyboard" didn't work either. I powered off and started again and though it was slower than normal booting it seems to have recovered.
John