Hii sajolida,

Alas, I did not properly record that data.  The recorded times that I reported were from a subsequent boot. At the time, I was focused on writing down the content of the message to record it (and not lose it). IMO any such message should be logged somewhere to alleviate the user from taking down that content.  Also, it would be great is Tails could log the events/messages like this and notify the user to task them to Whisper back to the development team when an error occurs - if that is possible - sort of like a boot trace to detect anomalies that the development team can really use to improve the reporting process.
 
 
On 02/18/14, [email protected] wrote:
 
[email protected]:
> I was connected to the Internet, but with regard to answering the 2nd question
> there appears to be an ambiguity in the phrase "Tor was ready" when the message
> appeared, at least according to my understanding as described below.
>
> The normal sequence I have recorded when Tails boots up is that I have my router
> turned off so that I can setup my preferences in torrc, and run macchanger.
> When I turn the router on, I get the following 3 messages in a small black oval:
> Note: I am starting to keep a log of the 24 hour time each occurs
> 21:34:11 Connected to eth0 (i.e. Internet with regard to your question)
> 21:34:11 Syncing the system clock
> 21:35:50 Tor is Ready
>
> When Vidalia (Yellow status appears) I am monitoring the Message Log, The
> Vidalia Control Panel, The Bandwidth and the Network Map with the results:
> From the Message Log:
> 21:35.52 (for both) Tor software is running and Connected to Tor Network
>
> 21:45:21 Vidalia Green (just under 10 minutes)
>
> The ambiguity mentioned above is due to the fact that two different events are
> reported with the same text message output:
> 21:35:52 Connected to the Tor Network (from the Message Log) <----- This is when
> Vidalia is still in Yellow Status and No websites in Connection (Network Map)
> 21:45:21 Connected to the Tor Network (from the Vidalia Control Panel Green
> Status) <---- This is the real deal when the Bandwidth starts to paint
>
> I do not consider that "Tor is ready" until the Connection Map subpart of the
> Network Map window is populated which took about 10 minutes in the above
> sequence to occur. I consider that the above message at 21:35:50 for Tor is
> Ready really indicates that the system clock has been successfully synchronized,
> and that the message at 21:35:52 Connected to Tor Network does not fully mean
> that the Tor Network is actually ready or safe for a user to use at that point
> in time.
>
> I probably got the message due to my use case of not being connected to the
> Internet while I was doing my standard setup as described with the router off.
> This may indicate that the launching of Tails Upgrader instead of being launched
> silently at the beginning of each working session should more properly be tied
> to the notion of being connected to Internet as you asked in your question. I'm
> guessing that the Tails Upgrader was already initiated during the time that my
> router was off, and that whatever state the Tails Upgrader was in when I turned
> on the router was what initiated the error message I experienced.

Thanks for the precise report. I raised the issue on our development
list. It might be possible to improve on the logic of the Tails Upgrader
launcher. See:

https://mailman.boum.org/pipermail/tails-dev/2014-February/004900.html

Could you also tell us when the error message of Tails Upgrader appears?





_______________________________________________
tails-support mailing list
[email protected]
https://mailman.boum.org/listinfo/tails-support
To unsubscribe from this list, send an empty email to [email protected].
_______________________________________________
tails-support mailing list
[email protected]
https://mailman.boum.org/listinfo/tails-support
To unsubscribe from this list, send an empty email to 
[email protected].

Reply via email to