After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 727491 - Focus on window does not change on a touch screen panel
Focus on window does not change on a touch screen panel
Status: RESOLVED DUPLICATE of bug 723552
Product: gnome-shell
Classification: Core
Component: general
3.8.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2014-04-02 12:16 UTC by sbozdag
Modified: 2014-04-02 13:38 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description sbozdag 2014-04-02 12:16:36 UTC
Hi,

Our environment has a Debian based box attached to a large LCD panel for video output. User interaction is handled via an IR touch screen plated on that panel. Gnome Shell 3.8.4 is running as the window manager.

Steps to re-produce our so error:

1. Open an application which has a window (e.g. Firefox)
2. Start another application up (e.g. Nautilus)
3. Touch the title bar of the first application and move it around the screen.
4. End the touching event.
5. Now touch on the title bar of the second application.
6. Hold on and try to move it around the screen. But, in a weird way, the first application's window is sticked to the focus event.

To sum up, the focus does not pass to the next window over the title bar. We are able to interact with the next opened window. However, touching the title bar does not change the focus.

We are able to produce the same behaviour for all applications we run. We searched through the filed bugs but no match found for a similar report.

Is there any workaround about it? Otherwise is it a known bug?

Thanks.
Comment 1 Florian Müllner 2014-04-02 13:38:58 UTC
(In reply to comment #0)
> Otherwise is it a known bug?

Yes, it sounds like bug 723552 which is fixed in 3.12.

*** This bug has been marked as a duplicate of bug 723552 ***