176044 - Causes system to freeze when left+right click and drag on hyperlink

Status: RESOLVED DUPLICATE of bug 159055

(SeaMonkey :: General, defect)

Description

[Shaun Cummins]

When pressing the left button (over a hyperlink) followed by an almost
simultatneous right click then quickly drag on a hyper link (or left-click drag
+ a quick right-click), the program locks and freezes the system.  I have been
able to reproduce this error at will (usually takes 2 or 3 attempts), even on a
fresh boot.  This seems to occur on any webpage, even the default page that
loads with Mozilla 1.0.

I'm using Mozilla 1.0 on Redhat Linux 7.1 using a 2.4.2-2 kernel compiled for a
i686.

Comment 1

[R.K.Aa.]

resembles old drag/drop freeze bug 96504, but judging by comments there that one
was fixed in 1.0.

When you say the system freeze: do you mean that the mouse cursor is "locked"
into some shape, (meaning X is affected) or is it linux as such (meaning you
can't with the keyboard or via network either)

To test whether keyboard works do a ctrl+alt+F2 to see if you can get to a
console prompt. (And if you DO get a prompt: Log in to console mode and "killall
mozilla-bin", then ctrl+alt+F7 to get back to X)

(Or try alt+tab if you use KDE or Gnome)

Comment 2

[Shaun Cummins]

Problem is not as severe as I first thought.  Mozilla stops responding to
keyboard and mouse commands as mentioned before.  However, pressing "alt" on the
keyboard resolves the problem and Mozilla is responsive once again.

Comment 3

[R.K.Aa.]

Thanks for quick reply. No blocker, then. Reducing severity.

I reproduced this bug with a two day old trunk CVS build, Linux, following your
descriptions. Hitting "Esc" also clears the stuck cursor mode (which is an angle
cursor with a "+" and  the drag/drop sheet-icon on). I think this is a duplicate
- will look.

Comment 4

[R.K.Aa.]

bug 84087 and bug 125818 are similar.

Comment 5

[R.K.Aa.]

bug 159055 and bug 169108 are similar as well.
steps to reproduce are so to speak identical to bug 159055 - resolving as dup.

*** This bug has been marked as a duplicate of 159055 ***