Bug 216125

Summary: Remaps the window on (unexpected) disconnect, causing it to interrupt the user's work
Product: [Applications] krdc Reporter: Lisandro Damián Nicanor Pérez Meyer <perezmeyer>
Component: generalAssignee: Urs Wolfer <uwolfer>
Status: REPORTED ---    
Severity: wishlist    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:

Description Lisandro Damián Nicanor Pérez Meyer 2009-11-25 18:38:39 UTC
Version:           4.3.2 (KDE 4.3.2) (using 4.3.2 (KDE 4.3.2), Debian packages)
Compiler:          cc
OS:                Linux (x86_64) release 2.6.31-1-amd64

Reported by: Wouter Verhelst
Debian bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557977

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.
Comment 1 Urs Wolfer 2009-11-29 14:03:30 UTC
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?