Welcome to awesome bug tracking system.

FS#908 - Can't exit fullscreen mode in xvnc4viewer

Attached to Project: awesome
Opened by Benjamin (bn8net) - Friday, 20 May 2011, 10:23 GMT
Task Type Bug Report
Category Core
Status Unconfirmed
Assigned To No-one
Operating System Linux
Severity Low
Priority Normal
Reported Version 3.4.10
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No



In my awesome (3.4.6-1 debian squeeze), when I start xvnc4viewer (4.1.1+X4.3.0-37 debian squeeze) and I enable fullscreen mode (by using F8 button), I can't disable it after. I just have to kill process... I don't know if it's an awesome bug or xvnc4viewer bug, but it's realy boring...

Thank you for your help,

This task depends upon

Comment by Uli Schlachter (psychon) - Saturday, 21 May 2011, 11:49 GMT
What exactly does "can't disable it after" mean? How are you trying to disable it?
Comment by Benjamin (bn8net) - Saturday, 21 May 2011, 12:49 GMT
When I'm in fullscreen mode, and I want to disable it, I press F8 button to display xvnc4viewer menu and unmark "Fullscreen". But It does not work : the menu does not close and the mark near "Fullscreen" in menu does not desapear. Other choices in menu does not work too in fullscreen mode perhaps they work as well when fullscreen mode is disabled. Thank's
Comment by Uli Schlachter (psychon) - Saturday, 21 May 2011, 13:45 GMT
I took a look at xvnc4viewer's source code. Fullscreen is implemented by making the window override-redirect and resizing it accordingly. Un-fullscreening is implemented by unsetting the override-redirect flag again.
awesome ignores both ConfigureNotify events which are generated by this. Meh.

In theory, after you pressed the fullscreen button (and nothing happened, still fullscreen), awesome's key bindings should work again. But I guess something weird which I didn't find yet makes this actually not work...

(I took a look at metacity's and dwm's source code. Metacity is complex and DWM doesn't handle ConfigureNotify events either)