[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: ksmserver
From:       Thomas Schubert <thom.schubert () gmx ! de>
Date:       2001-09-30 10:20:14
[Download RAW message or body]

Thanks for replying, Waldo,

but I'm getting nowhere.

This is rather weird, so I guess maybe some developers might actually be 
interested. 

Summary: At logout from kde 2.2.1 the greying effect starts, then all windows 
come back to the front and are accessible and functioning, including kicker. 
ksmserver opens two (non-visible) windows in the task-bar. Clicking one of 
them does nothing, clicking the other craches kde.
Logout itself is still possible.
All users (!) are affected, even root. Install of kde was as clean as 
possible, and displayed no problems at first.
I have tried deleting all possibly connected files, including DCOP*, MCOP*, 
.x*, .X*, in home, removing .kde in home and /tmp. No effect.
Even starting from init 1, and killing every process in sight (including all 
processes started by kde, that don't immediately kill kde) as well as 
unloading all possible modules, displays this behaviour.
EXCEPT: killing kwin prevents this effect temporarily; restart kwin -> it's 
back.

This is occurring with at least another user with a very different 
setup/distro.

Grateful for any assistance
Thomas

On Sunday 30 September 2001 00:13, Waldo Bastian wrote:
> On Saturday 29 September 2001 03:46 am, Thomas Schubert wrote:
> > Hi.
> > some problems appeared on kde-linux concerning ksmserver and
> > session-management, which prevent regular log-out behaviour, and no
> > solution was found so far (tried deleting .kde, /tmp, DCOP related stuff,
> > and others). This occurs with all users (including root), so its some
> > sort of  global thing.
> > I'm trying to track it down, but need help. Where would
> > session-management save its settings? What obscure locations/files could
> > I check/delete? There doesn't seem to be any zombie processes lying
> > around.
>
> ksmserver uses  .../share/config/ksmserverrc for its configuration but I
> doubt that this is causing problems.
>
> It also uses a socket. If you open a terminal and do echo $SESSION_MANAGER
> you should get something like:
> 	local/wantelbos:/tmp/.ICE-unix/3595
>
> Where "wantelbos" is the hostname and "/tmp/.ICE-unix/3595" is the location
> of the socket. The number "3595" should be equal to the pid of ksmserver.
>
> However, most problems with session management seem to originate in the
> applications using session management. E.g. there might be an application
> running at the time session management tries to shutdown that doesn't
> properly handle the session management protocol. ksmserver stores the
> session in ksmserverrc.
>
> Cheers,
> Waldo
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[prev in list] [next in list] [prev in thread] [next in thread]