Bug 252397 - Mouse cursor becomes invisible in KPackageKit.
Summary: Mouse cursor becomes invisible in KPackageKit.
Status: RESOLVED WORKSFORME
Alias: None
Product: kpackagekit
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: Steven M. Parrish
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-26 04:48 UTC by Mars
Modified: 2018-11-05 23:30 UTC (History)
3 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 Mars 2010-09-26 04:48:38 UTC
Version:           unspecified (using KDE 4.4.5) 
OS:                Linux

The mouse cursor became invisible while I was using KPackageKit.  When I moved my mouse to make the cursor move outside the KPackageKit window, the mouse cursor re-appeared, i.e. an arrow appeared.  But when I moved the cursor back to the KPackageKit window, the cursor became invisible again.  

(It still functioned, I was able to click on the exit button, but its hard to use when it can't be seen.)


Reproducible: Didn't try




Sorry, I can't say how to reproduce it.  

I am not sure of the circumstances when the mouse pointer became invisible.  I was using KPackageKit, but I can't remember what I was doing with it.  I hope that other people will comment on this bug, and tell us when it occurs.
Comment 1 Andrew Crouthamel 2018-11-05 03:13:12 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 2 Mars 2018-11-05 21:18:49 UTC
I didn't find out how to reproduce this bug, so this bug can't be fixed.

I haven't used KDE for a few years now, so this bug is no longer a problem for me.

I guess we should close this bug.
Comment 3 Andrew Crouthamel 2018-11-05 23:30:19 UTC
Thanks for the update!