| Summary: | Problems with events and evdev | ||
|---|---|---|---|
| Product: | xorg | Reporter: | Marcelo Estanislau Geyer <estanisgeyer> |
| Component: | Input/evdev | Assignee: | Zephaniah E. Hull <warp-spam+fdo> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | 6.9.0 | ||
| Hardware: | x86 (IA32) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
I don't really know what is the main reason. My expirience: Trying to reassign "hot key action" (Control center/Regional & Acessibility/Keyboard shortcuts) to some action (I was trying to minimize widow). KDE at the moment saying - hey! There ara already exist action for the buttion would you like to reassighn? Answering yes and trying new function: pressing "UP" and the current window do minimise. Ok now I can see the button works. The next step is to deactivate the "hot action" and try functionallity of "UP" in konsole, now it works! Restarting KDE and... The same story "UP" having trouble in konsole etc. making the procedure agein and forcing to work "UP" normally. Ok now i did kill all my home configs. It is ~/.kde directory and some .kdeinit??? Starting Xorg, xterm, mc - rtying "UP" -works fine. Startkde after passing wizard running console and "UP" works just fine. Well will try for some time this configuration and if new bug will appear I'm gonna report. You see It's not only Kde because if "UP" not works in KDE then in pure X with running xterm only "UP" acts all the same... Ya it's strange it looks like kde having influence on X, how could it be possible? p.s. The "up" problemm exist for both my keyboards PS/2 and Usb. I up to date KDE 3,4 for version 3.5, the problem with event "UP" I continued, however he was alone to enter in the Control center/Regional & Acessibility/Keyboard shortcuts, to make some modification and click in the button "default". I can restart the Xorg that the configuration keycode 111, Keysym "Up" is fine. Well, I beleave bug for kde 3.4 configuration file. Reassign to the new evdev maintainer. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
I found problems with driver evdev in top of the KDE (3,4 and 3.5). I do not know if it is incompatibility with the KDE or small bug of this driver, but I am put here for knowledge of all. I'm use a keyboard PS/2, layout br, model abnt2. In environment KDE, keycode 111 (referring to the event "Up") is not recognized. No longer GNOME this does not happen. They see the output of xev, in kde: KeymapNotify event, serial 30, synthetic NO, window 0x0, keys: 25 0 0 0 0 0 0 0 0 0 0 0 0 4294967168 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 KeyRelease event, serial 30, synthetic NO, window 0x2600001, root 0x119, subw 0x0, time 3488711, (723,197), root:(727,735), state 0x10, keycode 111 (keysym 0xff52, Up), same_screen YES, XLookupString gives 0 bytes: Now, they see output in Gnome: KeyPress event, serial 29, synthetic NO, window 0x2a00001, root 0x119, subw 0x0, time 3648714, (73,254), root:(78,303), state 0x10, keycode 111 (keysym 0xff52, Up), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 29, synthetic NO, window 0x2a00001, root 0x119, subw 0x0, time 3648795, (73,254), root:(78,303), state 0x10, keycode 111 (keysym 0xff52, Up), same_screen YES, XLookupString gives 0 bytes: They repair that in kde xev does not generate the KeyPress of keycode 111. In environment KDE, the event "Up", functions in the menu of the KDE and in the bar of address of firefox, for example, but when it opens one konsole or a text publisher, this event it does not function. Some idea?