GNOME Bugzilla – Bug 688105
AppMenu on primary screen can be obscured by full-screen applications
Last modified: 2013-11-18 14:11:43 UTC
When an application on a secondary screen has an AppMenu, its AppMenu lives back on the primary screen. If the primary screen is running an application in full-screen mode, you can't see the AppMenu. In that case, the only solution is: - un-fullscreen/close the primary app - use the AppMenu as required - Re-open/fullscreen the primary app
Like i said in the previous bug report, I think an app menu in the title bar would be a nice solution. Maybe easier after switching to CSD (if it's still planned).
Can you please describe the case where you had two fullscreen windows open at once? Thanks.
never said anything about two fullscreen windows at once. The problem is you cannot acces the AppMenu of an app on the secondary monitor if the primary monitor has an app in fullscreen mode. Even if its not fullscreen, it's cumbersome to go to the primary monitor for the menu if i work on another at the moment. It's not that big a deal now, but if the trend is to stuff more things into this menu it will.
Sorry, misunderstood. Can you give an example of the apps in your specific case?
the cause i wrote the original bug was: I was watching a presentation with totem on the primary monitor. Then i needed the calculator to check something, so i opened it on the secondary monitor. When i wanted to switch calc to advanced mode i was kinda lost, because i did't find the option. After googling i realized the option moved to the appmenu, which i didn't see because totem was fullscreen on the primary monitor. I don't know, but i do this quite often .. watch something on the primary monitor (or maybe playing a game) and do some other stuff (browsing, chatting, etc..) on the secondary.
I think that it will be most effective if we deal with this issue as a part of bug 695377 . Florian - I see that you have already commented there. Please feel free to add any information that you feel is important. *** This bug has been marked as a duplicate of bug 695377 ***