Weird behavior of gtk controls

Bug #128256 reported by Tomasz Melcer
2
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Expired
Low
Unassigned

Bug Description

Sometimes gtk apps start to behave quite strange. Most menus doesn't popup (both main window menus and popups), that seem to happen with all gtk programs I use: gajim, evolution, freeciv, gimp... Firefox is an exception, the menus work correctly, but program ignores all key presses (I think that's because firefox reimplements his toolkit and uses gtk in a different way than other apps).

It all happens simultaneously. Just after logging in, everything works well. Sometimes after few minutes/hours whole environment starts to have such misbehaviors. It never affected single app; when I saw that one app is misbehaving, all apps started to do so. Everything returns to normal when I close all gtk apps I have. Closing f.e. only firefox windows doesn't help.

I work under fvwm-crystal (a set of configuration files for fvwm). All this never happened to other users of this computer, all of them use standard gnome.

That's all pretty weird and difficult to describe, I cannot find any cause or even any way to reproduce; I am filling this report in hope that someone will help me debug that or at least someone will verify this.

System is Ubuntu Feisty, updated regularly. libgtk2.0-0 is 2.10.11-0ubuntu3.

Revision history for this message
Tomasz Melcer (liori) wrote :

I forgot of one more thing. While the environment is in that broken 'mode', all gtk entry widgets (except firefox) don't display cursor. I can still type there, but i don't see the cursor.

I've just spotted a thing that may cause these misbehaviors. I use a usb-to-ps2 converter to connect my keyboard to the computer. It seems that this small device sometimes resets the keyboard. The keyboard lights its diodes for a second when that happens. I typed an url into firefox now and while typing the diodes blinked, then firefox stopped to accept key presses. My hypothesis is that due to keyboard reset a flag (possibly in gtk, fvwm, X or kernel) somewhere is set to wrong value.

I tried xev to get keyboard state from X, but then I noticed that I can type in firefox again; i think xev is so low-level tool that it could change that flag.

Revision history for this message
Tomasz Melcer (liori) wrote :

Ok, I checked: that's not converter's fault, the bug happens also when I do not use that converter. Also, the output from xev is identical whether the system is misbehaving or not.

Revision history for this message
Tomasz Melcer (liori) wrote :

It looks like the bug is somehow triggered by having two keyboards attached to the PC. One was connected by USB, second (my primary) by PS/2. Now I have only the second one and I had no such misbehavior for almost a week. I think I can still reproduce that bug, so if anyone can help, I'm ready to test things.

Revision history for this message
Tomasz Melcer (liori) wrote :

Well, I just got it once again, with one keyboard connected... so ignore my last comment.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Not likely a GTK bug, maybe a network issue or an xorg bug

Revision history for this message
Henrik S. (henrik-hw0) wrote :

Please take a look at:
https://bugs.launchpad.net/ubuntu/+bug/229123

Does any of the symptoms sound familiar?

Revision history for this message
penalvch (penalvch) wrote :

Thomasz Melcer, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p xorg REPLACE-WITH-BUG-NUMBER

Please note, given that the information from the prior release is already available, doing this on a release prior to the development one would not be helpful.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Changed in xorg (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for xorg (Ubuntu) because there has been no activity for 60 days.]

Changed in xorg (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.