GNOME Bugzilla – Bug 525638
Fullscreen Locked & won't go to smaller window
Last modified: 2008-04-03 00:12:26 UTC
Totem is locked in full screen mode and though it shows the option to "leave full screen" mode nothing happens when clicked. Also nothing happens when "Esc" is pressed. There is no option to minimize so to gain access to the desktop you must close totem.
How do you get to that state? Which version of metacity, GTK+ and Totem are you using?
(In reply to comment #1) > How do you get to that state? Which version of metacity, GTK+ and Totem are you > using? > When I click to open it or if I click on a file totem plays, it opens in full screen mode. I once clicked full screen mode and it has never gone back. Totem 2.20.0 GTK+ 2.12.0-1ubuntu3 Metacity 1:2.20.0-0ubuntu3 Movie player 0.10.14
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 477529 ***
(In reply to comment #3) > Thanks for the bug report. This particular bug has already been reported into > our bug tracking system, but please feel free to report any further bugs you > find. > > > *** This bug has been marked as a duplicate of 477529 *** > In reading bug 477529 the complaint is that a VOLUME POP-UP won't close "NOT EVEN LEAVING FULLSCREEN MODE HELPS" thus in bug 477529 they can leave fullscreen mode. Where as in this bug (525638) FULLSCREEN MODE CAN NOT BE LEFT the program can only be in FULLSCREEN MODE or closed. Not windowed nor minimized just closed. Please consider reopening this bug.(525638) If these two different problems are linked to the same root cause it might help to add this side effect to the bug description of (477529). Thank you for your time.
It's the same code, and there's no need to yell. The effects are explained in the bug itself.
The capitalization was to highlight the differences in the problem descriptions, as this plain text. It was not meant as yelling. I apologize for any confusion. (In reply to comment #5) > It's the same code, and there's no need to yell. The effects are explained in > the bug itself. >