Bug 546267 - mouse pointer disappears when keyboard key is pressed and does not come back when mouse is moved
Summary: mouse pointer disappears when keyboard key is pressed and does not come back ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gtk2
Version: 12
Hardware: i686
OS: Linux
low
high
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-10 15:09 UTC by Samo Dadela
Modified: 2010-12-21 16:09 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
gtk
Last Closed: 2010-12-04 01:51:24 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Samo Dadela 2009-12-10 15:09:57 UTC
Description of problem:
When writing an email after a character is typed the mouse pointer disappears, but when the mouse is moved does not come back. This makes it impossible to paste text using the mouse since you can't see the mouse pointer location.

This happens in claws (when writing emails) and also in gedit - I guess the classification should be gnome/gtk, but I could not find the exact one. I think all gtk editor widgets are affected by the same problem.

Version-Release number of selected component (if applicable):
claws: 3.7.3
gedit: 2.28.0

How reproducible:
Open claws/gedit and try typing some text, the mouse pointer goes away (which is correct). Move the mouse within the edit window -> mouse pointer does not come back. Move pointer outside edit window, mouse pointer does come back. Move pointer back to edit window -> no mouse pointer. 

Steps to Reproduce:
1. open claws (reply to a message) / gedit 
2. type something in the email body -> mouse cursor dissapears (OK)
3. move mouse within edit window -> no mouse pointer (BUG)
4. move mouse outsize edit window -> pointer comes back (OK)
5. move mouse back to edit window -> still no mouse pointer (BUG)


  
Actual results:
No mouse pointer when mouse is moved in gtk/gnome edit windgets. 

Expected results:
Mouse pointer should become visible when mouse is moved!

Additional info:
Tried also changing the mouse theme -> no change. Tried Xfce4 -> no change!
Note: nvidia proprietary drivers were installed, nouwow disabled.

Comment 1 Matthias Clasen 2009-12-11 19:09:41 UTC
Can you reproduce this with gtk2-2.18.5-3.fc12.x86_64 (in updates-testing) ?
There have been fixes in event handling that might explain why I can't reproduce it with that version.

Comment 2 Samo Dadela 2009-12-14 09:01:39 UTC
I'd rather not install anything from updates-testing. I have currently installed gtk2-2.18.3-22.fc12.i686. I guess I'll wait for the next gtk2 update.

Comment 3 Samo Dadela 2009-12-14 09:45:07 UTC
FYI: installed update gtk2-2.18.4-3.fc12.i686... the problem is still here.

Comment 4 Istvan Cebrian 2009-12-14 10:20:18 UTC
Also suffering from this annoying problem. Would like to add that problem also occurs in "gnote" however mouse for me in only not visible when over gnote or gedit as soon as I move away from either mouse is once again visible.

using: gtk2-2.18.4-3.fc12.i686, gedit-2.28.0-1.fc12.i686 and gnote-0.6.3-1.fc12.i686

Comment 5 Istvan Cebrian 2009-12-14 10:26:46 UTC
Would also like to add that when editing in gedit mouse cursor reappears if I save the text file.

Comment 6 Samo Dadela 2009-12-14 10:33:21 UTC
Indeed, after saving the cursor is back...

Comment 7 Istvan Cebrian 2009-12-16 11:19:33 UTC
In gnote when cursor disappears one can get it back by clicking on "Text" menu twice.

Comment 8 Matthias Clasen 2009-12-16 17:14:46 UTC
Let me know if you can reproduce this problem with gtk2-2.18.5. I can't

Comment 9 Istvan Cebrian 2009-12-16 19:03:01 UTC
Using gtk2-2.18.5-3.fc12.i686 from updates-testing repo and still experiencing same problem. Btw should probably point out that I am using synergy may-be it has something to do with issue? Samo are you using synergy?

Comment 10 Samo Dadela 2009-12-17 10:13:13 UTC
Argh... it seems it really is synergy. I killed synergys and the problem went away. Started synergys again problem came back. So to reproduce you must have synergys running (synergy-1.3.1-14.fc12.i686).

Removed synergy and installed synergy-plus... same problem ;( 

Weird that only the gtk widgets are affected...

Comment 11 Matthias Clasen 2009-12-17 13:28:35 UTC
Alex, could there by some interaction between synergy and csw that affects motion events ? I have no idea what synergy does exactly...

Comment 12 Istvan Cebrian 2009-12-17 13:37:23 UTC
Yeah I confirm that killing synergy solves problem. Btw I am also sufering from another bug, mouse and synergy related in Evolution (bug 494712)

Comment 13 Alexander Larsson 2010-01-18 10:22:15 UTC
I'm unable to reproduce this problem (testing with gtk2-2.18.6-1.fc12 and synergy-1.3.1-14.fc12) here. I tested both with gedit and gnotes (but not claws as i don't have it set up).

How exactly do you reproduce it? Is the gedit running on the synergy "server" machine? Are you connected to another synergy client? If so, what version and OS?

Can you reproduce the problem if you run:

GDK_NATIVE_WINDOWS=1 gedit
(ensuring that gedit isn't already running)

Comment 14 Samo Dadela 2010-01-18 10:36:02 UTC
Alexander,

[/home/samod]$ cat .quicksynergy/synergy.conf 
section: screens
	stress.domain.com:
	relax:
	stag:
end
section: links
	stress.domain.com:
		up = relax
		right = stag
	relax:
		down = stress.domain.com
	stag:
		left = stress.domain.com
end

I start it with:
  /usr/bin/synergys -c $HOME/.quicksynergy/synergy.conf

 [stress/FC12] <- synergy -> [stag/Win]
       |
[ Mouse/Keyb  ]
  
stress: my Linux system running synergys... FC12
stag: my Windows system running synergy client... Win2003 R2
relax: another Windows system (ignore it, powered off). 

Note: quicksynergy is nothing more than a gui that created the conf file.
Note: I've tested this with "synergy" and "synergy plus" both have the same problem.. must be something that synergy (events?) does in combination with GTK2. 

On how to reproduce: see my posts above - they explain exactly what you should click...

Comment 15 Samo Dadela 2010-01-18 10:40:06 UTC
Alexander,

GDK_NATIVE_WINDOWS=1 gedit solves the problem - using this variable both gedit and claws-mail work... without it not.

Are there any major drawback in using GDK_NATIVE_WINDOWS? Otherwise I'll set it in my profile... at least until there is a proper fix for this.

Comment 16 Alexander Larsson 2010-01-18 15:26:12 UTC
GDK_NATIVE_WINDOWS=1 disables the use of client side windows in gtk 2.18. Its not meant to be used as a general switch, but rather for applications that need special old compat behaviour. It doesn't exactly use the old code but does some tweaks that make it more compatible. However its gonna be slower and could cause other bugs.

Comment 17 Alexander Larsson 2010-01-18 15:26:47 UTC
Its kinda weird that i can't reproduce this while you can though. What exact gtk version do you have?

Comment 18 Samo Dadela 2010-01-19 08:55:23 UTC
I'm using: gtk2-2.18.6-1.fc12.i686

Though I did not reboot in a while... I'll let you know next time I do so.

Comment 19 Samo Dadela 2010-01-19 09:04:26 UTC
Alexander... I've installed FC12 as soon as it came out... maybe I have some old conf setting from the intial packages... I'll also try to create a new user and see if it works there - maybe its something in my environment.

Comment 20 Samo Dadela 2010-01-21 08:30:54 UTC
Alexander:
Updated system, rebooted -> no change.
Installed latest NVIDIA proprietary drivers (maybe this is the difference) -> no change. 
Created a new user and started synergys -> problem stays.

Comment 21 Anthony Thyssen 2010-03-19 06:21:13 UTC
I can confirm that ths problem also happens for me with synergy and claws-mail and zim notepad applications.   This is with FC12 and all updates to this date.

Bug 560472  seems to be related to this one but using graphical elements in some games.  I am making this note in that bug too.

The GDK_NATIVE_WINDOWS=1  solution however works for my problems and I have set it as part of my normal environment setup for FC12  until I hear of a more permanent solution.

Comment 22 Bug Zapper 2010-11-04 03:42:19 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 23 Bug Zapper 2010-12-04 01:51:24 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 24 George Kraft 2010-12-21 16:09:53 UTC
I'm having the same issue on RHEL6.


Note You need to log in before you can comment on or make changes to this bug.