Closed
Bug 576749
Opened 14 years ago
Closed 14 years ago
Firefox Sync 1.4 doesn't connect automatically on newly created Ubuntu 10.04 profiles (works with migrated ones) both with Ubuntu custom build and with the official Mozilla one
Categories
(Cloud Services :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 577608
People
(Reporter: mgol, Unassigned)
References
Details
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.6) Gecko/20100628 Ubuntu/10.04 (lucid) Firefox/3.6.6 Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.6) Gecko/20100628 Ubuntu/10.04 (lucid) Firefox/3.6.6 Firefox Sync 1.4 doesn't connect automatically after starting a browser. Reproducible: Always Steps to Reproduce: 1. Open Firefox 2. Go to Tools -> Sync 3. Actual Results: The field Connect is active, indicating that Firefox Sync is disconnected. Expected Results: Firefox Sync should connect automatically at browser start.
Comment 1•14 years ago
|
||
Do you have a master password set?
Component: General → Needs Triage
Product: Firefox → Weave
QA Contact: general → needstriage
Reporter | ||
Comment 2•14 years ago
|
||
No, I don't.
Reporter | ||
Comment 3•14 years ago
|
||
My browser add-ons, if anyone's interested (obtained with InfoLister): Extensions (enabled: 23, disabled: 0): * Adblock Plus 1.2 * Adblock Plus Filter Uploader 2.0.1 * Cooliris 1.12.0.36605 * DownloadHelper 4.7.3 * DownThemAll! 1.1.10 * Fast Dial 2.23b1 * Firebug 1.5.4 * Firefox Sync 1.4 * FirefoxNotify 1.5.4 * FireGestures 1.5.7 * Flash Killer 1.2.1 * Google Gears 0.5.36.0 * Greasemonkey 0.8.20100408.6 * InfoLister 0.10.3 * LeechBlock 0.5 * Long URL Please 0.4.3 * NoScript 1.9.9.97 * Novell Moonlight 2.2 * Read It Later 2.0.6 * RightToClick 2.7.2 * Tab Mix Plus 0.3.8.4 * Update Scanner 3.1.2 * User Agent Switcher 0.7.2 Themes (1): * Default 3.6.6 [selected] Plugins (11): * Adobe Reader 9.3 * Cooliris * DivX Browser Plug-In * Java(TM) Plug-in 1.6.0_20 * mplayerplug-in is now gecko-mediaplayer 0.9.9.2 * Picasa * QuickTime Plug-in 7.6.4 * RealPlayer 9 * Shockwave Flash * Silverlight Plug-In * Windows Media Player Plug-in
Comment 4•14 years ago
|
||
A Sync log would be helpful. https://wiki.mozilla.org/Labs/Weave/ReportingBugs
Reporter | ||
Comment 5•14 years ago
|
||
How can I get this log? I don't see an option in Sync 1.4 Tools menu.
Comment 6•14 years ago
|
||
about:sync-log oddly, the only other report I've seen of this involved Ubuntu 10.04 as well.
Reporter | ||
Comment 7•14 years ago
|
||
2010-07-03 21:30:03 Service.Main INFO Loading Weave 1.4 2010-07-03 21:30:03 Engine.Bookmarks DEBUG Engine initialized 2010-07-03 21:30:03 Engine.Forms DEBUG Engine initialized 2010-07-03 21:30:03 Engine.History DEBUG Engine initialized 2010-07-03 21:30:03 Engine.Passwords DEBUG Engine initialized 2010-07-03 21:30:03 Engine.Prefs DEBUG Engine initialized 2010-07-03 21:30:03 Engine.Tabs DEBUG Engine initialized 2010-07-03 21:30:03 Engine.Tabs DEBUG Resetting tabs last sync time 2010-07-03 21:30:03 Service.Main INFO Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.6) Gecko/20100628 Ubuntu/10.04 (lucid) Firefox/3.6.6 2010-07-03 21:30:03 Service.Util DEBUG Using a fake svc object for @labs.mozilla.com/Weave/Crypto;2 2010-07-03 21:30:03 Service.Main DEBUG Caching URLs under storage user base: https://phx-sync295.services.mozilla.com/1.0/USERNAME/
Comment 8•14 years ago
|
||
If you've manually disconnected at some point, Sync won't reconnect until you tell it to. If you connect, then restart, does it autoconnect then?
Reporter | ||
Comment 9•14 years ago
|
||
Nope, I would discover such a simple problem myself. I am connected, then I close and re-run Firefox and afterwards I'm not connected any more.
Reporter | ||
Comment 10•14 years ago
|
||
I just reproduced it without any problem on a new profile with only Firefox Sync installed, with my Firefox Sync login from the default Fx profile.
Comment 11•14 years ago
|
||
(In reply to comment #10) > I just reproduced it without any problem on a new profile with only Firefox > Sync installed, with my Firefox Sync login from the default Fx profile. Do you see your Sync password and secret phrase saved in Firefox's password manager? Do you have Firefox configured to never remember passwords?
Reporter | ||
Comment 12•14 years ago
|
||
> Do you see your Sync password and secret phrase saved in Firefox's password
> manager? Do you have Firefox configured to never remember passwords?
That's what I did a while ago:
1) I set up another temporary profile and installed Firefox Sync 1.4
2) I set up a new Fx Sync account, I told it to sync and waited till the end of synchronization process
3) I turned Firefox off and on (Sync was not connected)
4) I connected manually to Sync
5) goto 3
I guess that pretty much answers all of Your questions (and many more).
Reporter | ||
Comment 13•14 years ago
|
||
Password must have been always saved as I only have to connect manually but Fx doesn't ask me for a password or/and secret phrase.
Comment 14•14 years ago
|
||
In about:config, what is the value of services.sync.autoconnect, and is it shown as the default value?
Reporter | ||
Comment 15•14 years ago
|
||
true, default.
Comment 16•14 years ago
|
||
That's odd... can't repro, but I don't have an Ubuntu box on hand. Can you set javascript.options.showInConsole to true, restart, and see if anything shows up in the Error Console? Also, can you test with a build from mozilla.com, instead of the Ubuntu build?
Reporter | ||
Comment 17•14 years ago
|
||
Nothing in the Error Console with javascript.options.showInConsole set to true. I also tried the official Mozilla build with the profile mentioned in the comment 12 and it was the same - an empty Error Console, services.sync.autoconnect still set to true and marked as default and still no autoconnecting at start. Only this time, with official build, I am getting this in bash: /usr/lib/gio/modules/libgvfsdbus.so: wrong ELF class: ELFCLASS64 Failed to load module: /usr/lib/gio/modules/libgvfsdbus.so It seems related to the fact that the official build is 32-bit, whilst Ubuntu ships 64-bit browser.
Reporter | ||
Comment 18•14 years ago
|
||
OK, now this appeared in the Error Console (sometimes it shows up, sometimes not...) Failed to load XPCOM component: /home/USER/.mozilla/firefox/XXXXXXXX.YYY/extensions/{340c2bbc-ce74-4362-90b5-7c26312808ef}/platform/Linux/components/WeaveCrypto.so
Reporter | ||
Comment 19•14 years ago
|
||
I can reproduce it neither on Windows with Firefox 3.6.6 nor on Arch Linux with its Namoroka 3.6.6 build (both run in VirtualBox 3.2 under Ubuntu 10.04). I don't know if it's of any relevance but I've noticed another difference - both Windows's Firefox and Arch's Namoroka show Sync icon in Tools menu (and for some other things, too). In Ubuntu 10.04 I don't see any icons at Tools menu entries, no matter if using Mozilla official build or Ubuntu one.
Comment 20•14 years ago
|
||
Just an idea what would happen if Network Manager thought it was in a disconnected state.
Reporter | ||
Comment 21•14 years ago
|
||
What exactly do You mean? My NM applet claims to be connected all the time and Firefox Sync doesn't loose connection. It just doesn't automatically connect at browser start.
Comment 22•14 years ago
|
||
I'd like to confirm that I'm seeing this bug on my machine. Linux distribution is Linux Mint 9 64-bit (Ubuntu 10.04 based) Mozilla info: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.6) Gecko/20100628 Linux Mint/9 (Isadora) Firefox/3.6.6 which I got from the Ubuntu repositories for lucid, exact package version is 3.6.6+nobinonly-0ubuntu0.10.04.1 I followed all your troubleshooting recommendations on the comments above and get the exact same behavior as Michael. Specifically, no sync-log or Error console entries that would indicate a problem. Everything indicates that firefox doesn't even try to connect sync on startup, perhaps ignoring the .autoconnect=true option. Problem does not exist on my other similar setup but 32-bit machine. Perhaps we can change a logging level somewhere in about:config to get more data?
Comment 23•14 years ago
|
||
I've seen the same bug on a machine running Fedora 12 64-bit, with Firefox 3.5.9. My other machines running Fedora 13 64-bit did not show this problem. Strangely enough, while I was able to reliably reproduce this bug on the F12 machine yesterday, I couldn't reproduce it today, even though I haven't installed any updates. I'm connecting to my own Weave Minimal Server, FWIW.
Comment 24•14 years ago
|
||
Progress! After having tried a fresh profile without any extensions except Sync, I've tried disabling extensions in my regular profile (quite fresh, but lots of addons). I've found two extensions, which when enabled, cause the auto-login not to happen: - User Agent Switcher 0.7.2 (might interfere with displaying the UA in the log?!) - Vimperator 2.4pre (patch for Minefield; might interfere with a lot) It can take about 1 minute for the "Logging in user foo" message to appear (longest has been 63 seconds, but I waited not forever of course - max 2 minutes in general). As said in bug 575964, it would be great to have additional DEBUG log entries regarding this. My extension collection is: https://addons.mozilla.org/en-US/firefox/collection/cfa4b018-82f8-1d7a-0404-c47f2fc5b8ef (Babelfish, HTML Validator, Selenium IDE, YSlow, User Agent Switcher and Vimperator currently disabled) I'm using my own minimal server, too, and can see the icon in the Tools menu. Where does Sync remember if it was connected on shutdown?
Comment 25•14 years ago
|
||
FWIW, I've filed a bug for Vimperator at: http://code.google.com/p/vimperator-labs/issues/detail?id=351
Reporter | ||
Comment 26•14 years ago
|
||
@Daniel Hahler You should probably fill in another bug report. I use User Agent Switcher on my main profile, but as I stated in comments 12: https://bugzilla.mozilla.org/show_bug.cgi?id=576749#c12 and 17: https://bugzilla.mozilla.org/show_bug.cgi?id=576749#c17 the problem is completely reproducible without installing any extensions at all (apart from Firefox Sync); with official Mozilla build, with a fresh Firefox profile and with a fresh Firefox Sync profile. It's reproducible only on Ubuntu 10.04, Arch Linux doesn't experience this problem. My bug report is thus definitely NOT associated with any other extensions.
Reporter | ||
Updated•14 years ago
|
Summary: Firefox Sync 1.4 doesn't connect automatically → Firefox Sync 1.4 doesn't connect automatically on Ubuntu 10.04 with fresh Firefox and Firefox Sync profiles, both with Ubuntu custom build and with the official Mozilla one
Reporter | ||
Comment 27•14 years ago
|
||
As we still don't know if it's Mozilla or Ubuntu's fault and it seems this bug is Ubuntu specific, I reported the bug on Launchpad: https://bugs.launchpad.net/firefox/+bug/603398
Comment 28•14 years ago
|
||
@Michał: do you have ubufox installed? (this is a Ubuntu firefox extension, and should show up in the list of addons)
Comment 29•14 years ago
|
||
@Michał: is it also reproducible for you with a vanilla Firefox build, e.g. from http://nightly.mozilla.org/ ?
Reporter | ||
Comment 30•14 years ago
|
||
@Daniel No, I don't. I used to have it but it generated so many problems that I purged it a long time ago. I've just checked (it sometimes installs itself again automatically during some major updates) and it's not installed.
Comment 31•14 years ago
|
||
@Michał: Ok, however, this affects my work machine on Windows XP, too (no Ubuntu there obviously). I do not think it's Ubuntu related, but only to something profile specific, which Ubuntu might install (like e.g. this extra extension).
Reporter | ||
Comment 32•14 years ago
|
||
@Daniel Yep, the problem persists with Firefox dev build. This time I see this message in terminal, though: $ ./firefox -no-remote -P tmp 2010-07-09 02:39:21 Service.Main ERROR Could not load the Weave crypto component. Disabling Weave, since it will not work correctly. Maybe it has something in common in what I described in comment 18? "Failed to load XPCOM component: /home/USER/.mozilla/firefox/XXXXXXXX.YYY/extensions/{340c2bbc-ce74-4362-90b5-7c26312808ef}/platform/Linux/components/WeaveCrypto.so"
Reporter | ||
Comment 33•14 years ago
|
||
(In reply to comment #31) > @Michał: Ok, however, this affects my work machine on Windows XP, too (no > Ubuntu there obviously). > I do not think it's Ubuntu related, but only to something profile specific, > which Ubuntu might install (like e.g. this extra extension). Well, maybe You're right. However, with Windows XP You need some specific configuration to trigger the bug (as You described; besides, I was unable to reproduce it in my VirtualBox Window XP installation), in Ubuntu this bug "works" out-of-the-box. ;)
Comment 34•14 years ago
|
||
(In reply to comment #24) > I've found two extensions, which when enabled, cause the auto-login not to > happen: > - User Agent Switcher 0.7.2 (might interfere with displaying the UA in the > log?!) Well, I hate to admit it, but my problem was solved by disabling the User Agent Switcher. Funny thing, I thought I'd reproduced it on a new profile while it was active on my main one. Cross profile trouble seems too much off to retry, but I could if you want. Sorry for not chipping in properly in the first place, and thank you for the User Agent Switcher heads-up.
Reporter | ||
Comment 35•14 years ago
|
||
Erm... I uninstalled User Agent Switcher and on my main profile the problem disappeared. I was *really* surprised as I tested it with new profiles without extensions, too, so I created another new Fx profile and registered it with another new Fx Sync profile and the problem exists on this new profile... I'm really not getting what's going on here...
Comment 36•14 years ago
|
||
I had the same problem on Fedora 13 x86_64 boxes. Disabled User Agent Switcher - now Sync auto-connects. *shrugs*
Comment 37•14 years ago
|
||
Ok guys, I did some more testing and here are my results: We are talking about two different bugs here! One bug is about User Agent Switcher (and as mentioned Vimperator which I did not test) This affects all versions I have, on all systems. The second bug is about the Ubuntu builds: Any profile initialized with my 3.6.6 builds from lucid won't autoconnect. This whole mixup was caused because our main profiles were migrated from a previous version, while our test profiles were initialized with the new version.. I've got a headache now :S :) Anyway, if you'd be so kind, please post me a sum of all the relevant ubuntu or extension bug reports that were opened, as I'd like to monitor them. Secondly, I'd still like to know if there is an option to enable to get more feedback on about:sync-log which might help.
Reporter | ||
Comment 38•14 years ago
|
||
Nick, You're a genius! :D I did think there are two different bugs, one for User Agent Switcher and another one for a clean Firefox but I didn't think that the thing that matters is at which OS version the profile was created. "Power users" usually migrate their profiles again and again so to not loose specific settings... We would probably discover it earlier if someone with new Ubuntu profile told us so... Anyway, as this bug's summary is about Ubuntu, I reported another bug for User Agent Switcher - please, subscribe there to discuss both issues separately. https://bugzilla.mozilla.org/show_bug.cgi?id=577608
Summary: Firefox Sync 1.4 doesn't connect automatically on Ubuntu 10.04 with fresh Firefox and Firefox Sync profiles, both with Ubuntu custom build and with the official Mozilla one → Firefox Sync 1.4 doesn't connect automatically on newly created Ubuntu 10.04 profiles (works with migrated ones) both with Ubuntu custom build and with the official Mozilla one
Reporter | ||
Comment 39•14 years ago
|
||
Also: since both those bugs seems to be confirmed by a large amount of users, could we mark them both as confirmed?
Comment 40•14 years ago
|
||
(In reply to comment #38) > the thing that matters is at which OS version the profile was created. To be exact, I've only tested the Ubuntu lucid x86_64 3.6.6 built against a x86 3.6.3 karmic built by mozilla-team (as a reference). That's because, frankly that's what my two PCs are set-up for. I still don't know how an Ubuntu lucid x86 3.6.6 built fares, nor if the bug is present on mozilla 3.6.6 builts. Sorry.
Reporter | ||
Comment 41•14 years ago
|
||
To summarize, those are problems reported so far: 1) Ubuntu-specific problem: newly created profiles without extensions are affected: https://bugzilla.mozilla.org/show_bug.cgi?id=576749 (this bug) https://bugs.launchpad.net/firefox/+bug/603398 2) Problems caused by extensions: 2a) User Agent Switcher: https://bugzilla.mozilla.org/show_bug.cgi?id=577608 2b) Vimperator: http://code.google.com/p/vimperator-labs/issues/detail?id=351 (no Bugzilla bug) Remark ad. 1) Problem seems to occur (I didn't do a thorough testing indicating that many migrated profiles all doesn't suffer from this bug) only on newly created Ubuntu 10.04 Firefox profiles, HOWEVER, it doesn't matter if they were created and used by Ubuntu Firefox build or Mozilla official one.
Reporter | ||
Comment 42•14 years ago
|
||
Sorry for double posting - the official build I'm talking about is 3.6.6 (32-bit, of course). So it seems it doesn't matter if the browser is 32- or 64-bit (but I don't know if I can say the same about OS "bitness").
See Also: → https://launchpad.net/bugs/603398
Comment 43•14 years ago
|
||
This bug is definitely NOT Ubuntu related, as I was able to reproduce it on a Fedora 12 machine. There is no User Agent Switcher and Vimperator installed.
Reporter | ||
Comment 44•14 years ago
|
||
@Richard So maybe it's related to profiles created under Firefox 3.6.6? My current profile has been created by Firefox 3.0 or earlier IIRC.
Comment 45•14 years ago
|
||
The profile on the Fedora 12 machine where the bug occurs, is rather "new" and was created with Firefox 3.5.8. The profile of the machine that does not show this bug, is actually very old. Maybe even pre Firefox 3.0... I will test a fresh profile on a fresh Fedora 13 installation later today and report the results. BTW: In my Comment 23, I reported that I couldn't reproduce this bug on the F12 machine yesterday. Sadly, today it reappeared again.
Comment 46•14 years ago
|
||
(In reply to comment #43) > This bug is definitely NOT Ubuntu related, as I was able to reproduce it on a > Fedora 12 machine. There is no User Agent Switcher and Vimperator installed. It might be another addon interfering in your case, of course.
Reporter | ||
Comment 47•14 years ago
|
||
(In reply to comment #43) @Richard Daniel is right, could You test it on a new profile (as I did with Ubuntu)?
Comment 48•14 years ago
|
||
Confirmed on Vista SP2. I have about ten extensions installed, non of which were updated after update to Sync 1.4. This is definitely a change in 1.4. This is problematic as Sync has now become unreliable, and the absence of feedback from the status bar just makes this problem worse.
Comment 49•14 years ago
|
||
OK I can confirm that it is a conflict with User Agent switcher. Might as well remove it.
Reporter | ||
Comment 50•14 years ago
|
||
@Christopher Please, don't write about User Agent Switcher in this bug report. Bug 577608 is meant for this. This bug report SPECIFICALLY states it's about profiles with NO extensions installed. People in this bug don't experience the problem with migrated profiles. Besides, if the only problem would be with UAS, it would mean that it's not necessarily Sync's bug. It might have been as well that UAS broke some interfaces that were not used before.
Comment 51•14 years ago
|
||
Well the title was changed since I saw the topic. Also I'm a newbie. I was just correcting previous posting to eliminate confusion. Is that being unhelpful?
Reporter | ||
Comment 52•14 years ago
|
||
(In reply to comment #51) > Well the title was changed since I saw the topic. Sorry, I thought You're new at this bug report. > Also I'm a newbie. I was just > correcting previous posting to eliminate confusion. Is that being unhelpful? No, I just wanted to make some things more clear. I'm just a bit afraid that if too many UAS-related comments happen here, more and more people can start reporting here instead of in bug 577608. Sorry if it sounded a bit harsh.
Comment 53•14 years ago
|
||
OFFTOPIC: For what it's worth, I'm now using the following in my vimperatorrc, and this enables connecting+sync at login, and additionally syncing on browser exit: autocmd VimperatorEnter .* emenu Tools.Sync.Connect autocmd VimperatorEnter .* emenu Tools.Sync.Sync Now autocmd VimperatorLeave .* emenu Tools.Sync.Sync Now
Comment 54•14 years ago
|
||
Is this fixed with 1.4.1b3? At least the bug 577608 is - and it may be the same race condition after all.
Reporter | ||
Comment 55•14 years ago
|
||
I experience neither this bug nor bug 577608 with Firefox Sync 1.4.1, it seems fixed.
Updated•14 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Updated•14 years ago
|
Component: Needs Triage → General
QA Contact: needstriage → general
You need to log in
before you can comment on or make changes to this bug.
Description
•