Bug 767704 - Problems with full screen applications and GNOME Shell's Messaging Tray
Summary: Problems with full screen applications and GNOME Shell's Messaging Tray
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: wine
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Andreas Bierfert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-14 17:06 UTC by Peque
Modified: 2012-08-18 17:56 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-18 17:56:09 UTC
Type: ---


Attachments (Terms of Use)

Description Peque 2011-12-14 17:06:48 UTC
Description of problem:
While using, in GNOME Shell, full screen applications that should capture the mouse, top left "Applications" corner is correctly handled (that means if you move your mouse over that corner, the overview mode wont be activated). If you move your mouse to the bottom right "Messaging Tray" corner, the tray will pop up over your full screen application.

Version-Release number of selected component (if applicable):
Wine 2.3.33, but it happened as well in 2.3.29 when I used it.

How reproducible:
Just move your mouse over the bottom right corner, and see the Messaging Tray popping up.

Additional info:
This happens to me while playing a game (StarCraft II). Seems it happens with other applications or games where that corner is needed to correctly scroll through the map. When the Messaging Tray appears, you can not even scroll down until it goes down again.

Comment 1 Jonas Wielicki 2012-02-23 00:54:47 UTC
I can confirm this with pyglet fullscreen applications.

Comment 2 Michael Cronenworth 2012-08-18 17:56:09 UTC
The latest version of Wine is 1.5.9. Please upgrade.

I just played a game of Starcraft 2 1.5.1 and Diablo 3. I cannot see or access the Gnome 3 Messaging Tray when I am inside the game.


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