[kwin] [Bug 326893] KDE programs are not restored to the correct locations when restoring the previous session on login

Thomas Lübking thomas.luebking at gmail.com
Sat Jan 11 08:35:22 GMT 2014


https://bugs.kde.org/show_bug.cgi?id=326893

Thomas Lübking <thomas.luebking at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |CONFIRMED
          Component|general                     |core
            Version|4.11.2                      |4.11.5
           Assignee|unassigned-bugs at kde.org     |kwin-bugs-null at kde.org
            Product|kde                         |kwin
   Target Milestone|---                         |4.11
     Ever confirmed|0                           |1

--- Comment #17 from Thomas Lübking <thomas.luebking at gmail.com> ---
This is a two level issue (was for me)

1. ps ax | krep kwin
  556 ?        Sl     0:11 /usr/bin/kwin --replace -session
10d3d76761000138940825800000024960000_1389410931_93899

If there's no "-session <key>" parameter, you're facing a condition where kwin
is started w/o being asked to restore the window attributes from the last
session.

Happened to me because ksmserver is very picky about reloading stuff.
If the stored restart/command does not fit the expected WM command, it will
just call the configured WM w/o any further parameters (including session
control)
(Here, "kwin" is a script to call /usr/bin/kwin, thus leading to mismatching
"kwin" ./. "/usr/bin/kwin" comparism)

2. Beyond that (well, now that session restorage works in principle),
apparently clients like at least TheGimp do not set/restore SM_CLIENT_ID -
neither directly, nor on their leader window.
SM_CLIENT_ID is the relevant property for session restorage, but KWin has some
heuristics to match the session data to the new window anyway.

I assume this broke by making the wmClientMachine detection asynchronous, see
bug #308391 - "and the case of session management is" not ultimately so "very
academic" since WM_CLIENT_MACHINE is $(cat /etc/hostname) - not the stored
"localhost"

tl; dr:
Those windows do actually simply not support session management, but
nevertheless there's a regression in KWin's workaround for that.
         -> (2) is a KWin bug, (1) is ebkac


@Martin
The intended patch is to drop client machine comparism on session restorage
heuristics (to cause the academic problem ;-)

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Unassigned-bugs mailing list