gdm-session-worker crashed with signal 7 in g_simple_async_result_complete()

[McDope]

happened when i tried to restart x after a crash (which happened when opening a containing folder from firefox download) by using "sudo restart gdm" on tty2.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gdm 3.8.1.1-0ubuntu5 [modified: usr/bin/gdm-screenshot usr/lib/gdm/gdm-host-chooser usr/lib/gdm/gdm-session-worker usr/lib/gdm/gdm-simple-chooser usr/lib/gdm/gdm-simple-greeter usr/lib/gdm/gdm-simple-slave usr/lib/gdm/gdm-xdmcp-chooser-slave usr/sbin/gdm]
ProcVersionSignature: Ubuntu 3.10.0-5.15-generic 3.10.2
Uname: Linux 3.10.0-5-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.11-0ubuntu1
Architecture: amd64
Date: Thu Jul 25 11:08:36 2013
ExecutablePath: /usr/lib/gdm/gdm-session-worker
InstallationDate: Installed on 2010-05-06 (1177 days ago)
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
MarkForUpload: True
ProcCmdline: gdm-session-worker\ [pam/gdm-launch-environment]
ProcEnviron:
 LANG=de_DE.UTF-8
 TERM=linux
 PATH=(custom, no user)
Signal: 7
SourcePackage: gdm
StacktraceTop:
 ?? () from /usr/lib/libaccountsservice.so.0
 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gdm-session-worker crashed with signal 7 in g_simple_async_result_complete()
UpgradeStatus: Upgraded to saucy on 2013-07-06 (20 days ago)
UserGroups:

mtime.conffile..etc.dconf.db.gdm: 2013-07-06T14:30:40.545261
mtime.conffile..etc.init.d.gdm: 2013-07-20T01:22:46

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1202352, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.