420036 - after autoconnect on start the status bar still shows as "disconnected"

Status: RESOLVED WORKSFORME

(Cloud Services :: General, defect)

Description

[bugzilla.mozilla.org]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b4pre) Gecko/2008022703 Minefield/3.0b4pre
Build Identifier: weave-0.1.18, Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b4pre) Gecko/2008022703 Minefield/3.0b4pre

I think this is an error with the status menu not showing the real status
Using weave-0.1.18 in Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b4pre) Gecko/2008022703 Minefield/3.0b4pre

When I started FF3 this morning the weave status icon did not show the account name and had the "Sign in ..." option available. But looking at the log shows that weave actually tried to sync with my account (replaced by xxxxxxxxx). (It failed because network was down at that moment)


2008-02-28 09:07:27	Service.Main	INFO	Weave Sync Service Initializing
2008-02-28 09:07:27	Service.Main	INFO	Weave scheduler enabled
2008-02-28 09:07:29	Chrome.Window	INFO	Sync window opened
2008-02-28 09:07:29	Service.Main	INFO	Hashing username xxxxxxxxxxxxxx
2008-02-28 09:07:29	Service.Main	INFO	Using server URL: https://services.mozilla.com/user/xxxxxxxxxxxxxxxxx/
2008-02-28 09:07:29	Service.DAV	INFO	Logging in
2008-02-28 09:07:56	Service.DAV	WARN	_makeRequest: got status 2147746065
2008-02-28 09:07:56	Service.Main	INFO	Hashing username xxxxxxxxxxxxxxxx
2008-02-28 09:07:56	Service.DAV	WARN	_makeRequest: got status 2147746065
2008-02-28 09:07:56	Service.DAV	WARN	_makeRequest: got status 2147746065

Now, looking at the weave prefs, there is no immediate indication but one level deeper, on the "Sign in" dialog, I see that I have "Automatically connect on start" turned on. I understand that this causes weave to connect with the saved account. 

For consistency it should make that a real "sign in" action and update it's status to show that the user is logged in. 


Reproducible: Always




possible related bugs #410550 #410551

Comment 1

[Dan Mills [:thunder]]

I'm not sure I understand this bug.

Autoconnect is enabled, and you've confirmed that it did in fact try to connect.  It failed because your network was down, and so it remains 'disconnected', since it did not successfully log in.

This seems like expected behavior to me.