User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b9) Gecko/20110110 Firefox/4.0b9 Build Identifier: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b9) Gecko/20110110 Firefox/4.0b9 I have three devices running with firefox. One X86_64 PC (openSUSE 11.3), one X86 PC (openSUSE 11.3) and a Nokia N900 (Maemo5 PR1.3). Firefox Sync works really good on the 64bit machine and on the N900, but when I try to configure sync on the 32bit machine, it every time fails. When I use the add device wizard it generates the three part code again and again, it fails every time. So I tried to do it by hand. I entered all required information including the sync key, but then the Firefox on the 32bit machine crashes reproducible. The both PCs run the same version of Firefox, only the architecture is different. When I try the wizard way to add a new device, the error console of the that should be added prints: Service.JPAKEClient ERROR Failed to encrypt key. When I try it by hand, GDB repots the following: Program received signal SIGSEGV, Segmentation fault. 0xb5d4a650 in PK11_ImportSymKey () from /usr/lib/libnss3.so Reproducible: Always Steps to Reproduce: 1.Choose Tools -> Set UP Sync... 2.Choose Connect 3.Enter Code Or 1.Choose Tools -> Set UP Sync... 2.Choose Connect 3.Choos I dont't have the device with me 4.Enter information and sync key Actual Results: In the first variant nothing happens, it generates one code after another, console prints: SERVICE.JPAKECLient ERROR Failed to encrypt key. In the second variant firefox craches with es segmentation fault. Expected Results: Set up a new sync device. On both PCs Firefox 4 Beta 9 is in use, build by openSUSE Build Service project mozilla:beta. On the N900 the last beta from Firefox is in use, too. It works on the 64bit machine and on the N900.

CCing bsmith, perhaps he can provide some input on this issue?

Seems to be a problem with Firefox 4 on openSUSE 11.3. On openSUSE 11.3 it does not work with any beta of Firefox 4, but on openSUSE 11.4 RC1 it works. So I close this as RESOLVED WORKSFORME an report this behavior in Novell bugzilla.