Opened 18 years ago
Closed 8 years ago
#138 closed defect (obsolete)
Gnome panels on top of a full screen guest if running the Beryl window manager
Reported by: | gbuonfiglio | Owned by: | |
---|---|---|---|
Component: | GUI | Version: | VirtualBox 1.3.6 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | other |
Description (last modified by )
When running Beryl Window Manager and changing the guest to full-screen, the Gnome upper and bottom panels continue on top of the guest full screen session. Changing back to Metacity the full screen session works as expected.
My system is Ubuntu 6.10, Beryl is 0.2.0 rc1 and VirtualBox is 1.3.6.
As I understand, both packages (VirtualBox and Beryl) will be included in the next Ubuntu Release. Should I open a ticket on Ubuntu and Beryl projects also?
Change History (8)
comment:1 by , 18 years ago
comment:2 by , 18 years ago
I've found a workaround :)
In full screen mode toggle "on top" of the virtual machine's window to hide panels
comment:3 by , 18 years ago
I can second this problem, the "on top" solution did not work for me. Anything that you can do on the virtualbox side of this problem would be helpful.
comment:4 by , 18 years ago
the "on top" didn't work for me either i got one solution here, assume the host key for vbox is ctrl_r by default. ctrl_r + f to turn the vm into fullscreen mode then ctrl_r to escape from vm use ctrl+alt+return which is the default hotkey of beryl to turn a window into fullscreen mode after that, i think you can get a fullscreen vm now. although a bit complicated, but at least it works :)
comment:6 by , 17 years ago
where is the "on top" selector? I can't seem to find out how to get to it.
comment:7 by , 16 years ago
Component: | other → GUI |
---|
comment:8 by , 8 years ago
Description: | modified (diff) |
---|---|
Resolution: | → obsolete |
Status: | new → closed |
Please reopen if still relevant with a recent VirtualBox release.
I had such problem with older version of metacity (from Ubuntu 6.06 - panels stayed on top even on metacity). Problem disappeared after update of metacity, so I think this issue should also be sent to Beryl team