summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2012-10-16 12:34:22 -0400
committerGravatar Joey Hess <joey@kitenet.net>2012-10-16 12:34:22 -0400
commit4d7b4e14610bcc4f00c706b15390f5a81b6cd35f (patch)
tree7b2ef56e5ba277f188bc0a4f2e4d21d3f3c34caf
parent65415c5a241b0172832be0e321e2d515837944a2 (diff)
fixed
-rw-r--r--doc/bugs/Assistant_enters_eternal_loop_and_eats_up_all_of_RAM_after_X_restart.mdwn6
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/bugs/Assistant_enters_eternal_loop_and_eats_up_all_of_RAM_after_X_restart.mdwn b/doc/bugs/Assistant_enters_eternal_loop_and_eats_up_all_of_RAM_after_X_restart.mdwn
index bf364370d..d3f539431 100644
--- a/doc/bugs/Assistant_enters_eternal_loop_and_eats_up_all_of_RAM_after_X_restart.mdwn
+++ b/doc/bugs/Assistant_enters_eternal_loop_and_eats_up_all_of_RAM_after_X_restart.mdwn
@@ -16,3 +16,9 @@ I've also seen it happen on another computer in similar circumstances. That one
*Please provide any additional information below.*
Given that the assistant isn't really using X directly, I suppose this could be due to losing its connection to the gpg and ssh agents as a side-effect of X being shut down. I'm not sure if it happens immediately after X being killed, or once I log back in again.
+
+> Reproduced. Root caused to a bug in the haskell dbus library, which I can
+> reproduce with 2 line test case; basically anything using connectSession
+> will do this when the dbus session goes away. Sent test case and
+> profiling data to library author to get it fixed, and have disabled
+> dbus in git-annex in the meantime. [[done]] --[[Joey]]