Bug 211931 - krdc full-screen meny conflicts with auto-hide desktop panel
Summary: krdc full-screen meny conflicts with auto-hide desktop panel
Status: RESOLVED DUPLICATE of bug 232554
Alias: None
Product: krdc
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Arch Linux Unspecified
: NOR wishlist
Target Milestone: ---
Assignee: Urs Wolfer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-26 13:32 UTC by John Wheaton
Modified: 2011-02-11 18:52 UTC (History)
4 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 John Wheaton 2009-10-26 13:32:24 UTC
Version:            (using KDE 4.3.2)
Installed from:    Ubuntu Packages

I have an auto-hide panel at the top of the screen, and when I go into full-screen mode in krdc the full-screen icon bar for krdc cannot be recalled.  I moved my panel to the bottom of the scree and the krdc full-screen icon bar can be recalled.

Expected behavior:  krdc icon bar should be able to be recalled with a mouse-over even if there is a kwin/plasma panel set to auto-hide at the top of the screen.

Please let me know if you need any other information to reproduce this error.
Comment 1 Urs Wolfer 2009-10-26 20:34:57 UTC
A workaround for your case would be to move the KRDC fullscreen toolbar to another side. You can easily drag it to any side.

But sure, this case can be improved.
Comment 2 John Wheaton 2009-10-26 22:49:37 UTC
Is there a special place the toolbar needs to be grabbed so it can be dragged?  I have tried a number of times and it seems to be stubbornly fixed to top-center.  I notice the two vertical bars on the left-side of it and I have tried to grab that and move it... no luck.
Comment 3 Urs Wolfer 2009-10-27 22:16:59 UTC
You can press your mouse cursor anywhere in the toolbar, and keep it pressed while moving it to another place on the screen. Note that it "jumps" around instead of flowing what you probably have assumed...
Comment 4 John Wheaton 2009-10-28 15:19:11 UTC
Oh... hey... look at that.  Thanks!
Comment 5 Elias Probst 2010-07-02 17:20:22 UTC
This problem does still exist in 4.5 RC1.
Are there any plans/ideas how to fix it?
Comment 6 Urs Wolfer 2010-07-10 17:02:29 UTC
I do not have any idea how to handle this in a better way. KRDC fullscreen window should have higher priority than Plasma.

KWin developers, any ideas here?
Comment 7 Thomas Lübking 2010-07-10 18:24:11 UTC
(have no krdc installed)

@John:
- what happens instead? the plasma panel shows up?
- i assume you're talking about a panel on the host (actually i have no idea what krdc really does but is sounds like an nxclient)
- does it also happen if you use kwin's rmb menu option to set the window to fullscreen?
- do you happen to use the plasma netbook mode?

@Urs:
in case the above holds: sure you really set the window to _real_ fullscreen mode (_NET_WM_STATE_FULLSCREEN) and not just some maximized/borderless mode?

is there another (focussed) window (dialog, popup etc) that might break the fullscreen state?
Comment 8 John Wheaton 2010-07-10 23:22:56 UTC
@Thomas:
- yes, as originally described, the plasma panel shows up instead.  It effectively overlaps the krdc icon bar and I cannot click anything
- krdc:  K Remote Desktop Client ... yeah, kinda like nxclient (or MS Remote Terminal Consol)
- yes
- no, I use full KDE

HTH
Comment 9 Felix Leimbach 2010-10-16 13:22:53 UTC
I've tested fullscreen krdc on KDE 4.5.2 with my KDE panel set to auto hide and reproduced this bug:

Inside the krdc session I'm connected to a Windows Server. When I click on its taskbar NOTHING happens. It feels like windows hangs, but it's just that the click didn't arrive in windows.
When I change my KDE panel from "Auto hide" to "Always visible" the problem goes away.

Seems like an annoying problem for everyone connecting to windows in fullscreen mode.
Comment 10 Andreas Blochberger 2011-02-02 13:47:54 UTC
Maybe Bug 232554 is related
Comment 11 Urs Wolfer 2011-02-11 18:52:37 UTC

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