Closed Bug 217436 Opened 21 years ago Closed 11 years ago

Keyboard input locks up with GTK2 build using Klipper / KDE

Categories

(Firefox :: General, defect)

Product:
Firefox
Component:
General
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: denis, Unassigned)

Details

Attachments

(1 file)

Here is the output of firebird which gives the lock up issue
19.26 KB, text/plain
Details 
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5a) Gecko/20030812 Mozilla Firebird/0.6.1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5a) Gecko/20030812 Mozilla Firebird/0.6.1

Built Firebird with GTK2 (on Gentoo Linux), also built with GTK1 .. 
Firebird will sometimes suddenly lock up, and will not accept any keyboard
input. It still responds to mouse input, and all functions work, minus clipboard
functionality. 
Just today I noticed I could "unlock" firebird by clicking on the Klipper icon
in my KDE taskbar, and selecting another clipboard entry. This will unfreeze
Firebird, but this happens every now and again. I have not found out on exactly
what conditions this appear but it seems to be associated with clipboard
activity. (new string to clipboard etc.)

Reproducible: Sometimes

Steps to Reproduce:
1. Compile Firebird with GTK2 
2. Use the KDE desktop and have the Klipper applet started 
3. Use firebird for a while copy stuff from KDE applications a lot
4. When Firebird freezes try clicking Klipper and selecting a different entry.

Actual Results:  
Firebird freezes as reported above.

Expected Results:  
Firebird should not freeze when utilizing the clipboard in KDE. 

Using default Qute theme, Gentoo linux 1.4+ (with all applied updates), GTK2 2.2.1
are you doing anything with right-click in the bookmarks when this is occuring?
 Possibly related to bug 210910?
QA Contact: asa → mpconnor
Summary: Keyboard input locks up with GTK2 build using Klipper / KDE → Keyboard input locks up with GTK2 build using Klipper / KDE
No, I actually became aware of bug 210910 very separately from this.
The problem described above occurs in fact without having used any bookmarks at
all. I have now experienced this clipboard bug for a long time, while I have not
been able to pinpoint an exact way to freeze it yet, it seems to be related to
selecting text in KDE applications, not other GTK applications.. 

I will try disabling klipper for a while to see if that stops the bug from
occuring. 
Turning off klipper does not work at all, the freezes still occur and now that
klipper is disabled, the easiest workaround is not possible.. 

I have not yet managed to find a consistent way of reproducing this, but using a
similar setup should produce the bug at least 10 times per working day, possibly
double that amount if you copy / mark a lot of text in KDE.. 
Running the Suse build Firebuild 0.6.1 under Suse 8.2 with kde 3.1.3. gives me
the same keyboard lockups as described here.
I seem to get consistent problems with this when using and marking text in KDEs
Konsole terminal application.. Marking and copying from Kmail might not be a
problem always, but very very often after having used konsole I will get the
lockup bug. 
I first tried the build MozillaFirebird-0.7-i686-linux-gtk2+xft.tar.gz from 
ftp.mozilla.org and ran into this problem as well. So I uninstalled, deleted 
old profiles and I downloaded 0.8 from CVS on 1/25/04 compiled WITHOUT gtk2-xft 
support on my SUSE 9.0 box and even though the fonts looked **** the browser 
worked fine and there were NO lockup issues. I compiled WITH gtk2-xft support 
and started with a new profile and immediately the browser locks up once I use 
the keyboard! Before using the keyboard, the mouse functions properly in 
firebird. I started firebird with the default skin and no extensions or themes 
I first tried the build MozillaFirebird-0.7-i686-linux-gtk2+xft.tar.gz from 
ftp.mozilla.org and ran into this problem as well. So I uninstalled, deleted   
old profiles and I downloaded 0.8 from CVS on 1/25/04 compiled WITHOUT gtk2-xft   
support on my SUSE 9.0 box and even though the fonts looked **** the browser   
worked fine and there were NO lockup issues. I compiled WITH gtk2-xft support   
and started with a new profile and immediately the browser locks up once I use   
the keyboard! Before using the keyboard, the mouse functions properly in   
firebird. I started firebird with the default skin and no extensions or themes  
This bug has disappeared on my workstation. I will update the bug tomorrow with
new version information of GTK2, Qt and KDE. My firefox is now at 0.8, and is
indeed compiled with GTK2. I am still using klipper and konsole a lot, however
my suspicion is that this bug disappeared when going to KDE 3.2..
My current setup, which is an upgraded version of the same gentoo installation
that has had this problem, is :

- Gentoo Linux (kernel 2.4.25-gentoo)
- KDE 3.2.1
- Qt 3.3.0
- Firefox 0.8
- GTK+ 2.4.0

The problem disappeared some time ago, I am not sure exactly when :/ 
I have the same problem, witnessed it yesterday
KDE 3.2
Firefox 0.8+ Gtk2 (not on the machine so i cant give a build id - but a while 
ago)

I have this problem with SuSE 9.0 and firefox 0.8.  When I first updated to SuSE
9 I saw this problem with firefox 0.7.  A fresh install of the 9.0 and Firefox
0.8 solved the problem.  A few days ago, I activated IP-masq and played around
with some permission settings and wallah, the problem returned.  Every user and
wm has the problem EXCEPT for Root.  Root works just fine without any lockup. 
Can this be some weird permission setting for ???????
I have seen this bug, and the way I get it to go away is by minimizing the
window and then opening it again. It only seems to affect the location bar, but
I do see it a lot in ChatZilla now too.

Possibly related to Bug 211132.

Using Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040615 Firefox/0.9
on Slackware Current
Status: UNCONFIRMED → NEW
Ever confirmed: true
It's worse than a lockup: I get a reproducible crash when using kde and 
alt-tab switching.  The steps are:

1. double-click on the URL in the url-bar, to highlight it
2. alt-tab switch a few times in and out of firefox to other windows 
   (crash seems especially fast if other window is konqueror, but any 
   other window seems to do too)

Et voila: rapid crash.  This has been annoying me for a while but it's only now
that I tracked down the connection to kde, and in particular to klipper.  If
I disable klipper, no crash.  I'm using kde 3.3 on debian.  My firefox is
the official 1.0-PR 20041001 build from the mozilla site, not the Debian build.
This has happened with other recent versions of firefox; removing my .mozilla
directory does not help.

Please fix this bug before 1.0.  It has existed for quite a while now, and
would be annoying to kde users.  Konqueror is a great browser -- I use it
a lot now -- but firefox is good to have around too.
Firefox 1.0 just crashed in an identical way.  This is an up-to-date Debian
unstable system but this behaviour has existed for months.  This time I had
talkback enabled; the talkback ID is TB1901838G
Assignee: bross2 → nobody
QA Contact: mconnor → general
Unfortunately this bug is too vague/old to still be useful. If you're having trouble with a recent Firefox build, please file new bugs.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: