Bug 257396 - mouse click, keyboard cursor up key stop working
Summary: mouse click, keyboard cursor up key stop working
Status: RESOLVED WORKSFORME
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-20 10:17 UTC by Rajinder Yadav
Modified: 2018-11-17 05:31 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rajinder Yadav 2010-11-20 10:17:18 UTC
Version:           unspecified (using KDE 4.5.1) 
OS:                Linux

This just started happening, maybe about 3 days ago, i've been using kubuntu 10.10 without an issue for a while.

problem one my mouse button click will just stop working, i am unable to focus on a window, close it etc.

problem two my 'up' key no longer works, if i run xev this is the ouput, the key event is getting noticed but the output is odd?

btw i've tried using a 2nd keyboard, plugged into a seperate usb port, same problem.

FocusOut event, serial 34, synthetic NO, window 0x4000001,
    mode NotifyGrab, detail NotifyAncestor

FocusIn event, serial 34, synthetic NO, window 0x4000001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 34, synthetic NO, window 0x0,
    keys:  0   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 34, synthetic NO, window 0x4000001,
    root 0x15a, subw 0x0, time 1254472, (-1740,-199), root:(0,819),
    state 0x10, keycode 111 (keysym 0xff52, Up), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False


note i can still use the cursor up key from my num keypad

Reproducible: Didn't try

Steps to Reproduce:
this just shows up at random times
Comment 1 Rajinder Yadav 2010-11-20 10:25:53 UTC
when i reboot the system, the cursor up key is working, then it just stops at odd times, i also tired logging in and out, that didn't seem to help
Comment 2 Christoph Feck 2010-11-20 11:47:50 UTC
Sounds like bug 256266 and bug 173606.
Comment 3 Rajinder Yadav 2010-11-20 12:25:13 UTC
On 10-11-20 05:47 AM, Christoph Feck wrote:
> https://bugs.kde.org/show_bug.cgi?id=257396
>
>
>
>
>
> --- Comment #2 from Christoph Feck<christoph maxiom de>   2010-11-20 11:47:50 ---
> Sounds like bug 256266 and bug 173606.
>

I think we need to split my bug into 2 bugs, the keyboard bug is similar 
to Bug 256266, while the mouse bug is another, but the two might be 
related in cause?

I don't want the mouse click bug to get lost because my bug report is 
logged as a duplicate, thanks!
Comment 4 Rajinder Yadav 2010-11-20 12:31:56 UTC
i read bug 173606 and it seems to be the same symptom i am seeing, if i logout and back in using the keyboard the mouse click works fine

is there a way for me to update my kde package for kubuntu 10.10 if the bug has already been addressed? thanks
Comment 5 Andrew Crouthamel 2018-11-05 03:12:25 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Andrew Crouthamel 2018-11-17 05:05:50 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Rajinder Yadav 2018-11-17 05:10:18 UTC
I am no longer using kubuntu 10.10 and have updated to 18.04, feel free to close this bug. 

I no longer see this problem in the new releases.

Thank you.
Comment 8 Andrew Crouthamel 2018-11-17 05:31:54 UTC
Thanks for the update!