Red Hat Bugzilla – Bug 161929
Temporary Freezes (lockups) when typing into address window
Last modified: 2008-08-02 19:40:36 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.8) Gecko/20050512 Red Hat/1.0.4-1.4.1 Firefox/1.0.4
Description of problem:
Firefox literally freezes (though temporarily, between 2-20 seconds) when typing addresses into the browser, or entering into Google search window. It happens regularly but not with any specific action or sequence. THE KEY is that it only happens when KDE "klipper" is enabled. This is an x86_64 issue with RHEL 4 (original and update 1)... I haven't seen it on x86, nor on either x86 or x86_64 under RHEL 3.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Enable "klipper" in KDE 3.3
2.Surf using Firefox 1.04
Actual Results: Occasional freezes of 2-20 seconds. Always seems to unfreeze. Entire KDE windows environment misbehaves during this time, then everything returns to normal.
Expected Results: No Freezes. None occur when "klipper" is turned off.
Yes, I can confirm that this bug exists. A workaround to that is to enable
"Ignore Selection" in Klipper.
Is anybody able to reproduce this with the upgraded version of RHEL 4.*?
Since this bugzilla report was filed, we have seriously upgraded Gecko-related
packages, which may have resolved this issue. Users who have experienced this
problem are encouraged to upgrade their system to the latest version of their
Please, confirm to us that this bug is reproducible on the latest upgrade of the
supported distribution (that's RHEL, or Fedora 7, 8, and Rawhide).
Setting the bug to NEEDINFO. If I won't get confirmation of reproducability in
30 days, the bug will be closed as INSUFFICIENT_DATA.
[This is mass-changing of bugs which seem to be too old and irrelevant anymore;
we are sorry, if this bug should not be incldued.]
Reporter, could you please reply to the previous question? If you won't reply in
one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received feedback to the
information we have requested above, we will assume the problem was not
reproducible, or has been fixed in one of the updates we have released for the
Users who have experienced this problem are encouraged to upgrade to the latest
update of their distribution, and if this issue turns out to still be
reproducible in the latest update, please reopen this bug with additional
Closing as INSUFFICIENT_DATA.