Closed Bug 64323 Opened 24 years ago Closed 24 years ago

View Saved Data hangs the browser on linux

Categories

(Toolkit :: Form Manager, defect)

x86
Linux
defect
Not set
critical

Tracking

()

VERIFIED DUPLICATE of bug 58417

People

(Reporter: blizzard, Assigned: morse)

Details

When I use the View Saved Data button on Linux on the new toolbar or in prefs
the browser hangs on linux.  It doesn't crash but it doesn't ever refresh
windows or respond to UI events.
This is working fine for me on a tree that I pulled on January 4.  Neither 
method of invocation is causing a hang.  Closing this as WFM -- reopen if you 
are still seeing the problem.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
OK, this works fine on my machine at home but it still crashes at work with the
same build.  Steve, can you tell me what files the form manager uses so that I
might be able to track this down to some bad data on the filesystem?
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
The data that the form manager displays is in a *.w file in your profile (the * 
is a randomly-generated name).  You might try removing that file (or, 
equivalently, starting with a fresh profile) to see if the problem goes away.  
That would indicate a corrupted file.  If indeed deleting that file clears up 
the problem, you can e-mail the file to me (assuming you want to trust me with 
any personal data you have in that file) and I'll try to figure out why it is 
causing the hang.

The xul file that the form manager is attempting to bring up at the time 
that your hang is occuring is WalletViewer.xul (in extensions/wallet/editor).
I don't have any .w files in my profile directory.  Here's what I had in my
prefs that was wallet related:

user_pref("wallet.SchemaValueFileName", "75716294.w");
user_pref("wallet.caveat", true);
user_pref("wallet.crypto", true);

I removed those three prefs and the window came up.  I seem to remember, way
back when, turing on crypto-enabled saved passwords for mail and it hung then, too.
Ah, it's a crypto problem.  Now I'm pretty sure you are running into bug 58417.

*** This bug has been marked as a duplicate of 58417 ***
Status: REOPENED → RESOLVED
Closed: 24 years ago24 years ago
Resolution: --- → DUPLICATE
No complaints, been resolved for a long time, marking verified
Status: RESOLVED → VERIFIED
Product: Core → Toolkit
QA Contact: tpreston → form.manager
You need to log in before you can comment on or make changes to this bug.