On Mon, 2007-Jan-15 at 18:54:20 +0100, Andre Oppermann wrote: > Brooks Davis wrote: > >On Mon, Jan 15, 2007 at 08:55:07PM +1030, Daniel O'Connor wrote: > > > >>Hi, > >>I recently updated my machine to -current, however I can nolonger unlock > >>my desktop - I have to manually kill the kdesktop_lock process. > >> > >>I've recompiled kdebase but it had no effect. I plan to try kdelibs soon. > >> > >>Is this a known issue? > > > > > >The problem is apparently due to breaking of sending zerobyte messages > >over certain types of sockets. I think peter has a patch that works > >around it in KDE, but I'm not sure it's available anywhere. > > I have a fix in the works. > Just for the record, this problem doesn't seem to be KDE-specific. I'm experiencing the same behaviour under Gnome 2.16 - xscreensaver isn't able to correctly close itself and without manually killing the proces, you are not able to return to the desktop. - i386 FreeBSD 7.0-CURRENT #0: Mon Jan 15 06:48:57 CET 2007 - gnome2-2.16.2 - xscreensaver-gnome-hacks-4.24_1 Sending a sigterm to gnome-screensaver does the trick. m.Received on Mon Jan 15 2007 - 20:50:41 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:04 UTC