Hi, I am currently at a customer where the security policy does not allow me to simultaneously connect my laptop to the Internet and the local LAN. However, there is a Windows Terminal server with a web browser that I can use in case I need to browse the Internet while connected to the LAN. This server is configured so that if the session has been idle for more than a certain amount of time, the connection is dropped, server-side. In itself, that's not a problem. However, it becomes a problem because this usually happens when krdc is on a different virtual desktop (otherwise I would've seen the warning that the server sends out two minutes prior to disconnecting), and upon disconnect krdc unmaps the full-screen window, and remaps a non-fullscreen but maximized window right after that, unconditionally. This remap causes it to be shown on the then-active virtual desktop, interrupting any work that I may be doing at that time. The fix to this is easy: rather than unmapping the normal window when going full-screen, it should be brought to the background. This way, when the full-screen window is removed, the maximized window does not need to be created, and will remain on the other virtual desktop.
tags 557977 upstream forwarded 557977 http://bugs.kde.org/show_bug.cgi?id=216125 thanks Wouter: I think this is a wishlist bug, so I forwarded it upstream as a wishlist bug. I'll keep this bug as normal thought (some other more experienced maintainer may change that thought). Regards, Lisandro.
tags 557977 upstream forwarded 557977 http://bugs.kde.org/show_bug.cgi?id=216125 thanks Wouter: I think this is a wishlist bug, so I forwarded it upstream as a wishlist bug. I'll keep this bug as normal thought (some other more experienced maintainer may change that thought). Regards, Lisandro.
tags 557977 upstream forwarded 557977 http://bugs.kde.org/show_bug.cgi?id=216125 thanks Wouter: I think this is a wishlist bug, so I forwarded it upstream as a wishlist bug. I'll keep this bug as normal thought (some other more experienced maintainer may change that thought). Regards, Lisandro.
tag 557977 moreinfo thanks From the KDE BTS [0]: Basically it should restore the main window state after going to windowed mode again. If this does not work, it's a bug. Can you reproduce this issue all the time? Does it restore to the same position always? [0] <https://bugs.kde.org/show_bug.cgi?id=216125> You may either answer here and I'll forward it ASAP, or you may suscribe to the bug upstream and continue it there (this last option would be preferred) Regards, Lisandro.
Hi, you reported http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557977 some time ago. Can you please provide the additional information that has been requested from KDE upstream? Eckhart
Hi, you reported http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557977 some time ago. Can you please provide the additional information that has been requested from KDE upstream? Eckhart
Hi, I thought I had, but apparently that's wrong. Sorry 'bout that. Yes, it does happen every time. I should note that I'm not using KDE, since I don't believe in desktop environments; but I do cherry-pick some applications from both gnome and kde that I find useful. One of these is krdc. My UI of choice is IceWM. Due to the fact that virtual desktops are not implemented consistently across all user environments, I don't think 'restoring the window state' is something that can be implemented in a safe manner. Note that you don't need to update the window anymore; just making sure it does not get unmapped should be enough.