docky will not start at login

[Rob Peters]

Two 13.04 systems running docky. About every third or forth time logging in the docky application will not start. The docky.desktop file in .config/autostart is listed below. Did not notice this behavior on 13.04. Problem is observed in virtualbox as well as on a Thinkpad t60.

[Desktop Entry]
Version=1.0
Encoding=UTF-8
Name=Docky
Type=Application
Exec=docky
Terminal=false
Icon=docky
Comment=The finest dock no money can buy.
NoDisplay=false
Categories=Utility;

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: docky 2.2.0-1
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic i686
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
Date: Sat Oct 19 09:34:29 2013
InstallationDate: Installed on 2013-07-14 (96 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130714)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: docky
UpgradeStatus: No upgrade log present (probably fresh install)

[Rob Peters (makitso)]

Sorry, shoud have been "Two systems on 13.10..."

[Rob Peters (makitso)]

Also, this is with xubuntu

[Rob Peters (makitso)]

Upon close examination, Docky does start but then terminates within 1 or 2 seconds after the main screen displays. Confirmed that there is no Docky process running after the fail.

[Rob Peters (makitso)]

The program 'Docky' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 1327 error_code 11 request_code 53 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)