Bug 275831 - panel in auto hide mode prevents virtulbox functionality
Summary: panel in auto hide mode prevents virtulbox functionality
Status: RESOLVED DUPLICATE of bug 217560
Alias: None
Product: plasma4
Classification: Plasma
Component: containment-panel (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-16 18:26 UTC by menschmeier
Modified: 2011-12-02 16:48 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description menschmeier 2011-06-16 18:26:18 UTC
Version:           4.6 (using KDE 4.6.4) 
OS:                Linux

I am using VirtualBox as VM runing other operating system.
I activated the auto hide mode for the panel (containing the K-menue an other widgets) to get more desktop space for my programs.

If I do so and let run VirtualBox in full-screen-mode I can not use the little Virtualbox-panel that used to appear when you move the cursor to the centered botton of the screen.

I actived the always-visible-model of the KDE-panel I can use the VirtualBox-panel when I run it in full-screen-mode.



Reproducible: Always

Steps to Reproduce:
1. KDE-panel is on bottom of the desktop
2. set the auto-hide-mode for it
3. start VirtualBox 
4. start a VM 
5. put the VM in full-screen-mode
6. position the mouse cursor in centered botton position

Actual Results:  
the VirtualBox panel does not appear

Expected Results:  
the VirtualBox panel should appear

OS: Linux (x86_64) release 2.6.38-8-generic
Compiler: cc
Comment 1 Christoph Feck 2011-06-17 00:24:13 UTC
I have seen many people using a top-aligned VM panel, but could have been VMWare. How do you suggest to solve the problem with two applications fighting for a screen edge?
Comment 2 Konstantin 2011-08-13 14:42:50 UTC
It seems to be a duplicate of bug 217560.
Comment 3 Gregor Tätzner 2011-12-02 16:48:55 UTC
good catch

*** This bug has been marked as a duplicate of bug 217560 ***