By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 2336 - Trinity loses mouse pointer
Summary: Trinity loses mouse pointer
Status: RESOLVED WORKSFORME
Alias: None
Product: TDE
Classification: Unclassified
Component: other (any) (show other bugs)
Version: R14.0.x [Trinity]
Hardware: Other Linux
: P5 normal
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2015-01-29 15:07 CST by Darrell
Modified: 2018-08-02 20:53 CDT (History)
3 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Darrell 2015-01-29 15:07:20 CST 
I am unable to repeat this bug with certainty. On several occasions I have lost the mouse pointer in a Trinity session. That is, the mouse pointer is not viewable. I know the mouse pointer is "present" because I used the Eyes applet to track mouse pointer movement (refer to bug 1433). I have to exit X to restore the pointer.

Seems the problem is related to a monitor restoring from DPMS off mode or system suspend. When I restore the Trinity session the pointer is not viewable.

Originally I thought the bug was related to krfb, which has several bugs outstanding. That is, I would remote connect to a Trinity desktop where the monitor had entered DPMS off mode and I then could not view the mouse although the Eyes applet indicated the pointer was "there."

I have seen the bug without using krfb too. On my T400 laptop I have seen the bug when restoring from system suspend. Again, the mouse pointer is not viewable but is "there."

I have not witnessed this bug with the Mate desktop, which I also use. Thus I believe the bug is not related to X but Trinity.
Comment 1 Darrell 2015-02-05 14:42:07 CST 
Please refer to bug 2349. I believe the root cause is one and the same.
Comment 2 Michele Calgaro 2018-08-02 20:53:46 CDT 
I can't reproduce the bug at all and never run into this problem.
I will currently close this bug. If you can reproduce it systematically, please reopen and provide detailed info.