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 1347 - Mouse pointer not visible when TDE session gets locked.
Summary: Mouse pointer not visible when TDE session gets locked.
Status: RESOLVED FIXED
Alias: None
Product: TDE
Classification: Unclassified
Component: tdebase (show other bugs)
Version: 3.5.13 [Trinity]
Hardware: Other Linux
: P5 minor
Assignee: Francois Andriot
URL:
Depends on:
Blocks:
 
Reported: 2012-11-28 11:08 CST by f_ii
Modified: 2013-09-25 05:44 CDT (History)
5 users (show)

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

Attachments
F17-TDE package list (12.13 KB, application/bzip2)
2012-11-29 09:06 CST, f_ii 		Details
View All 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 f_ii 2012-11-28 11:08:34 CST 
Description of problem:

Mouse pointer not visible when TDE session gets locked.

When TDE session gets locked by timeout mouse pointer disappers.
Mouse pointer should appear when mouse changes position, which is not the case.
Currently mouse pointer appears on mouse wheel action only.

Version-Release number of selected component (if applicable):
fedora-release-17-1.noarch
trinity-tdebase-3.5.13.1-1.fc17.opt.x86_64

How reproducible:
100%

Steps to Reproduce:
1. session get locked
2. mouse pointer get invisible
3. mouse pointer does not get visible by mouse move
  
Actual results:
 Mouse pointer does not get visible by mouse move.
Expected results:
 Mouse pointer should get visible by mouse move.
Additional info:
Comment 1 Darrell 2012-11-28 11:26:31 CST 
Mouse pointer is visible here with Slackware. As you are using Fedora, Francois should get involved.
Comment 2 Francois Andriot 2012-11-28 15:37:07 CST 
Hello, I do not have this behaviour on my F17 virtual machine.
When I lock the screen, the mouse cursor does not get hidden, it remains visible.

Do you use a personalized mouse cursor, or have you kept the standard "black arrow" cursor ?

How did you install Fedora and TDE ? Did you do some kind of "minimal installation" of Fedora, then install TDE ?
Maybe a missing Fedora package is causing the problem.

Can you reproduce this behaviour on another desktop environment, like KDE4 or Gnome ?
Comment 3 f_ii 2012-11-29 08:57:32 CST 
(In reply to comment #2)
> Hello, I do not have this behaviour on my F17 virtual machine.
> When I lock the screen, the mouse cursor does not get hidden, it remains
> visible.

I've tried many times even when I lock the session by locking button I get to screen with credentials dialog and after 5-10 seconds without mouse move black cursor becomes invisible.
Moving mouse does not help then, the only way which help is mose wheel movement.

> 
> Do you use a personalized mouse cursor, or have you kept the standard "black
> arrow" cursor ?

Everything standard.

> 
> How did you install Fedora and TDE ? Did you do some kind of "minimal
> installation" of Fedora, then install TDE ?
> Maybe a missing Fedora package is causing the problem.

I've installed F17+TDE from spin iso downloaded from TDE website:
  e3366ad8a8ef666a162651c67bcfffc0  TDE_FC17_x86_64.iso

Then I updated system via yum...

> 
> Can you reproduce this behaviour on another desktop environment, like KDE4 or
> Gnome ?

I'll try and let you know
Comment 4 f_ii 2012-11-29 09:06:44 CST 
Created attachment 1034 [details]
F17-TDE package list
Comment 5 Timothy Pearson 2013-06-08 02:13:34 CDT 
This should be fixed in GIT hash 936f951.  Leaving open with NEEDINFO pending confirmation of the fix. :-)
Comment 6 Darrell 2013-08-17 15:16:54 CDT 
Patches have been submitted. Is this report still valid?
Comment 7 f_ii 2013-09-25 05:44:48 CDT 
The issue has been fixed.

I'm not seeing above described behavior on TDE version
 trinity-*3.5.13.2-2.fc17.opt.x86_64

on the same machine where it was failing with trinity-*3.5.13.1*.