User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8) Gecko/20051111 Firefox/1.5 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8) Gecko/20051111 Firefox/1.5 If im starting a FTP Transaction (wich takes a fews seconds until the Username and Password mask appears). In that time, after starting the FTP transaction and before appearing the password mask, i draged a link from the Bookmarks. Now when the PW and Username Window appears, before i droped the Link from the Bookmark, Firefox crashes. Reproducible: Always Steps to Reproduce: 1.open a ftp transaction wich needs some seconds before PW and Username Window 2.Drag with the mouse a Link from your Bookmarks 3. If the PW and Username Window appears, Firefox stucks... Actual Results: cant do anything with firefox Expected Results: not crashing
*** Bug 325346 has been marked as a duplicate of this bug. ***
Could you reinstall Firefox with Talkbalk (choose custom install; Quality Feedback Agent) and provide a Talkback ID? To find the ID after the crash go to <install dir>\extensions\email@example.com\components\talkback.exe and copy the ID to this bug.
Does FF crash (app is gone) or does it "only" hang/freeze? I guess it could be something like Bug 246801.
Component: Tabbed Browser → General
QA Contact: tabbed.browser → general
Summary: waiting for FTP Transaction while have a link draged. → waiting for FTP Transaction while have a link dragged.
Version: unspecified → 1.5 Branch
(In reply to comment #3) > Does FF crash (app is gone) or does it "only" hang/freeze? > > I guess it could be something like Bug 246801. > Jepp, you are right! Its just freezing, not crashing, sorry. Its really like Bug 246801.
Ok, so I'm duping it. FWIW: When this happens, the cursor deadlock is UN-locked by simply hitting the "Esc"-key, because only mouse input is locked, not the keyboard. *** This bug has been marked as a duplicate of 246801 ***
Status: UNCONFIRMED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.