Wiki gardening.

wiki/src/bugs/Failure_to_wipe_memory_when_RAM_disk_is_full.mdwn

@@ -42,6 +42,8 @@ memory.
 Probable solution: Force squashfs to keep certain files, especially
 the shutdown scripts and the files required for kexec, in memory.
 
+--JohnDoe
+
 > Already done using memlockd, see [[memory erasure implementation
 > notes|contribute/design/memory_erasure]] for details. Sounds like we
 > may have missed a few files, though: `/etc/init.d/gdm3 stop` is
@@ -51,4 +53,5 @@ the shutdown scripts and the files required for kexec, in memory.
 >> Do we need to stop gdm using the init-scripts instead of, let's say, kill -9
 >> when doing the *emergency* shutdown? --JohnDoe
 
---JohnDoe
+>>> Tails 0.9 uses pkill and fixes at least that probable cause.
+>>> Can anyone still reproduce the bug, or should we close it?

wiki/src/bugs/Tor_connection_error.mdwn

@@ -3,3 +3,8 @@ Booting into Tails 0.9 and connection to the Tor network never happens.  Vidalia
 > Does it happen consistently, or was it just once?
 
 I'm not the OP but it happens intermittently here too on two separate boxes. Manually opening Vidalia will sometimes show a single connection (like to Sickittotheman) but other times the network map is blank or says no relays available. Rebooting may or may not help.
+
+> With that little information, there's nothing we can do about it
+> => closing :/
+
+[[done]]

wiki/src/bugs/X_very_slow_in_0.8.mdwn

@@ -99,3 +99,11 @@ All other processes are 0% or near 0%. Here is some output from syslog:
 >> command-line, by pressing TAB in the initial language choosing
 >> menu. Does it solve the issue you're experiencing?
 >> `xorg-driver=vesa` is worth trying as well.
+
+>>> No reply since months, closing. Hopefully 0.10 (and its backported
+>>> X.Org stack) will help. In this area, there's not much *we* can do
+>>> about it, but include more recent drivers and forward bug reports
+>>> upstream... and the latter needs reactive bug reporters to be
+>>> worth it.
+
+[[done]]